Menu
  1. Services
  2. Case studies
  3. Method
  4. Pricing
  5. About
  6. Contact

More pages

Get my free audit

Blog · Guide

Meta Conversions API: what it is and why the pixel isn't enough

By Published 5 min read

Short answer

The Conversions API (CAPI) sends your sales and leads to Meta from a server, alongside the browser pixel. It recovers events the pixel loses to ad blockers or load errors, and with a shared event_id Meta counts each one once. You can set it up with no code in Events Manager, through a partner or with server-side GTM.

What is Meta’s Conversions API?

The Conversions API, or CAPI, is a connection that sends your business events to Meta from a server: purchases, leads, sign-ups, payments. The pixel does the same thing from your visitor’s browser. The API does it from your store, your tagging server or your CRM.

Meta describes it as a direct connection between your marketing data and its optimization systems, and it works for web, app, offline and messaging events, per its help page on the API. To Meta, an event that comes in through the API gets processed like a pixel event: it’s used for measurement, reporting and optimization, as the developer docs explain.

In the accounts I manage, I set it up before launching any conversion campaign. If Meta optimizes on incomplete data, it goes looking for people like the ones that got recorded, and those aren’t always the ones who buy.

Why does the pixel alone lose data?

The pixel needs the browser to load a script and let it send info to Meta. That breaks more often than you’d think:

  • Ad blockers and browsers with tracking protection, which cut off the script or the request.
  • Load and connection errors: the person closes the tab before the thank-you page loads, or the network drops right then.
  • Sales that never touch the browser: a subscription that renews, a payment confirmed hours later or a sale closed over the phone.

Meta says it in its help center: API data is less affected than pixel data by browser loading errors, connectivity issues and ad blockers. It also points out that the API lets you optimize for actions that happen later, like subscriptions, in-store sales or customer scores.

How does Meta avoid counting the same sale twice?

Meta recommends a redundant setup: the pixel and the API send the same events. That means you have to deduplicate, or every purchase gets counted twice and your ROAS looks better than it is.

Meta’s recommended method uses two fields, per its deduplication guide:

  1. The pixel’s eventID has to match the server event’s event_id.
  2. The event name has to be the same in both (for example, Purchase).

If both arrive within 48 hours, Meta drops the duplicate and, when the content is similar, keeps whichever one it got first. For a purchase, the ideal event_id is the order number. For a lead with no number of its own, a random ID works, as long as the browser and the server send the same one.

How deduplication works
  1. 1Purchase creates order 1234
  2. 2Pixel sends Purchase with eventID 1234
  3. 3Server sends Purchase with event_id 1234
  4. 4Meta counts one purchase

There’s a second method using the fbp cookie or an external_id, but Meta warns it’s weaker: it generally only deduplicates when the browser event arrives before the server event. That’s why I always use event_id. If you want the short definition, it’s in the glossary.

What is Event Match Quality, and how do you raise it?

An event helps optimization when Meta can link it to a Facebook or Instagram account. Event Match Quality (EMQ) measures exactly that. Meta calculates a score from 0 to 10 based on the customer info you send with each server event and how many of those events it manages to match. It uses the last 48 hours, per its Event Match Quality page.

That same page ranks the data by priority:

Priority Customer info
High Email, click ID (fbc)
Medium Phone, external ID, browser ID (fbp), country, date of birth, Facebook Login ID
Low First name, last name, city, zip code, lead ID

One rule gets broken a lot. Email, phone, name and location go hashed with SHA-256, while fbc, fbp, IP address and user agent go unhashed, according to Meta’s parameter list. Send fbc exactly as it comes out of the _fbc cookie on your domain.

What are the setup options?

Meta compares three routes on its setup options page, and I add a fourth that I use in most accounts:

Option How it works Best for
From Events Manager If you already have the pixel, Meta creates the server connection in one click, no code. Web events only. Getting started today
Partner integration Your store platform or CRM sends events through a ready-made connection. Stores on popular platforms
Direct integration Your tech team codes the API calls from your server. Custom builds
Server-side GTM A Google Tag Manager container on your own server receives each event and passes it to Meta, Google and the rest. Accounts running several platforms

Google explains that the server-side container runs on a server you control, in your own Google Cloud project or another environment, in its intro to server-side tagging. The upside I see in practice: one well-built event feeds Meta, Google Ads, TikTok, GA4 and Microsoft with the same data and the same ID.

Jean's tip

Start with the purchase or the lead, not every event. Once that event comes in through both the pixel and the API, deduplicated and with a solid match score, then I add the rest of the funnel.

What changes for you as an advertiser?

The first thing you’ll notice is that Ads Manager gets closer to what your store or CRM says, because events that used to get lost now show up. The second takes a bit longer: with fuller signals, the algorithm gets better at finding buyers, and cost per result tends to drop. Meta frames it that way in its help center without promising a number, and I won’t promise one either.

Maintenance changes too. You need to check in Events Manager that events keep arriving through both routes, that deduplication works and that the match score doesn’t drop when someone changes the site.

If you sell on WhatsApp, the API has a version for messaging events, with its own click ID. I walk through it step by step in how to track WhatsApp conversions. And if you want someone to set it up and audit it, that’s part of my measurement and tracking service. You can also grab a free audit and I’ll tell you what your pixel is missing right now.

FAQ

Does the Conversions API replace the Meta pixel?

You shouldn't swap one for the other. Meta recommends running both (it calls this a redundant setup) and deduplicating events with the same event_id. The pixel adds browser signals, and the API covers what the pixel misses.

What happens if I send the same purchase through the pixel and the API?

If both events have the same name and the same event_id, and they arrive within 48 hours, Meta keeps one. Without an event_id, the purchase can get counted twice.

What's a good Event Match Quality score?

Meta scores it from 0 to 10 using the last 48 hours of data. Meta doesn't set a minimum. What helps is sending more customer info (email, click ID, phone) and watching the score go up in Events Manager.

Can the Conversions API track people who rejected cookies?

No. Meta says the API isn't designed to get around policies like iOS App Tracking Transparency or European privacy rules. It has to respect consent the same way the pixel does.

Do I need a developer to set it up?

Not always. If you already have the pixel, Meta lets you turn it on from Events Manager with no code, and many store platforms have it built in. A direct integration or server-side GTM does need someone technical.

Sources

  1. About Conversions API, Meta Business Help Center
  2. Conversions API, Meta for Developers
  3. Handling Duplicate Pixel and Conversions API Events, Meta for Developers
  4. About event match quality, Meta Business Help Center
  5. Customer Information Parameters, Meta for Developers
  6. Compare Conversions API setup options, Meta Business Help Center
  7. An introduction to server-side tagging, Google for Developers

Want this working in your account?

I start with a free audit: I review your account and your tracking, and tell you what I'd change first.

Get my free auditSee: Measurement & tracking

Keep reading