How to Set Up the Meta Conversions API (CAPI): A Practical Guide

The Meta Conversions API (CAPI) sends conversion events server to server, so you keep tracking when the browser pixel is blocked by iOS, ad blockers, or consent tools. To set up Meta CAPI you connect your existing pixel or dataset to a server-side source, send the same events you already track in the browser, and deduplicate them so nothing is double counted. Here is what you need and the main ways to do it.

What is the Conversions API, and why is the browser pixel not enough?

The browser pixel fires from the visitor's device. That means anything between the browser and Meta can stop it: iOS tracking prompts, ad blockers, cookie consent tools, and network failures. When events go missing, Meta's optimization gets worse and your reported conversions understate reality.

CAPI fixes this by sending the same events from your server directly to Meta. It is not a replacement for the pixel: the two work together, with the pixel capturing rich browser signals and CAPI filling the gaps. For a deeper comparison, see Meta Pixel vs Conversions API and server-side vs browser-side tracking.

What do you need before you start?

Gather these first, because missing any one of them will stall the setup:

• A pixel or dataset. In current Events Manager, your pixel is represented as a dataset. CAPI attaches to that same dataset ID.
• Admin access. You need admin rights on the Business Manager, the ad account, and the dataset to generate access tokens and connect integrations.
• First-party customer data. Server events match to people through hashed identifiers like email, phone, name, and IP. The more you can send, the better your match rate.
• A place to send events from. Your platform, a gateway, a server-side tag container, or your own backend. The next section covers the options.

What are the main ways to set up CAPI?

1. Native partner integration. Platforms like Shopify, WooCommerce, and most major carts have a built-in Meta integration that turns on CAPI with a few clicks. Easiest path and low maintenance, but you get limited control over which events and parameters are sent.
2. Conversions API Gateway. Meta's hosted gateway sits on your domain and mirrors pixel events to the server automatically. Good middle ground with strong match quality and little code, though it carries a hosting cost and less flexibility than a full implementation.
3. Server-side Google Tag Manager. A server container gives you fine-grained control over event mapping and works across multiple destinations. Powerful and vendor-neutral, but it requires tagging expertise and a hosting environment to run the container.
4. Direct API or developer implementation. Your backend posts events straight to the Conversions API. Maximum control and the best data quality, but it is the most engineering-intensive and the most work to maintain.

Most agencies start with a native integration or the gateway, then graduate to server-side GTM or a direct build once they need custom events or cleaner data.

The step everyone gets wrong: deduplication

Once both the pixel and CAPI are live, you are sending each conversion twice. Without deduplication, Meta counts it twice and your reporting and optimization both suffer. The fix is to send a matching event_id and event_name on both the browser event and the server event for the same action. Meta uses that pair to recognize the two as one event and keep only a single copy.

Generate the event_id once per event and pass the identical value through both paths. Getting this wrong is the single most common CAPI mistake, so if your numbers look inflated after launch, start here. Our walkthrough on how to fix duplicate events between pixel and CAPI covers the failure modes in detail.

How do you confirm CAPI is working?

• Events Manager overview. Open your dataset and look at the event sources. You should see events arriving from both the browser and the server, with a “Processed” and deduplicated count that looks reasonable.
• Test Events tool. Use the test event code to fire a live action and watch it appear in real time. This confirms your server payload is well formed before you trust the production stream.
• Event Match Quality (EMQ). Check the match quality score on your key events. A healthy score means Meta is matching your server events to real people. See what counts as a good CAPI EMQ score for benchmarks.

Common mistakes to avoid

• Sending only some events server-side. Aim for full coverage of your key conversions, not just purchases.
• Skipping customer parameters, which quietly tanks your match quality and EMQ.
• Mismatched or missing event_id values, which reintroduces duplicates.
• Sending raw, unhashed personal data. Identifiers must be normalized and hashed before they leave your server.
• Treating setup as one and done. Deploys, consent changes, and platform updates all break tracking silently.

That last point is the real risk. CAPI is not something you configure once and forget: a theme update, a token expiry, or a tagging change can drop your events without any error message. Continuous monitoring catches those regressions the day they happen instead of at the end of a bad month. That is exactly what Taglert watches for you, keeping an eye on pixel health, CAPI event flow, and EMQ so a silent break never quietly drains your ad spend.