Meta Conversions API (CAPI) is a server-side integration that sends conversion events directly from your server to Meta, bypassing the browser entirely. Instead of relying on the Meta Pixel to fire from a user's browser, CAPI sends the same purchase, lead, or custom event data through a direct API connection between your backend and Meta's systems.
The result: Meta sees more of your conversions. Not because more happened, but because fewer get lost.
How Meta Conversions API works
When a customer buys something on your site, two things can happen. A browser-based pixel tries to fire and report the event to Meta. And if you have CAPI set up, your server independently sends the same event through the API.
The browser path fails more than most brands realize. Ad blockers block it. iOS restrictions limit it. Slow connections drop it. Browser-side tracking consistently misses 20 to 40% of actual purchase events. CAPI sends the same signal from your server, where none of those variables apply.
Meta then deduplicates the two signals using an event ID you pass with each event. One conversion gets counted once. You get the coverage of server-side data without double-counting.
What Meta Conversions API actually sends
Each event sent through CAPI includes the event type (Purchase, Lead, AddToCart, etc.), a timestamp, your pixel ID, and customer information used for matching. That customer data — email, phone number, name, location — is hashed before it leaves your server. Meta uses it to match the event to a user in its system, which is what determines your match rate.
Match rate is the percentage of events Meta can connect to a real user account. Higher match rate means the platform AI can learn from more of your conversions. A CAPI implementation that sends events but sends them with weak or missing identifiers gives you the integration without the performance benefit. The event arrives. Meta just cannot do much with it.
Meta Conversions API vs the Meta Pixel
The pixel and CAPI are not alternatives. They are designed to run together. The pixel captures browser-side behavior — page views, clicks, time on site — that your server does not see. CAPI captures the high-value conversion events that the browser misses or drops.
Running both gives Meta a more complete picture of your customer journey. Running only the pixel leaves a significant portion of your conversions unreported. Running only CAPI means losing the behavioral signals the pixel captures upstream of conversion.
The right setup is both, with proper deduplication. For a detailed breakdown of how to run them together without inflating your event counts, see running a pixel and a Conversion API at the same time.
Why match rate determines whether CAPI actually works
Most brands implement Meta Conversions API and assume the work is done. The integration is live, events are flowing, and the dashboard shows activity. But implementation and performance are different things.
What Meta does with your events depends on how well it can match them to users. If you send a Purchase event with only an IP address and user agent, Meta's match rate on that event is low. If you send the same event with a hashed email, hashed phone number, and external ID, match rate is substantially higher. More matched events means more training data for Meta's optimization algorithm. That's what moves ROAS.
The practical implication: CAPI setup is not a one-time task. Match rate needs to be monitored. If it drops, the quality of your signal to Meta drops with it, and campaign performance follows. See understanding match rate for a full breakdown of what match rate is and how to diagnose drops.
What Meta Conversions API does not fix
CAPI solves the browser loss problem. It does not solve an incomplete data problem. If your checkout does not collect email addresses, CAPI cannot send what it does not have. If your CRM data is siloed from your ad platform setup, offline conversions still will not reach Meta. If events are duplicated because deduplication is misconfigured, Meta will count more conversions than actually happened.
CAPI is infrastructure. The quality of what it sends depends entirely on the quality of the data you give it to work with. For context on how Conversions API fits into a broader signal infrastructure approach, what marketers need to know about Conversions API covers the full picture across platforms.
