Meta Conversions API Explained: How It Works With the Pixel

Your agency says "set up CAPI" and Meta keeps prompting you to do it. Here's what the Meta Conversions API is, how it sits next to the Pixel, and how duplicate events are handled.

Ömer S. Ekinci
CEO, Oxford Impulse
Published
4 min read

If your agency has asked you to “set up CAPI”, or Meta Ads Manager keeps nudging you to connect it, it helps to know what you’re agreeing to before you say yes, and what it doesn’t do.

The short answer

The Meta Conversions API is a way for your server, ecommerce platform or CRM to send events straight to Meta, instead of relying only on the browser. Meta recommends running it alongside the Meta Pixel, and when both send the same event, deduplication stops it being counted twice[1][2].

What the Conversions API is

The Conversions API (CAPI) sends events from a system you control to Meta. Those events can come from your website, your app, physical stores or messaging conversations. The sender can be your server, your ecommerce platform or your CRM (customer relationship management system)[1].

Each event is linked to a dataset ID, and Meta treats it like an event sent by the Pixel[1]. So a Purchase from CAPI is still a Purchase. It just took a different route to get there.

That route is the point. The Pixel is code that runs in the visitor’s browser. CAPI is a connection between servers. This is what people mean by server-side tracking for Meta.

Watch out

Nothing in the Meta pages we used says CAPI replaces the Pixel. The guidance is to use them together.

Why run it alongside the Pixel

Meta recommends running the API alongside the Pixel for the best ad performance[2]. Meta’s Business Help page adds the reasoning: data sent through the API is less affected than Pixel data by browser errors, connectivity issues and ad blockers, and it suggests you also use the Pixel[5].

Think of it as two routes for the same information. If the browser route is disrupted, the server route may still carry the event, and the Pixel remains in place alongside it.

We’re not going to promise what this does to your results. Meta’s pages describe the setup it recommends. They don’t give you a number to expect, and neither should anyone selling you the setup.

If you work with Google as well, the equivalent idea there is covered in our guide to enhanced conversions for web at https://oxfordimpulse.com/enhanced-conversions-for-web-setup/ .

How deduplication works

Run both routes and the same purchase can arrive twice: once from the browser, once from the server. Deduplication is how Meta recognises that these are one event, not two. It’s needed whenever you send the same event through both the Pixel and the API[2].

The main method: event ID

Give each event an ID on both sides. The Pixel’s eventID must equal the server’s event_id, and the event names must match too[2]. If they do match, the event received first is generally the one Meta keeps[2].

In practice, generate one ID when the action happens (for example an order number), then pass that same value to the Pixel call and to your server payload. If your platform has a built-in Meta integration, check how it sets these IDs rather than assuming it does.

The 48-hour window

Events are deduplicated only if they’re received within 48 hours of the first event carrying that event_id[2]. A server event that turns up three days after the browser one won’t be matched.

The fallback key

There’s an alternative: event_name plus fbp and/or external_id. This works mainly when the browser event arrives first, within the past 48 hours[2]. Treat it as a fallback. The event ID method is the one to aim for.

Tip

After you connect CAPI, test one purchase and confirm in Events Manager that it is not counted twice before you trust the setup.

The stated limits

Meta’s “Using the API” page sets out the boundaries[3]:

  • Up to 1,000 events per request.
  • An event_time can be up to 7 days old. If any event is older, the whole request errors and no events in it are processed.
  • Send events as they happen, ideally within an hour.
  • Offline store events can be sent within 62 days.
  • The page says there is no specific rate limit.

The 7-day rule deserves attention. If you batch events and one is too old, you lose the entire request, not just that event. Keep batches small enough to inspect and send them promptly.

What you need to start

Two things. A secure access token, which Meta recommends generating in Events Manager, and your dataset ID[4]. Older pages call the dataset ID the Pixel ID, but it’s one identifier, not two separate requirements[4].

If a developer builds the connection, give them the token securely and treat it like a password.

FAQs

What is the Meta Conversions API?

It’s a way to send website, app, offline and messaging events from a server, platform or CRM to Meta. The events are linked to a dataset ID and treated like Pixel events[1].

Does the Conversions API replace the Meta Pixel?

No. Meta recommends running the API alongside the Pixel[2]. Its Business Help page also suggests using the Pixel in addition to the API[5].

Why does Meta recommend using both?

API data is less affected than Pixel data by browser errors, connectivity issues and ad blockers[5]. Running both gives events two ways to reach Meta.

What is deduplication in the Conversions API?

It’s how Meta avoids counting the same event twice when it arrives through both the Pixel and the API. If the events match, the one received first is generally kept[2].

How do I match Pixel and server events?

Make the Pixel eventID equal the server event_id, and use the same event name on both[2]. Generate the ID once per action and pass it to both routes.

How long does Meta wait to deduplicate events?

Events are deduplicated only if received within 48 hours of the first event with that event_id[2]. Anything later isn’t matched on that basis.

What if I don’t have an event ID?

The alternative is event_name plus fbp and/or external_id. It works mainly when the browser event arrives first, within the past 48 hours[2].

Are there limits on Conversions API requests?

Yes. A request can hold up to 1,000 events, and event_time can be up to 7 days old, otherwise the whole request errors and nothing is processed[3]. Meta’s page says there is no specific rate limit[3].

Where to go from here

Start by checking whether your Pixel already sends an event ID, then confirm your platform or developer passes the same value server-side. Generate your access token in Events Manager and test one order end to end. For more on how we approach paid social, see our Meta Ads page at https://oxfordimpulse.com/meta-ads/ .

Sources

Share this article

Written by

Ömer S. Ekinci

CEO, Oxford Impulse Google Partner

Ömer S. Ekinci is the director of Oxford Impulse, a London-based Google Partner agency. He works hands-on in Google Ads, Meta Ads and Google Merchant Center accounts for e-commerce, healthcare and B2B brands across the UK, Europe and the US.

Free audit

Want a second pair of eyes?

Get a free audit and a clear list of what to fix first.

Get a free audit
0% read 4 min left

Meta Conversions API Explained: How It Works With the Pixel

Get a free audit