Guide
How conversion tracking actually works
A plain-English breakdown of what is really happening between an ad click and a counted conversion, why most setups leak, and what a healthy one looks like.
The three layers of tracking
Modern conversion tracking is not one thing, it’s three layers that are supposed to work together:
- Client-side (the browser pixel). Fires from the visitor’s browser when they take an action. Easy to set up, and easy for browsers and ad blockers to stop.
- Server-side (the Conversions API). Sends the same events from your server directly to the platform. Browsers can’t block it, so it catches what the pixel loses.
- Offline conversions. Your real downstream outcomes, a funded loan, a bound policy, a closed sale, sent back from your CRM so the platform optimizes toward revenue, not just form fills.
Why pixel-only setups leak
Apple’s App Tracking Transparency, Safari’s Intelligent Tracking Prevention, and ad blockers all limit or strip browser-based tracking. On a pixel-only setup, that commonly means 20 to 40 percent of conversions never make it back to the platform as clean signal.
The dangerous part is that your dashboard still looks fine. It shows a cost per lead, so you keep scaling, while the platform is quietly optimizing on a partial picture of who actually converts.
Deduplication: counting each conversion once
Once you run both the pixel and the Conversions API, the same conversion can arrive twice, once from the browser and once from the server. Deduplication uses a shared event ID so the platform recognizes them as the same event and counts it once. Get this wrong and you either double-count (inflated, useless numbers) or under-count (wasted spend). Getting it right is the whole point.
Event Match Quality
Event Match Quality (EMQ) is the platform’s measure of how well it can match your events to real people, based on the customer information you send with each event (hashed email, phone, name, and so on). The stronger the match, the better it can optimize and attribute. Advertisers scaling real budget generally want to be near 7 out of 10 or higher. Many are well below that and never check.
What a healthy setup looks like
A healthy account runs all three layers, deduplicated, with strong advanced matching and a healthy EMQ, and it validates that the events actually register in the platform’s test tools rather than assuming they do. It also carries the real downstream outcome from the CRM back to the platform, so optimization is aimed at customers, not just clicks.
That is exactly what the Tracking 100 score grades, across the six signals that decide whether the platform can actually find your buyers.
Common questions
Is the Meta pixel still enough on its own?+
No. Since iOS 14.5 and browser tracking restrictions, a browser-only pixel typically loses 20 to 40 percent of conversions to iOS, Safari, and ad blockers. Server-side tracking (CAPI) is what recovers them.
What is the difference between the pixel and the Conversions API?+
The pixel runs in the visitor’s browser and is easily blocked. The Conversions API (CAPI) sends the same events from your server, which browsers cannot block. Running both, deduplicated, is the current standard.
What is Event Match Quality?+
Event Match Quality (EMQ) is Meta’s score, roughly 0 to 10, for how well it can match your events to real people using the customer information you send. Higher EMQ means better optimization. Most advertisers scaling spend want to be near 7 or above.
Want to know how yours scores?
Get your Tracking 100 score in about three minutes. No account access.