The Meta Pixel runs in the visitor's browser, so ad blockers, browser privacy features, consent choices and iPhone tracking limits can stop it reporting conversions. The Conversions API (CAPI) sends the same events from your server or CRM directly to Meta. Running both, with deduplication, gives Meta fuller data to measure results and find more buyers.
Missing conversions cost you twice. Your reports understate what ads achieve, so you may switch off campaigns that work. And Meta's delivery system, which learns from the conversions you report, has less to learn from. This explainer covers how CAPI works, what it fixes, what it doesn't, and how to set it up without a big project. It's one part of the tracking layer described in our guide to performance marketing in 2026.
Why does the Pixel miss conversions now?
Because more and more of the browser environment it depends on is blocked, restricted or cleared. The Pixel is a piece of JavaScript that fires when someone views a page or completes an action. If the script doesn't load or its cookies don't survive, the conversion isn't reported.
The usual culprits:
- Ad and tracker blockers that stop Meta's script loading at all.
- Browser privacy features such as Safari's Intelligent Tracking Prevention and Firefox's tracking protection, which limit how long cookies last or block third-party trackers.
- Apple's App Tracking Transparency on iPhones, which since iOS 14.5 has required apps to ask permission before tracking users across other companies' apps and websites.
- Consent banners, where visitors in many regions decline marketing cookies.
- Slow pages and quick exits, where someone submits a form and leaves before the Pixel fires on the thank-you page.
- In-app browsers inside Facebook and Instagram that behave differently from a normal browser.
None of this is unusual or a sign of a broken setup. It's simply how the web works now.
What exactly is the Conversions API?
CAPI is a direct, server-to-server connection that lets your website, store or CRM tell Meta about a conversion without relying on the visitor's browser. When a form is submitted or an order is placed, your server sends Meta a message describing the event.
Each event typically includes:
- Event name (Lead, Purchase, CompleteRegistration, or a custom event).
- Event time.
- Customer information, such as email or phone number, hashed (scrambled one-way) before sending so the raw details aren't exposed.
- Technical details like IP address, browser user agent and Meta's click identifier when available.
- An event ID used to avoid counting the same conversion twice.
- Value and currency for purchases.
Meta matches the hashed details against its users to connect the conversion to someone who saw or clicked your ad.
Pixel only, CAPI only, or both?
Run both. The Pixel captures browser behaviour well; CAPI fills the gaps and adds events the browser never sees.
| Setup | Strengths | Weaknesses | Verdict |
|---|---|---|---|
| Pixel only | Easy to install; tracks page views and on-site behaviour | Misses events when blocked, declined or interrupted | No longer enough on its own |
| CAPI only | Reliable server events; can include CRM and offline outcomes | Loses some browser signals that help matching and remarketing | Workable but incomplete |
| Pixel + CAPI with deduplication | Fullest data; best matching; supports CRM feedback | Slightly more setup and testing | Meta's recommended approach |
How does deduplication work?
When the Pixel and CAPI report the same conversion, they share an event name and event ID, and Meta keeps only one. Without that shared ID, a single lead can be counted twice, which flatters your results and confuses optimisation.
In practice your developer generates a unique ID when the conversion happens (for example, the form submission ID), passes it to the Pixel event in the browser, and sends the same ID with the server event. Meta's Events Manager shows whether deduplication is working.
If your reported conversions suddenly double after adding CAPI, deduplication is almost certainly the issue. Fix it before trusting any numbers.
What is Event Match Quality, and how do you improve it?
Event Match Quality is a score in Events Manager that estimates how well your server events can be matched to Meta users. Better matching means more conversions attributed to the right ads and better signals for optimisation.
To raise it, send more of the identifiers you legitimately collect:
- Email address and phone number (hashed).
- First and last name, city and postcode, where collected (hashed).
- Your own customer or lead ID (sent as an external ID).
- Meta's browser and click identifiers (stored in first-party cookies when available).
- IP address and user agent from the original request.
Only send what you collected with appropriate consent. More data isn't worth a privacy breach.
How do you set up CAPI?
Pick the lightest option that covers your events: a platform integration if you use a supported store or website builder, a gateway or server-side tagging if you want control without much code, or a direct integration for custom sites and CRMs.
| Option | How it works | Effort | Best for |
|---|---|---|---|
| Platform integration | Built-in connection in platforms such as Shopify or plugins for WordPress and WooCommerce | Low | Standard online stores and sites on supported platforms |
| Conversions API Gateway | Meta's hosted or self-hosted gateway that mirrors Pixel events server-side | Low to medium | Businesses wanting server events without custom code |
| Server-side tag manager | Events pass through a server container you control before going to Meta and others | Medium | Teams already using a tag manager and multiple ad platforms |
| Direct API integration | Your developer sends events from your backend or CRM | Medium to high | Custom websites, web apps, lead businesses with a CRM |
A direct integration is usually a scoped piece of development rather than a large project, especially if your site already records form submissions in a database. Ask for a fixed quote that includes deduplication and testing, not just "sending events".
Why does CAPI matter even more for lead generation?
Because the event that matters most, a lead becoming a customer, happens in your CRM or on the phone, where no Pixel can see it. CAPI lets you send those later outcomes back to Meta.
A typical setup for a service business:
- A lead arrives from a website form or a Meta instant form.
- Your team qualifies it and updates its status in your CRM.
- Your system sends a server event to Meta, such as "qualified lead" or "converted", with the lead's identifiers.
- Meta can then optimise lead campaigns towards people who resemble your qualified leads rather than anyone who fills in a form.
This is where cheap-but-poor leads start to improve. Our comparison of Meta lead form ads and messaging ads explains why form volume alone can mislead.
We built our own Ops Console with a lead centre that pulls in website form submissions and Meta lead-ad enquiries automatically, next to a CRM pipeline. Having every lead and its status in one system is what makes sending outcomes back to Meta straightforward. If your leads live in WhatsApp chats and notebooks, start by getting them into one place; our guide to tracking website leads covers the basics.
What about privacy and consent?
CAPI doesn't exempt you from privacy law; it moves data from your server instead of the browser, so you're responsible for collecting and sharing it lawfully. Treat it as you would any other transfer of customer data.
Good practice:
- Update your privacy policy to explain that you share conversion data with advertising platforms.
- Respect consent choices: if a visitor declines marketing tracking, don't send their data server-side either.
- Hash personal identifiers before sending (many integrations do this automatically).
- Never send sensitive information such as health details or financial account data.
- Follow the laws that apply to you: India's DPDP Act 2023, Australia's Privacy Act 1988, GDPR in Europe, and state privacy laws in the USA.
How do you check it's working?
Use Events Manager's test tools before launch, then review the overview weekly.
- Test Events: trigger a test conversion and confirm it arrives from both browser and server.
- Deduplication status: check that matching events are being merged.
- Event Match Quality: aim to improve it over time by adding identifiers you already collect.
- Event volume: compare server and browser counts; big unexplained gaps suggest a problem.
- Diagnostics: fix warnings about missing parameters or formatting.
If you use Advantage+ campaigns, accurate events matter even more, because the automation relies entirely on the signals you send. Our explainer on when to use Meta's Advantage+ AI targeting covers that side.
Frequently asked questions
Will CAPI lower my cost per lead?
It may, but there's no guaranteed improvement. CAPI mainly gives Meta more complete conversion data, which can improve both reporting and optimisation. The bigger gains usually come when you send qualified-lead and sale events from your CRM.
Do I still need the Meta Pixel if I use CAPI?
Yes, in most cases. The Pixel captures browser-side behaviour such as page views and supports remarketing audiences, while CAPI makes conversion reporting more reliable. Meta recommends running both with deduplication.
Is CAPI only for e-commerce?
No. It's especially useful for lead generation, because you can report what happens after the lead, such as qualification or a signed contract, which a browser pixel can never see.
Does CAPI get around ad blockers and consent rules?
It avoids technical blocking because events go from your server, but it doesn't override a person's privacy choices. If someone declines marketing tracking, you should respect that in your server events too.
How long does a CAPI setup take?
A platform integration can be switched on in an hour or two. A gateway or server-side tagging setup often takes a few days including testing, and a custom CRM integration can take longer depending on your systems.
Get your tracking right first
Better ads start with accurate data about who actually converts. If you'd like help connecting your site or CRM to Meta's Conversions API, with deduplication and consent handled properly, request a fixed-price quote.