How to Configure a Meta Conversion API Action in Workflows
Why Create a Meta Conversion API Workflow?
After setting up your Meta ad campaign and conversion dataset, creating a workflow to send Conversion API (CAPI) events is essential for improving the accuracy, reliability, and performance of your advertising efforts. Using CAPI alongside standard tracking methods offers several advantages:
- Improved Accuracy: Data is sent directly from your server, avoiding issues like browser restrictions, ad blockers, or cookie limitations.
- Better Attribution: Tracks conversions across devices and platforms, even for users who block cookies, providing more complete data for optimization and reporting.
- Fills Pixel Gaps: Ensures conversions are recorded even if the pixel is blocked or fails to load due to slow page speeds or privacy settings.
- Enhanced Optimization: Server-side data helps Meta improve ad targeting and campaign performance.
- Privacy Compliance: Reduces reliance on client-side cookies, aligning better with modern privacy regulations.
- Efficient Budget Spend: More accurate data allows Meta to optimize your ad spend and improve ROI.
In short, sending CAPI events ensures your ads perform efficiently, even as browser restrictions and privacy concerns increase.
Which Workflow Triggers Work with Meta Conversion API?
The triggers you can use with a Meta Conversion API action depend on the event type you select. Here are the eligible triggers for each event type:
Funnel Events
- Form Submitted
- Survey Submitted
- Customer Booked Appointment
- Order Form Submission
Note: For appointments, only the "Customer Booked Appointment" trigger works, not general appointment triggers.
Lead Events
- Facebook Lead Form Submission
- Pipeline Stage Change (only if the contact originated from a Facebook lead form)
Instagram DM Events
- Any trigger that results in contact creation in the CRM
Ad Manager vs. Integrations Connection Type
When configuring a Meta Conversion API action in a workflow, you'll see two connection types: Integrations and Ad Manager. The Ad Manager option simplifies the setup process by reducing the need to switch between Meta and your CRM.
Key benefits of using Ad Manager:
- Select the event type based on your campaign objective: use Funnel Event for "Website Traffic," Lead Event for "Lead Generation," or Instagram DM for "Click to Direct" ads.
- All pixels associated with your Ad Manager account are pre-populated in a dropdown, eliminating the need to copy and paste Pixel IDs from Meta.
- No need to generate or add an access token manually—the system handles it automatically.
For the Integrations connection type, refer to dedicated articles on setting up lead and funnel events for detailed field explanations.
Configuring Lead Events and Purchase Stage
When using a Lead Event with the stage name set to "Purchase," two additional fields appear:
- Value: Enter a static value or select a custom field.
- Currency: Choose from a dropdown list (defaults to USD), using the same currency options as Funnel Events.
These fields are only required when the stage name is "Purchase." If provided, the system includes them in the CAPI payload. For any other stage name, Value and Currency are ignored.
To set the stage name accurately for reporting, use the tag icon to select the appropriate pipeline and stage from your CRM.
Using Offline Event Triggers
Yes, you can use triggers like "Call," "Opportunity Change Status," or "Tag" with Meta Conversion API actions. The system will use the last available pixel data (such as an fbclid) to send the event to Meta's Conversion API. This allows offline actions to be recorded and attributed to your ad campaigns.