Meta ads conversions don't match the store
iOS opt-outs, ad blockers and a missing CAPI leave a chunk of real sales uncounted, while duplicate pixels count a few of them twice.
Pixel and CAPI reconciled against orders
Running Facebook or Instagram ads?
Meta ads look great in Ads Manager and terrible against Shopify. Usually the pixel fires twice, the Conversions API was never wired up, and iOS opt-outs ate the rest. We untangle what is really being reported and rebuild it so the numbers reconcile.
What it is
The Meta Pixel (formerly Facebook Pixel) is the tracking code for Facebook and Instagram ad conversions. It is the companion to the Conversions API (CAPI), which is the server-side event channel that partially restored tracking lost to iOS 14 ATT (Apple, 2021) and Enhanced Tracking Protection on Firefox.
Events include Purchase, Lead, CompleteRegistration, AddToCart, and custom events you define yourself. Event Manager, Aggregated Event Measurement and Advanced Matching are the current measurement stack. Business Manager and Ads Manager tie all of it back to an ad account.
The honest version
No technology is all upside. This is where Meta Pixel earns its place and where it tends to cause trouble.
Sound familiar?
The Meta Pixel problems that bring people to us, and what you have once each one is fixed.
iOS opt-outs, ad blockers and a missing CAPI leave a chunk of real sales uncounted, while duplicate pixels count a few of them twice.
Pixel and CAPI reconciled against orders
Browser pixel only, no server events, no event_id, and nothing to catch iOS users or anyone running a content blocker.
CAPI live, deduped, match quality measured
A theme install plus a GTM tag plus a Shopify app, each loading its own fbq. Purchase gets reported more than once per sale.
One pixel, one source of truth
A policy violation flag, often triggered by landing page content or billing, with campaigns paused and appeal buttons greyed out.
Appeal filed and account reinstated
No Advanced Matching, hashing disabled, or PII blocked at the consent banner, so Meta cannot connect events to users reliably.
Match quality in the good band
More than eight events configured in Aggregated Event Measurement, so one of the lower-ranked events silently reports nothing for opted-out iOS.
Eight prioritised events, counted
What we do
Call us for one dropped Purchase event, or hand us the whole ad tracking stack.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Three things stack up. iOS App Tracking Transparency means a big slice of iPhone buyers never send a browser event. Ad blockers and Enhanced Tracking Protection remove more. And without the Conversions API running server-side, there is no second channel to recover any of it. Add Advanced Matching and CAPI and the gap usually closes to something sensible.
Pick a path first: Shopify's native CAPI, a WooCommerce plugin, CAPI Gateway on your own box, or a server-side GTM container. Then make sure every event has a shared event_id and event_name on both the browser and server side so Meta can deduplicate. Hash email and phone for Advanced Matching. Verify with test_event_code in Event Manager, and watch Event Match Quality climb once real traffic flows.
Almost always because the pixel got installed more than once. A theme snippet, a GTM container, and a Shopify or WordPress app each load their own copy. We open the Meta Pixel Helper, find each source, and leave exactly one in place.
Yes. We review the policy flag, clean up whatever triggered it on the landing page or in Business Manager, and file the appeal through the right channel. Timelines are set by Meta, not us, but a well-prepared appeal gets a real answer faster than a generic one.
Consent first: the banner has to capture a real choice before any pixel or CAPI event fires for EU visitors. For iOS, prioritise your eight Aggregated Event Measurement slots around Purchase and the steps that lead to it. Send Advanced Matching only on consented sessions. That setup is defensible under GDPR and gets the most out of what Apple still allows.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: