Meta Ads (CAPI) Integration

What is Meta CAPI?

Meta Conversions API (CAPI) is a server-to-server integration that sends conversion events directly from Convertly’s server to Meta, bypassing browser-based pixel limitations caused by ad blockers, iOS privacy changes, and cookie restrictions.

When a lead marked as Closed Won has a fbclid (Meta click ID), Convertly dispatches a CAPI Purchase event to your Meta ad account.

What this enables

Meta receives a verified conversion signal tied to the original click
Your attribution is more accurate — not reliant on browser pixel fires
Meta’s optimization algorithm uses the signal to improve campaign targeting
You can see these events in Meta Events Manager → Server Events

Setting up Meta CAPI

Go to Settings → Ads Attribution → Meta Ads
Enter your Meta Pixel ID
- Find this in Meta Events Manager → Data Sources → your Pixel → Settings
Enter your Conversions API access token
- In Meta Events Manager → your Pixel → Settings → Conversions API → Generate access token
Select the conversion stage — the pipeline stage that triggers the CAPI event (usually “Closed Won”)
Click Save
Test by closing a lead with a known fbclid value and checking Meta Events Manager for the incoming server event (allow up to 15 minutes for events to appear)

Event details

Convertly sends the following event payload:

Field	Value
`event_name`	`Purchase`
`fbclid`	Captured from the lead’s form submission
`event_time`	Unix timestamp when the stage change occurred
`action_source`	`crm`
`user_data.fbc`	Formatted fbclid value

Meta Lead Form webhook (inbound)

Convertly also supports inbound Meta lead form submissions via Meta’s Lead Ads webhook:

A prospect fills out a Meta Lead Form ad
Meta sends the submission to Convertly’s webhook endpoint
The lead is created in your CRM automatically
meta_leadgen_id is stored on the lead for attribution

To set up the inbound webhook, contact support for your webhook endpoint URL and verification token — this requires configuration in your Meta Business Manager.

Troubleshooting

Issue	Check
No events appearing in Meta Events Manager	Verify the Pixel ID and access token are correct
Events appearing but not matching	Ensure auto-tagging (fbclid appending) is enabled in your Meta Ads campaign URL settings
Events duplicated	You may have both browser pixel and CAPI sending — check for deduplication setup in Meta Events Manager