Analytics and Tracking

Conversions API

Also called CAPI

A direct server-to-platform connection for reporting conversions, used alongside the browser pixel rather than instead of it.

Quick facts: Conversions API

Category
Analytics and Tracking
Also called
CAPI
Level
Advanced
Affects
Event completeness, bidding signals, reported cost per acquisition
Where to see it
Meta Events Manager, server-side Google Tag Manager, ecommerce platform integrations
In this article4
  1. How the Conversions API works
  2. Why the Conversions API matters
  3. Common mistakes with the Conversions API
  4. How to act on it

How the Conversions API works

A browser tag reports a conversion from the visitor’s device. The Conversions API reports the same conversion from your own systems — your website’s server, your ecommerce platform, your CRM, or a server-side tag container sitting between them. The event travels over a direct, authenticated connection to the advertising platform, so nothing about it depends on the visitor’s browser, connection or extensions.

Because the send comes from your side, you can attach information the browser never had. Meta’s version, usually written CAPI, accepts customer details such as email and phone in hashed form so the platform can match the event to an account. You can also send events that never touch a web page at all: an order confirmed by phone, a deal marked won in the CRM, a refund.

The important design point is that both sends are meant to coexist. The browser and the server report the same action, each carries the same event ID, and the platform uses that shared reference to count one conversion rather than two.

Why the Conversions API matters

Browser-reported events go missing for reasons you cannot control — blockers, closed tabs, cookie limits, a mobile connection that drops before the request completes. Every missing event is both an under-reported result and a signal the campaign never learned from. Automated bidding is trained on the conversions it is told about, so patchy reporting produces patchy optimisation, and the account quietly bids as though your best customers do not exist.

It also lets the platform learn from what actually happened rather than what happened on the website. If half your enquiries turn out to be unusable, sending only the qualified ones back through the API teaches the campaign to chase the good ones.

Common mistakes with the Conversions API

Turning off the browser pixel after connecting the API is the classic error. The two sources cover different gaps and the platform expects both. Sending events without a shared identifier is the next one, because the result is silent double counting that makes cost per acquisition look far better than it is — deduplication only works when both copies agree on the event name and the identifier.

The rest are process failures. Customer fields sent without hashing or without normalising them first. Consent ignored on the assumption that a server send is outside privacy rules, which it is not. And nobody watching the connection afterwards, so an integration that breaks during a site update goes unnoticed until the monthly report looks wrong.

How to act on it

Decide first which events genuinely need it: purchases and qualified leads, not every button click. Agree where each will be sent from, generate one identifier per action at the moment it happens, and reuse that same identifier on both the browser and server copies. Then verify in the platform’s event tools that the events arrive and are reported as deduplicated before you trust any number built on them.

Most businesses reach this point through a pixel and Conversions API implementation rather than building from scratch, because the work is less about code than about agreeing what counts as a conversion and keeping it working afterwards.

Do and do not

Do

  • Send browser and server copies with one shared event ID
  • Hash and normalise customer fields before sending them
  • Check the platform reports events as deduplicated

Do not

  • Switch off the browser pixel once the API works
  • Send personal fields without consent or hashing
  • Leave the connection unmonitored after launch

Questions people ask about this

Do I still need the pixel if I have the Conversions API?

Yes. The two are designed to run together and each catches events the other misses. The browser pixel captures on-page behaviour and gives the platform browser-level signals; the server send survives blockers and closed tabs. Removing the pixel usually reduces the total number of matched events rather than tidying anything up.

Will the Conversions API get my reported conversions back to what they were?

It recovers some of what browser tracking loses, but nobody can promise a specific recovery and the size depends entirely on your audience and setup. Treat it as improving the signal you send to bidding and the completeness of your reporting, then compare like with like over a full reporting period before drawing conclusions.

Is sending customer data through the API a privacy problem?

It can be, so handle it deliberately. Personal fields must be hashed before they leave your systems, you need a lawful basis and a consent position that covers the send, and your privacy policy should describe it accurately. Send only the fields that genuinely improve matching, and stop sending data for anyone who has refused.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.