Why your Facebook pixel is undercounting conversions
If Meta reports fewer sales than you know you made, you are not imagining it. The browser-based pixel structurally cannot see a large share of conversions anymore, and the gap has only grown.
Why it undercounts
- iOS App Tracking Transparency: most users opted out, so Meta loses the signal. See how iOS broke ad tracking.
- Ad blockers and privacy browsers block the pixel outright for a big slice of traffic.
- Consent: EU/UK visitors who decline are not tracked by the pixel.
- Short cookie lifetimes (Safari ITP) cut attribution windows.
How to recover the gap
Pair the pixel with the Conversions API (CAPI), which sends conversions server-to-server, bypassing much of the browser loss, with proper event deduplication so you do not double-count. You will not fully return to pre-iOS numbers, nobody will, but a good server-side setup recovers a large share, and gives Meta's optimisation better data. This is the same gap behind Meta and your shop never matching.
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · Meta Conversions API, explained