Ad Sync (Meta CAPI)
Send tracked conversions back to publishers' Meta pixels through the Conversions API. For network admins.
Publishers who buy traffic on Facebook/Instagram optimise better when Meta knows which clicks converted. Connect a publisher's pixel here and each of their conversions is reported to Meta automatically.
Fields and settings
| Field | What it does |
|---|---|
| Meta Pixel / Dataset ID | The publisher's pixel (dataset) ID from Meta Events Manager. |
| Event value sent to Meta | Which amount Meta sees: the publisher payout (recommended), network revenue, or no value. |
| Test event code | Optional code from Meta's Test Events tab so test sends show up there instead of in live data. |
How to use it
- Press Connect a pixel, choose the publisher and optionally one campaign (blank = all).
- Enter the pixel ID and access token, the Meta event and which value to send.
- Use Send test on the connection and check Meta's Test Events.
- Watch the Delivery log; retry failed events if needed.
Limitations
- Depends on: Only conversions whose click carried an
fbclidcan be matched to the Meta ad. - Not supported: Only Meta is supported today; Google and TikTok aren't implemented.
- Depends on: Requires the NestJS service and PostgreSQL, and the Ad Sync plan feature.
Troubleshooting
- “No sync events yet” — No converted click had an
fbclidyet. Use Send test to fire one now. - Events marked Failed — Usually a wrong pixel ID or an expired access token. Edit the connection, then Retry all failed.
Related
Was this article helpful?
Thanks for the feedback. Tell us more