Conversions API vs Meta Pixel: Differences, Deduplication and Why You Need Both
"Should I use the Conversions API or the Meta Pixel?" is one of the most searched questions about Meta tracking. The short answer is both. The useful answer is why — and how to run them together without counting every sale twice.
The one-line difference
The Meta Pixel is JavaScript in the visitor's browser. It reports what happens on your web pages: page views, button clicks, add-to-cart, form submissions.
The Conversions API (CAPI) is a server-to-server connection. It reports what happens in your business: a lead created in the CRM, a deal marked as won, an order paid by bank transfer.
For the bigger picture of what CAPI is and why Meta pushes it, see What Is Meta Conversions API.
Side by side
| Meta Pixel | Conversions API | |
|---|---|---|
| Runs in | Browser | Server, CRM or integration |
| Affected by ad blockers, iOS, cookie limits | Yes | No |
| Sees on-page behavior | Automatically | Only what you send |
| Sees CRM stages, phone and offline sales | No | Yes |
| Event time limit | Real time only | Up to 7 days after the event |
| Customer data for matching | Cookies, plus advanced matching if enabled | Hashed email, phone, name, IP, user agent, click IDs, external ID |
| Setup effort | Minutes | From minutes (ready integration) to weeks (custom code) |
Why not just pick one?
Pixel only: you lose events to ad blockers and browser privacy features, and you never report sales that close outside the website. Meta optimizes on a partial, skewed sample.
CAPI only: possible, but you lose the cheap, automatic on-page signals (views, scroll depth, add-to-cart) unless you rebuild them on the server. You also lose the browser cookies (_fbp, _fbc) that help matching — unless your integration captures them.
Both: the pixel covers behavior on the site, CAPI covers what the pixel misses and everything after the site. Meta merges them into one stream, as long as you deduplicate correctly.
How deduplication works
When the same event arrives from both the browser and the server, Meta needs to know it's one event. It decides using:
- the same
event_namein both copies (for example,LeadandLead— notLeadandlead_form), and - the same
event_idin both copies, or the sameexternal_idandfbp.
Meta recommends sending all of these. In practice, event_id is the one that does the work: you generate a unique ID when the event happens, pass it to the pixel (fbq('track', 'Lead', {}, {eventID: 'abc123'})) and send the same ID from the server.
The mistakes we see most often
- Different event names. The pixel sends
Purchase, the server sendspurchaseorOrder. No deduplication, double counting. - A new event_id on each side. The site generates one ID, the server generates another. Same result.
- Sending a CRM event that the pixel never saw — under the same name as a pixel event. For example, the pixel fires
Leadon form submit, and the CRM also sendsLeadwhen the manager creates the deal, with a different ID. Meta sees two leads. Better: keepLeadfor the form, and use a different event for each CRM stage (Schedulefor a booked meeting,Purchasefor a paid deal, a custom event for anything else). - Missing customer data on the server side. If CAPI sends only an event name with no email, phone or click ID, Meta can't match it to a person, and it adds little value.
- Delayed batches older than 7 days. One stale event makes Meta reject the whole batch.
A simple setup that works
- Pixel:
PageView,ViewContent, andLeadon form submit — with anevent_id. - CAPI from the site: the same
Leadwith the sameevent_id, plus hashed email/phone and thefbc/fbpcookies. - CAPI from the CRM: later stages under their own names —
Schedulewhen a meeting is booked,Purchasewith the deal value when it's paid.
This is exactly the pattern LeadMe implements. Its site script captures the click IDs and cookies with the form, and the CRM connection sends each deal stage you choose as its own event, so nothing is double-counted and Meta finally sees which leads turn into money.
How to check deduplication in Events Manager
- Open the event (for example,
Lead) in Events Manager → Overview. - Look at the connection method: you should see both Browser and Server.
- Check the deduplication indicator. If Meta reports most server events as duplicates of browser events, it's working. If the server count simply adds to the browser count, your IDs or names don't match.
Quick answers
Does the Conversions API replace the pixel?
No. Meta recommends running both. CAPI fills the gaps the pixel can't cover.
Will my numbers in Ads Manager go up after adding CAPI?
Usually, yes — because events that were lost are now counted. If they roughly double overnight, check deduplication first.
Is "Conversions API and Meta Pixel" the same as "Conversions API Gateway"?
No. The Gateway is one way to run CAPI, mirroring pixel events through your own cloud server. See Conversions API Gateway: cost and alternatives.
Related: System user and access token for CAPI · How to send CRM sales to Meta