Conversions API CAPI

Why it matters

Meta's ads learn from the events you send back: purchases, leads, bookings. The browser Pixel sends them from the visitor's browser, which can be blocked by ad blockers, privacy settings or a page that closes too soon. The Conversions API sends the same events from your server, so they arrive even when the browser does not report them. Meta's documentation recommends using both together, with matching event IDs so that duplicates are removed.

It also lets you send things the browser never sees: a lead marked qualified in your CRM, an appointment that was attended, a payment confirmed days later. That is the difference between optimising for form fills and optimising for patients, students or buyers.

How to set it up well

1. Choose a route. A partner integration from your platform (Shopify, a CMS), a server-side GTM container, or direct calls from your backend.
2. Send the same event names as the Pixel, with a shared event_id so Meta can deduplicate.
3. Pass customer information parameters such as hashed email and phone, only where you have consent. Better matching improves how often Meta can connect an event to a person, which Events Manager reports as Event Match Quality.
4. Send offline and CRM stages that mark a lead as qualified or won.
5. Test in Events Manager and watch the deduplication and matching diagnostics, not just "events received".

Common mistakes

• Sending events twice without an event ID, which inflates results.
• Ignoring consent. Server-side does not mean consent-free.
• Sending only the top of the funnel.
• Setting it up once and never checking it.

This is core work in BridgeE's Meta Ads and GTM engineering services.