The Meta Conversions API (CAPI) sends conversion events, like leads and purchases, from your server straight to Meta instead of relying only on the browser Pixel. Ad blockers and browser privacy settings cannot block it the same way. Meta recommends running it alongside the Pixel, with matching event IDs, so conversions are not counted twice.
- Meta reports that advertisers with a Conversions API setup saw an average 17.8% lower cost per result (April 2026).
- About 32.5% of US internet users run an ad blocker, which can stop the Pixel (GWI, 2025).
- Use the Pixel and CAPI together, and give both the same event_id so Meta counts each conversion once.
- Hash email, phone and name with SHA-256 before sending. Do not hash IP, user agent, fbp or fbc.
What is the Meta Conversions API?
The Conversions API is a direct connection between your server, or a tool your server uses, and Meta. When someone fills out your form or buys, your server tells Meta what happened. The Meta Pixel does the same job from the visitor’s browser. Using both gives Meta a more complete picture.
Pixel vs Conversions API
| Meta Pixel | Conversions API | |
|---|---|---|
| Where it runs | Visitor’s browser | Your server |
| Blocked by ad blockers? | Often | No |
| Affected by browser privacy settings? | Yes | Much less |
| Setup effort | Paste a code snippet | Partner integration, one-click or developer |
| Can send offline or CRM events? | No | Yes |
Why browser tracking breaks
Add Apple’s App Tracking Transparency, which most iPhone users decline, plus browsers that limit cookies, and a real share of your leads never reaches Meta through the Pixel. Meta then thinks the ad did not work and shows it to the wrong people.
Why small businesses need it
This is Meta’s own average, not a controlled test, so your result will differ. The mechanism is simple: Meta can only optimize on conversions it can match to a person. More matched conversions means better delivery.
How the Pixel and CAPI work together
Meta recommends what it calls a redundant setup: send the same events through both the Pixel and the Conversions API. If the browser event is blocked, the server event still arrives. If both arrive, Meta keeps one.
How deduplication works
- 1Your site creates a unique ID for each event, for example lead_10452.
- 2The Pixel sends the Lead event with eventID = lead_10452.
- 3Your server sends the Lead event with event_id = lead_10452 and the same event_name.
- 4Meta sees two events with the same name and ID within 48 hours and counts one conversion.
Event Match Quality explained
Event Match Quality is a score out of 10 in Events Manager that shows how well Meta can match your server events to real people. More, and better, customer information means a higher score.
| Parameter | Hash with SHA-256? |
|---|---|
| Email, phone, first and last name | Yes |
| City, state, zip, country | Yes |
| External ID (your customer ID) | Recommended |
| IP address, user agent | No, send as is |
| fbp and fbc cookies | No, send as is |
How to set it up: pick your path
| Your situation | Best option |
|---|---|
| Shopify, WooCommerce or another big platform | The official partner integration |
| Simple website, web events only | Meta’s one-click Conversions API in Events Manager |
| Need CRM, phone or offline events | Conversions API Gateway, server-side tagging or a custom setup |
Meta’s one-click option, launched in 2026, is free and hosted by Meta, but it mirrors what the Pixel sees. It cannot send events the browser never fired, like a lead that was qualified later in your CRM.
How to check it is working
- Events Manager → Test Events: submit your own form and watch both the browser and server event arrive.
- Check that the events show as deduplicated, not double-counted.
- Watch Event Match Quality and Event Coverage for a week.
Privacy and consent basics
Tell visitors in your privacy policy that you use the Pixel and the Conversions API to measure ads, which data is shared and how to opt out. If you have visitors from the EU or from US states with privacy laws, respect their consent choices on both the browser and the server side.
Frequently asked questions
Yes. Meta recommends using both with matching event IDs. The Pixel captures browser signals; the Conversions API fills the gaps when the Pixel is blocked.
Not if both send the same event_name and event_id. Meta deduplicates matching events received within 48 hours.
Meta scores it out of 10 and says higher matching quality produces better results. Send hashed email and phone plus IP, user agent, fbp and fbc to raise it.
Server events are not blocked by ad blockers. They still depend on matching the event to a person, so sending good customer information matters.
If you spend money on Meta ads, usually yes. Meta reports an average 17.8% lower cost per result for advertisers with a Conversions API setup.
