If you run Facebook or Instagram ads and sell through Shopify, you've probably noticed the numbers don't match. Shopify says you made 40 sales last week. Meta Ads Manager says 25. Which one is right — and why is there a gap?
The short answer: Shopify is counting orders. Meta Pixel is counting browser events — and a lot can go wrong between a customer clicking “Buy” and that event actually reaching Meta.
Here are the most common reasons your Meta Pixel is under-reporting, and what you can do about it.
Ad blockers and browser privacy settings
The Meta Pixel is a JavaScript snippet that runs in the customer's browser. If a customer has an ad blocker installed, or uses a browser with strict privacy settings — like Firefox with Enhanced Tracking Protection, or Safari with Intelligent Tracking Prevention — the pixel script often never runs at all.
A meaningful share of desktop users block third-party scripts. That means for every 10 orders placed from desktop, the pixel can miss several of them completely, and you'd never know unless you compared the numbers to your Shopify order count.
Mobile users are somewhat less likely to have ad blockers, but Safari on iPhone still applies aggressive tracking restrictions by default — which is a problem for Meta specifically, given how many purchases happen on iOS.
The thank-you page doesn't always load
The Meta purchase event is typically fired on the order confirmation page (the “thank you” page) after checkout. The problem is that this page doesn't always fully load:
- Customers close the browser tab the moment payment goes through
- Slow internet connections time out before the page renders
- Payment redirects — PayPal, Klarna, Afterpay — sometimes land on a page that doesn't include your pixel code
- Shopify's checkout is hosted on a separate domain, and pixel configuration mistakes are common in this step
When the thank-you page doesn't load — or loads without the pixel snippet — the purchase event is never sent to Meta. Shopify still recorded the order. Meta has no idea it happened.
iOS 14+ and what Apple's privacy changes did to ad tracking
Apple's App Tracking Transparency framework, introduced in 2021, required apps — including the Facebook app — to ask users for permission before tracking them across other apps and websites. The majority of iOS users opted out.
This means Meta can no longer track those users using the browser pixel alone. Conversions from opted-out iOS users are either estimated through Meta's statistical modelling or missed entirely. Shopify sees the order either way. Meta often doesn't.
This single change is responsible for a significant portion of the discrepancy that store owners started noticing around 2021 and that has persisted ever since.
Cookie consent and GDPR
If you're selling to customers in the EU, UK, or anywhere with a cookie consent requirement, many visitors click “Reject All.” When they do, the Meta Pixel script should be blocked from loading — that's the legally correct behaviour if your consent platform is set up properly.
Any purchase from a customer who declined tracking will appear in Shopify but not in Meta. This is not a bug. It's compliance. But it does mean a portion of your conversions will reliably never show up in Ads Manager.
What you can do about it
The most effective fix is to stop relying solely on the browser pixel and set up server-side tracking through Meta's Conversions API (CAPI). Instead of firing from the customer's browser, CAPI sends conversion data directly from your server to Meta. It's not affected by ad blockers, browser privacy settings, or page load failures.
Combining the browser pixel with CAPI is sometimes called “redundant tracking” — you get more complete data, and Meta can de-duplicate the events so you don't over-count.
TraceSignals Conversion Tracking does this for WooCommerce stores on WordPress: it connects your store to GA4, Google Ads, and Meta Pixel through both browser and server-side signals. If a browser event gets blocked, the server-side event still reaches Meta — so your campaign data stays accurate.
Even before setting up CAPI, you should regularly compare your Shopify order count against Meta's reported conversions. A gap of 10–15% is normal. A gap of 40% or more usually points to a configuration problem — often a pixel that isn't firing on the thank-you page at all, which is fixable.
The bottom line: the Meta Pixel was never designed to catch every conversion on its own. Browser limitations, privacy changes, and checkout flow quirks all create gaps. The fix is to layer in server-side tracking so you're not dependent on a JavaScript snippet loading perfectly every time a customer checks out. Better data means Meta's algorithm can find more buyers — and that directly affects your return on ad spend.