You open Meta Ads Manager and it claims 78 purchases. You open Shopify and see 100 orders. The channels disagree, and neither number is wrong — they are answering different questions. Meta is telling you how many sales its ads plausibly influenced. Shopify is telling you how many sales actually happened.
This guide walks through exactly why the two never line up, how big a gap is healthy, when a mismatch is genuinely broken, and — the part most articles skip — what the confusion costs you in real per-order profit.
Why Meta Ads and Shopify count orders differently
The mismatch comes from two separate families of causes. One family is structural methodology: the two systems measure the same reality in different ways, and no amount of tracking work will ever close the gap. The other is tracking loss: data that genuinely goes missing, which better plumbing can narrow. Understanding which is which is the whole game.
Meta counts views; Shopify counts checkouts
Meta's default attribution setting is 7-day click plus 1-day view, per Foreplay's 2025 attribution guide and Jon Loomer. That "1-day view" is the single biggest inflator.
It means Meta claims credit when someone sees your ad — scrolls past it, never clicks — and then buys within a day. Shopify has no concept of a view. It only records a completed checkout with a last-click source. So every view-through buyer shows up as a Meta conversion but gets filed by Shopify under organic, direct, or whatever they clicked last.
Modeled conversions fill in what Meta can't see
When Meta can't directly observe a purchase — an iOS opt-out, a blocked pixel, a consent decline — it estimates the conversion with a statistical model and reports the estimate as if it were counted. Shopify never models. It reports only real, completed orders.
These aren't fake sales; they're guesses at real buyers Meta couldn't track. But they mean Meta's total can exceed Shopify's even when your tracking is flawless.
Click date versus order date desyncs your days
Meta reports a conversion on the date of the click that earned the credit, not the date of the purchase. A click on Monday that converts Thursday shows up in Meta on Monday. Shopify records the order on Thursday.
That single detail makes any day-by-day comparison meaningless. Always compare on trailing 7- to 14-day windows, never a single day.
Cross-device buyers land in different buckets
Meta identifies logged-in users across devices. Someone who sees your ad on a phone and buys on a laptop is still credited to the ad. Shopify's last-click attribution ties the order to whatever referrer hit the buying device — often "direct." Same customer, two different homes.
For the deeper version of this — including how the revenue figures diverge, not just the order counts — see our companion piece on why Meta Ads ROAS doesn't match Shopify, and the sister issue of why Meta Ads sessions don't match Shopify.
How big should the gap be?
A 20–35% gap between Meta-reported purchases and Shopify orders is the normal range on the default window, according to Vaizle and TrackBee. Most of that excess is view-through plus modeled conversions.
Part of the tracking-loss side pushes the other direction. Browser ad blockers and Safari/Firefox tracking prevention stop client-side pixels from firing for an estimated 10–25% of users, per Audiense and Elevar — those buyers undercount in Meta while Shopify still records the server-side sale. The methodology inflation and the tracking loss partly cancel, which is why a moderate net gap is healthy.
If you tightened the window all the way down to 1-day click, Meta's reported conversions can drop by roughly 40%, per TrackBee — same real sales, narrower credit window. That's the clearest proof the number is a setting, not a fact.
When the mismatch is actually a bug
There is one gap size that is broken: when Meta shows close to 2× Shopify orders. That almost always means your Meta Pixel and Conversions API (CAPI) are both firing a Purchase for the same order without a shared deduplication key, so Meta counts each sale twice.
Meta's official deduplication rules collapse the two copies into one when they share a matching event_id and event_name. The dedup window is 48 hours, and Meta keeps whichever copy arrives first. If those IDs don't match, both survive and your count doubles.
A jump in conversions right after you added CAPI is not a win — it's a dedup misconfiguration. Correct redundant setup keeps your count stable while recovering blocked events. Google Ads users hit the parallel version of this, covered in why Google Ads conversions don't match Shopify.
A worked example
Say your store, "Nomad Mugs," runs Meta ads for one week and gets 100 real orders at $40 subtotal each. Of those buyers, 55 clicked a Meta ad within 7 days, 15 only saw one within a day, 10 came from Google, and 20 from organic or direct.
Here's how each system reports that single week of 100 sales:
- Meta: 55 click-through + 15 view-through = 70, plus about 8 modeled conversions ≈ 78 purchases. It reports revenue at subtotal only ($40 × 78 ≈ $3,120) and does not subtract refunds.
- Shopify: 100 orders, last-click — crediting ~55 to Facebook, ~10 to Google, ~35 to search/direct. The 15 view-through buyers are not credited to Facebook here, because they clicked nothing.
78 versus 100 is a 22% gap — squarely in the healthy range. Nothing is broken. Meta influenced sales it can't prove and can't un-count; Shopify is your source of truth for how many sales happened.
What the mismatch actually costs you
Here's the part the ranking articles gloss over: this isn't an accounting curiosity. You make budget decisions on these numbers, and the wrong one bleeds profit.
Walk the per-order math. Say each mug sells for $40 subtotal. Your Printify cost is $12, you charge $5 shipping that costs you $5, and Shopify Payments takes about 2.9% + 30¢ per transaction on the Basic plan, per ReportPundit and Webgility. On a $45 charge, the processing fee is about $1.61.
Per-order gross profit before ads: $40 − $12 product − $1.61 fee = $26.39.
Now split your ad spend across the right denominator. If you spent $1,000 for the week and you credit it against Meta's 78 conversions, your cost per order looks like $12.82, and per-order profit reads $26.39 − $12.82 = $13.57. If you divide the same $1,000 across Shopify's 100 real orders, cost per order is $10.00 and profit is $16.39. Same week, same spend — but a $2.82 per order swing depending on which number you trusted.
Scale that across a month and the "which count is real" question decides whether you kill a profitable campaign or double down on a losing one. One returned order also matters: a refund erases the $26.39 in Shopify and your payout, but Meta and GA4 typically keep the original conversion, so your dashboards stay inflated after the money leaves.
How to reconcile — and stop guessing
The reconciliation rule is simple: Shopify order count and total sales are your source of truth for what happened; Meta's number is only its own influence claim. Never expect them to equal. Compare on trailing windows, tag paid links with UTMs so Shopify classifies them consistently, and verify your Pixel-CAPI dedup so you're not double-counting. This is the core discipline in our full guide to reconciling your ecommerce data.
But manually joining Meta's window-based counts to Shopify's real orders to Printify's costs — every week — is where most sellers give up and just trust the biggest number. That's the expensive mistake.
PodVector connects Shopify, Meta Ads, Google Ads, Printify, Printful, and Stripe into one live data warehouse and computes your true per-order profit — spend, product cost, fees, shipping, and refunds netted against the real Shopify order, not Meta's inflated count. Victor, its AI operator, reads that combined data and proposes moves, executing approved actions on the Shopify side. Victor does not touch your ad account; he reads ad data and hands you the profit picture Meta's dashboard can't. If you're consolidating a catalog first, here's how to transfer from Etsy to Shopify before you wire it all together.
FAQs
Why does Meta show more orders than Shopify?
Because Meta credits view-through conversions (sales where the buyer only saw the ad), modeled conversions (statistical estimates of buyers it couldn't track), and cross-device purchases — none of which Shopify counts. Shopify records only completed checkouts by last click. A 20–35% gap on the default window is normal.
Is Meta lying or inflating numbers to justify my spend?
No. Meta counts view-through and modeled conversions by design and disclosure. It's answering "did my ad influence this sale?" — a different question than Shopify's "did a sale happen?" Neither is dishonest; they measure different things.
Will setting up the Conversions API make the numbers match?
No. CAPI recovers events lost to ad blockers and consent declines, but it does nothing about methodology gaps like view-through, modeling, and click-date reporting. Even with perfect tracking, expect a structural gap. If your count jumped after adding CAPI, you have a dedup misconfiguration, not more sales.
Meta shows almost exactly double my Shopify orders — what's wrong?
That's the classic signature of broken deduplication: your Pixel and CAPI are both sending a Purchase for each order without a shared event_id, so Meta counts every sale twice. Meta only merges duplicates that match on event_id and event_name within 48 hours. Fix the event ID and the phantom half disappears.
Which number should I use to make budget decisions?
Use Shopify's order count and total sales for how many sales and how much revenue actually happened, and use Meta's number only as a directional signal of influence. Better still, compute per-order profit against real Shopify orders — as the worked example shows, trusting the wrong denominator can swing your per-order profit by several dollars.
Why does the gap change when I switch attribution windows?
Because the window is a setting, not a fact. Narrowing from 7-day-click-plus-1-day-view down to 1-day click can cut Meta's reported conversions by around 40% — the same real sales, credited over a shorter lookback. Pick one window and compare it consistently over trailing periods.