What is the Meta Conversions API?

The Conversions API, or CAPI, sends your events to Meta server to server, from your server directly to Meta, instead of only from the shopper's browser through the Pixel. Because the call does not depend on the browser, it is not lost to ad blockers, app tracking choices, or cookie limits. You run it alongside the Pixel, deduplicated, so Meta sees the conversions the browser drops.

Do I still need the Meta Pixel if I have the Conversions API?

Yes. The recommended setup is Pixel plus Conversions API together, with a shared event ID so Meta deduplicates them. The Pixel captures rich browser context; the Conversions API ensures the event still reaches Meta when the browser blocks it. Running both, deduplicated, gives the most complete and best-matched signal.

How do I avoid double-counting with the Conversions API?

Send a shared event_id on both the Pixel event and the Conversions API event for the same action. Meta uses it to collapse the two into one conversion. Without a matching event_id, every purchase counts twice and your reporting and optimization break. The shared event ID is the single most important detail in a CAPI setup.

Field Guide Tracking and analytics

Meta Conversions API: a setup guide

Q: What is the easiest way to set up CAPI on Shopify?

Turn on Maximum customer data sharing in Shopify's Facebook and Instagram channel. It enables the Conversions API alongside the Pixel, handles deduplication, and sends additional matched data, with no code. It is the fastest path and the right first step before considering a Conversions API Gateway or server-side Google Tag Manager.

The Meta Pixel alone now loses a real share of your conversions. The Conversions API recovers them, server-side. Here is how to set it up, deduplicated and matched, without double-counting.

December 2, 2025 8 min read

The Meta Pixel on its own is no longer enough. Ad blockers, app tracking prompts, and browser cookie limits now delete a real share of the events it tries to send, so Meta optimizes your campaigns on incomplete data and attributes fewer of the sales you actually made. The Conversions API recovers that signal by sending events server to server, where the browser’s limits do not reach. This Meta Conversions API setup walks through doing it properly, deduplicated and matched, so it is pure upside.

What CAPI does, in one line

The Conversions API sends your events, view content, add to cart, purchase, from your server directly to Meta, alongside the Pixel that sends them from the browser. The browser path is what gets blocked; the server path does not. Run both together, with a shared event ID so Meta merges the duplicates, and Meta sees the full picture instead of only what the browser allowed through.

The Pixel tells Meta what the browser still permits. The Conversions API tells it what actually happened.

The Meta Conversions API setup paths, simplest first

You do not have to build CAPI from scratch. This Facebook CAPI setup is a ladder, and most stores should start at the top.

Shopify Maximum data sharing

For Meta CAPI on Shopify, the fastest path is turning on Maximum customer data sharing in the Facebook and Instagram channel. It enables the Conversions API alongside the Pixel, handles deduplication, and sends additional matched data, with no code. For most stores this Meta CAPI Shopify path is the whole job, and it is the same lever that raises event match quality.

A Conversions API Gateway or partner integration

If you are not on Shopify, or you need more control, Meta’s Conversions API Gateway or an official partner integration sends server events without a full custom build. It is more setup than the native toggle, less than a from-scratch implementation.

Server-side GTM or a direct integration

For a custom stack, or to route several platforms at once, a server-side Google Tag Manager container receives each event once and forwards it to Meta’s API along with your other platforms. Most power, most setup; reach for it when the simpler paths cannot do what you need.

Get these three details right

CAPI is only as good as how it is wired. Three things make or break it.

The CAPI must-haves

A shared event_id on the Pixel and CAPI event, so Meta deduplicates them
fbc and fbp captured client-side and sent with every server event
Hashed customer data, email and phone, for advanced matching
client_user_agent and the customer IP sent server-side
Tested in Events Manager: events show both Browser and Server
Match quality checked after, to confirm the signal improved

Verify, then trust

Use Meta’s test-event tool to fire a real test purchase and confirm you see one event with both Browser and Server sources, carrying your matched data and matching event IDs. Then watch your match quality climb over the next day or two. That is the whole tracking and analytics principle in action: one event, one stable ID, the best signal you can give the platform, sent through a path the browser cannot block.

If you are spending on Meta and your conversions look thin, or you are not sure your Pixel and CAPI are deduplicating correctly, take this Conversions API guide as far as verification, because that setup and check is exactly what a short tracking audit is built to deliver.