What is the Meta Conversions API?
The Meta Conversions API sends conversion events to Meta from your server or CRM. What it does, why B2B teams use it, and the mistakes to avoid.
The Meta Conversions API is a way to send conversion events to Meta from your own server or CRM, instead of relying only on the Meta Pixel in the visitor's browser. It can run alongside the Pixel or in place of it.
Why it exists
- Browsers limit the Pixel. Ad blockers, browser privacy features and consent choices can stop browser events from reaching Meta.
- Real results happen later. For a B2B company, the valuable events (a qualified lead, a closed deal) happen in the CRM days or months after the ad click, long after the Pixel has stopped watching.
Pixel and Conversions API together
Most setups send each event both ways: from the browser through the Pixel, and from the server through the Conversions API. Meta needs to know both messages describe one event, so each carries the same event name and an event_id. Meta then counts it once. Without that matching, the same conversion can be counted twice, which is a quiet version of the double-counting problem.
Telling Meta who converted
To connect a server event to the person who saw the ad, you send customer information such as email address or phone number, hashed before it leaves your system. Better matching helps Meta attribute the event and learn who converts. Only send information you have a lawful basis and consent to use.
Sending CRM stages, not just leads
The most useful use for B2B is sending later stages back: a lead that qualified, a deal that closed, with a value. Meta can then optimise toward the people who turn into customers, not the people who simply fill in a form. It depends on keeping the ad click ID or a matching email on the CRM record, which is the same groundwork as offline conversion tracking.
Common mistakes
- Sending events from both the Pixel and the API with no deduplication.
- Naming events differently on each side, so they never match.
- Sending only top-of-funnel events, so Meta optimises for cheap leads.
- Ignoring consent, and sending data the visitor declined to share.
We build this alongside the rest of the tracking when we run Meta and Facebook Ads. See the tracking side on our GA4 and Tag Manager page.
Questions people ask
Is the Meta Conversions API a replacement for the Pixel?
Not necessarily. Many setups use both, with deduplication, so events lost in the browser are still captured on the server.
Does the Conversions API need a developer?
Some setups use a Tag Manager server container or a partner integration, and others need custom code. The right route depends on your stack.
Can I send CRM deal stages to Meta?
Yes. That is one of the most useful B2B uses, provided each CRM record keeps the ad click ID or matching customer details.
See which Meta leads became customers.
The audit reconciles Meta's reported conversions with the leads and deals in your CRM.
Get the free audit