Send Meta Conversion API Events from Sparkforge Workflows

By Sparkforge Support Team ·Last reviewed May 3, 2026

Use the Meta Conversion API workflow action to send server-side conversion events to Meta. Ad Manager mode auto-populates your pixels and handles access tokens, so lead, funnel, and Instagram DM events flow without manual setup.

The Meta Conversion API (CAPI) workflow action sends server-side conversion events back to Meta. It fills the gap left by browser-based pixel tracking when ad blockers, slow load times, or privacy settings prevent client-side firing.

Why send CAPI events

Better tracking accuracy: Server-side events bypass browser restrictions, ad blockers, and cookie limits.
Cross-device attribution: CAPI tracks conversions even when the user blocks cookies.
Pixel gap coverage: Records conversions that the pixel missed.
Privacy-friendly: Less reliance on client cookies, better fit for current privacy rules.
Cleaner ad spend: More accurate signals help Meta optimize delivery and ROI.

Connection types: Integrations vs. Ad Manager

The Meta Conversion API action offers two connection types:

Integrations: manual setup with Pixel ID and access token from Meta.
Ad Manager: Sparkforge pulls your connected pixels into a dropdown and handles the access token automatically.

Ad Manager mode removes the back-and-forth between Meta and Sparkforge for setup.

Pick a trigger that matches your event type

Funnel events

Form Submitted
Survey Submitted
Customer Booked Appointment (note: this is the widget trigger, not the general Appointment trigger)
Order Form Submission

Lead events

Facebook Lead Form Submission
Pipeline Stage Change (only when the contact came from a Facebook lead form)

Instagram DM events

Any trigger that creates a contact in the CRM.

Stage Name and Purchase value

For lead events, the Stage Name should match your pipeline and stage for clean reporting. Use the tag icon to insert custom values for the opportunity pipeline and stage.

When Stage Name is Purchase, two extra fields appear:

Value: static number or a custom field.
Currency: defaults to USD; same currency list as funnel events.

Both are required only when Stage Name is Purchase. If Stage Name is anything else, Sparkforge ignores any Value or Currency in the payload.

Offline events with non-form triggers

You can use Call, Opportunity Status Change, Tag, and similar triggers with the Meta Conversion API action. Sparkforge sends the event using the most recent attribution data on the contact. If an fbclid is on file, the event reaches CAPI.

Example 1: A contact arrives via a Facebook lead form, attribution is Paid Social, and an fbclid is recorded. Later that contact converts to an opportunity. A workflow on Opportunity Status Change can send the event to CAPI because the fbclid is still attached.

Example 2: A contact starts on Google Ads (Paid Search), then later submits a Facebook form. The latest attribution becomes Paid Social with an fbclid. Subsequent workflows can send to CAPI on that fbclid.

Custom mapping for FBCLID and Lead ID

By default, custom mapping is off. Toggle it on to map your own values:

FBCLID for funnel events
Facebook Lead ID for lead events

If a custom mapping field is filled, it overrides the system default. If left blank, Sparkforge uses its built-in value.

Frequently Asked Questions

Why use the Conversion API on top of the Meta Pixel?

CAPI sends events server-side, so it captures conversions when the pixel is blocked by ad blockers, browser restrictions, or strict privacy settings. The result is more complete attribution data.

What is the difference between Ad Manager and Integrations connection types?

Ad Manager mode auto-populates your connected pixels in a dropdown and manages the access token for you. Integrations mode requires manually entering the Pixel ID and token from Meta.

Which workflow triggers work with funnel events?

Form Submitted, Survey Submitted, Customer Booked Appointment, and Order Form Submission. The general Appointment trigger does not work — use the Customer Booked Appointment widget trigger.

When do I need to set Value and Currency on a Meta CAPI action?

Only when the Stage Name is Purchase. In every other case Sparkforge ignores Value and Currency, even if they're in the payload.

Can offline triggers like Call or Tag send to Meta CAPI?

Yes, as long as the contact has an fbclid on file from a prior Facebook touchpoint. Sparkforge sends the event using the most recent attribution data.