Why Meta purchases don't match your Shopify orders (and how to fix it)
On this page
- Why the numbers are never identical
- The 30-minute reconciliation test
- What your result means
- Fix 1: Remove duplicate pixels
- Fix 2: Make browser and server events share an event ID
- Fix 3: Turn on server-side tracking
- Fix 4: Check value and currency
- While you're in there: GA4 and Google Ads
- How to know it's fixed
- Questions people ask
- Sources
Short answer: Meta Ads Manager and Shopify count different things. Ads Manager shows purchases Meta credits to your ads, under your attribution setting. Shopify shows every real order. So the two will never match exactly. But if Meta shows more purchases than you had orders, or far fewer than your ad-driven sales, something is broken. The usual causes are a duplicate pixel, browser and server events that aren't deduplicated, or no server-side tracking at all.
This guide shows you how to tell a normal gap from a broken setup in about 30 minutes, and what to fix for each case.
Why the numbers are never identical
Before you fix anything, know which differences are normal. These are not bugs:
- Ads Manager only counts what it attributes to ads. Shopify counts every order, including direct, email, organic and repeat customers. Ads Manager only shows purchases Meta links to someone who clicked or saw your ad inside the attribution window set on the ad set.
- The attribution window. Most purchase campaigns use a click window (often 7 days) plus a short view or engagement window. A person who clicked on Monday and bought on Saturday can be credited to Monday's ad. Check the "Attribution setting" column in Ads Manager to see exactly what your ad sets use. Meta has changed the defaults over time, so don't assume.
- Different days. Ads Manager can report a purchase against the day of the ad interaction, not the day of the order. Daily numbers drift apart even when weekly totals are close.
- Privacy limits and blockers. iOS privacy settings, browser tracking limits and ad blockers stop some browser pixel events. Meta also uses statistical modelling for some conversions it can't observe directly, so reported numbers are partly estimates.
- Refunds and cancellations. Shopify may net these out. Meta keeps the original purchase event.
A healthy account still shows a gap. What matters is the direction and the size.
The 30-minute reconciliation test
Don't compare Ads Manager to Shopify. Ads Manager is attribution. Compare events received to orders. That tells you whether tracking works, which is a separate question from what the ads earned.
- Pick the last 7 full days.
- Store: count real orders in Shopify (or WooCommerce > Orders). Leave out test, cancelled and fully refunded orders.
- Meta: open Events Manager, choose your dataset (pixel), and read the total Purchase events received for the same 7 days.
- If you also run Google or TikTok, note GA4's ecommerce purchases and TikTok Events Manager's purchase total.
- Put them in a table:
| Source | Purchases (7 days) | Difference vs store |
|---|---|---|
| Store orders | 100 | n/a |
| Meta Events Manager | ? | ? |
| GA4 | ? | ? |
| TikTok Events Manager | ? | ? |
Now read the result.
What your result means
| What you see | Most likely cause | Go to |
|---|---|---|
| Meta received more purchases than you had orders | Duplicate pixel, or browser and server events not deduplicated, or the purchase fires again on a page reload | Fix 1, Fix 2 |
| Meta received far fewer purchases than orders | No Conversions API (browser pixel only), consent settings blocking tags, or buyers not returning to the thank-you page | Fix 3 |
| Counts close, revenue wrong | Value or currency sent wrong | Fix 4 |
| Events Manager close to orders, but Ads Manager low | Tracking is fine. Ads are getting less credit, which is an attribution and performance question, not a tracking bug | Leave tracking alone |
Events received should sit a little under your real order count. Some buyers decline cookies or block scripts. A platform that receives more purchases than you had orders is always a red flag.
Fix 1: Remove duplicate pixels
This is the most common reason Meta shows too many purchases. The pixel is installed twice: once by the official app, and again by an old theme snippet, a second app, or Google Tag Manager.
Check:
- Install the Meta Pixel Helper browser extension and walk through your store: product page, add to cart, checkout and the thank-you page. Each event should fire once, for one pixel ID.
- Shopify: go to Settings > Customer events. It lists app pixels and custom pixels. Also look in Online Store > Themes > Edit code >
theme.liquidfor an oldfbq('init'snippet. - WooCommerce: check every plugin that mentions Meta or Facebook, your theme header and your GTM container.
Fix: pick one source for the browser pixel (the official app or plugin, or GTM) and remove the others.
Fix 2: Make browser and server events share an event ID
If you send a purchase from the browser (pixel) and from your server (Conversions API), Meta needs to know they're the same order. Meta's documentation says it keeps one copy when both events have the same event name and the same event ID, and only for copies that arrive within 48 hours of each other.
In practice:
- The pixel sends the ID as
eventID. The Conversions API sends it asevent_id. The value must be identical. - The safest value is built from the order ID, because both the thank-you page and your server know it.
- A classic break: a theme snippet sends a random ID while an app sends the order number. Both events arrive, neither matches, and Meta counts two purchases.
Check: in Events Manager, open your dataset and look at the Diagnostics tab for deduplication warnings. Then use Test Events, place a test order, and compare the event IDs on the browser and server copies.
Fix: send both copies from one system that uses one ID. On Shopify that usually means letting the Facebook & Instagram app handle both, and removing any custom pixel code that also sends Purchase.
Fix 3: Turn on server-side tracking
A browser-only pixel misses buyers whose browsers block it. The Conversions API sends purchases from the server as well, so Meta still gets them.
- Shopify: go to Sales channels > Facebook & Instagram > Settings > Data sharing settings. Shopify's help page explains the levels: Standard uses the browser pixel only, while Enhanced and Maximum add the Conversions API. Maximum is the top level.
- WooCommerce: Meta's official plugin has a Conversions API option. Server-side Google Tag Manager with a Meta CAPI tag is the other common route. It gives more control but needs hosting and upkeep.
Then send good customer data with server events: email and phone (normalised and hashed once), the fbp browser ID and fbc click ID, plus IP address and user agent. This is what drives your Event Match Quality score in Events Manager. Double-hashing email is a quiet, common mistake.
If buyers pay off-site (some wallets and buy-now-pay-later flows), check that they come back to the thank-you page. If they don't, the browser purchase never fires, which is another reason server events matter.
If you changed checkouts recently: Shopify retired checkout.liquid and the "additional scripts" box. Shopify's checkout upgrade guide says non-Plus stores were upgraded automatically after 26 August 2026, and old code there doesn't carry over. If a purchase tag lived in additional scripts, it may have stopped firing. Rebuild it as an app pixel or a custom pixel under Settings > Customer events.
Fix 4: Check value and currency
If counts look fine but revenue is off:
valuemust be a plain number, like89.50, not"$89.50".currencymust be a three-letter code that matches the value, likeUSDorGBP.- Pick one rule (with or without tax and shipping) and use it on Meta, Google and TikTok, so you can compare them.
Use Meta Pixel Helper on the thank-you page, or the Purchase event details in Events Manager, to see what's actually sent.
While you're in there: GA4 and Google Ads
The same order often gets double counted on the Google side too:
- GA4: every purchase needs a real, unique
transaction_id. Google's help page says GA4 deduplicates purchases that share a transaction ID, and also treats every empty-string ID as the same purchase. So never send a blank one. - Google Ads: keep one Primary purchase conversion action. A Google Ads tag purchase plus an imported GA4 purchase, both set to Primary, will count each sale twice. Google recommends the "Every" count setting for sales.
How to know it's fixed
Re-run the 7-day reconciliation one week after your change. Good looks like this:
- Meta Events Manager purchases are close to, and not above, your real orders.
- No deduplication warnings in Diagnostics.
- Purchase arrives from both browser and server.
- Event Match Quality for Purchase hasn't dropped.
Then re-run it after any new app, theme change or checkout change. That's when tracking usually breaks again.
Questions people ask
Should Meta and Shopify numbers ever match exactly?
No. Ads Manager reports purchases Meta attributes to your ads under your attribution setting, while Shopify counts every order from every channel. Compare Meta Events Manager's purchases received with your orders instead. Those should be close.
Why does Meta show more purchases than Shopify?
Usually a duplicate pixel, or browser and server events that don't share the same event ID, so Meta counts one order twice. A purchase that fires again when the thank-you page reloads causes the same thing.
Why does Meta show fewer purchases than Shopify?
Some of it is normal: not every buyer saw or clicked an ad, and some browsers block the pixel. A big gap in Events Manager (not just Ads Manager) usually means the Conversions API is off, consent settings block tags, or buyers don't return to the thank-you page.
Do I need the Conversions API if I have the pixel?
For most stores running Meta ads, yes. The pixel runs in the browser, which blockers and privacy settings can stop. The Conversions API sends the purchase from the server too, and deduplication keeps it to one count.
Will fixing tracking improve my ROAS?
It can't promise that. It makes the data Meta optimises on closer to your real orders, and it makes your reports honest. Better decisions can follow, but results depend on your offer, creative and budget.
Sources
- Meta for Developers: Handling duplicate Pixel and Conversions API events
- Shopify Help Center: Meta data sharing levels
- Shopify Help Center: Checkout upgrade guide
- Google Analytics Help: Minimize duplicate key events with transaction IDs
- Google Ads Help: About conversion counting options
Platform menus and defaults change often. This guide reflects them as of 18 Nov 2026. Nothing here promises results: they depend on your store, offer, budget and execution.