Meta Ads and Shopify sales don't match because they count different things. Meta credits an order to an ad if someone clicked or saw it within the attribution window, may model some conversions it can't observe, and records the order when it's placed. Shopify counts each real order once, credits only channels the buyer clicked, and knows which COD parcels were cancelled or returned.
This guide is for founders and marketers of Indian D2C and e-commerce brands, and the small agencies that run their ads, who open Ads Manager and Shopify side by side and see two different answers. It explains each cause of the gap (attribution windows, view-through credit, modelled conversions, Pixel and Conversions API duplicates, cash on delivery and RTO, time zones and currency), shows how Meta and GA4 differ too, and ends with a step-by-step way to reconcile the numbers and judge ads by the marketing efficiency ratio (MER) instead.
Platform settings change often. Everything below was checked against Meta, Shopify and Google help and developer pages on 16 November 2026.
Why don't Meta Ads and Shopify sales match?
Because each tool answers a different question. Shopify answers "how many orders did my store take, and which channel was the last one the buyer clicked?" Meta answers "how many purchases happened after someone interacted with my ads, within the window I chose?" Both can be correct at the same time and still show different totals.
Shopify's own analytics discrepancies page says it plainly: "It's unlikely that identical tracking mechanisms are being used by each of the services", and different reporting time zones add further gaps. So the aim is not to make the numbers identical. The aim is to know why they differ, check that the gap is stable, and make spending decisions on a number you trust.
Most of the gap comes from a handful of causes. The table shows how the three tools you probably use count the same sale.
| Question | Meta Ads Manager | Shopify | GA4 |
| What is counted | Purchase events sent by the Pixel and Conversions API, matched to people who interacted with an ad | Actual orders in your store | Purchase events from your site tag, linked to sessions |
| Who gets credit | Meta, if the buyer clicked, engaged with or viewed an ad within the window | A click-based model in its marketing reports, such as last click or last non-direct click | The reporting attribution model you choose, such as data-driven or last click |
| Can a view (no click) count? | Yes, with view-through attribution | No | No; GA4 only sees visits to your site |
| Estimated (modelled) results? | Yes, for some metrics and windows | No, orders are real records | It can model some data, depending on consent settings |
| Cancelled COD and RTO orders | Still counted as the original purchase | Visible as cancellations and refunds | Still counted unless you send refund events |
The sections below take each cause in turn, with the check you can run for it.
How do attribution windows change what Meta counts?
An attribution window is the number of days after an ad click or view in which Meta will credit a purchase to that ad, and a longer window means more purchases credited to Meta. Shopify uses its own rules, so the two can never agree exactly.
In Meta's Insights API, the default attribution option "means ["7d_click","1d_view"]", according to the Ad Account Insights reference: a purchase within seven days of clicking an ad, or within one day of seeing one. Meta first set this default for website conversions in January 2021, in its developer update on Apple's App Tracking Transparency prompt. Meta has kept adjusting the setting since. Jon Loomer's 2026 guide, an independent Meta ads specialist, reports that in March 2026 Meta started counting only link clicks as click-through, and that a 1-day "engage-through" window (likes, comments, shares, saves and engaged video views) replaced engaged-view. Check what your own ad sets use: in Ads Manager, open an ad set, and the attribution setting sits in the conversion section.
Shopify works differently. Its marketing reports give credit to the channel behind the order using click-based models, such as last non-direct click: the last channel the buyer clicked before buying, ignoring visits where they typed your address directly. An ad that was only seen never gets credit in Shopify. A shopper who saw your Instagram reel, later searched your brand on Google and bought is a Meta purchase in Ads Manager and a Google (or direct) order in Shopify.
Three effects follow from this:
- Meta can claim sales that Shopify gives to another channel. If Google, email and Meta all touched the buyer, each ad platform may count the sale. Add up "purchases" across platforms and you can get more sales than your store took.
- Recent days keep growing in Meta. A click today can become a purchase up to a week later, and that purchase is still credited to the click. Compare complete weeks, not yesterday.
- Changing the window changes the history. Comparing a 7-day click period with a 1-day click period is comparing two different measurements, not a performance change.
To see how much of Meta's number depends on the window, use Compare attribution settings in the Ads Manager columns menu and add 1-day click and 7-day click columns beside your normal results. The difference between them shows how much credit comes from slower or indirect buyers.
What are view-through and modelled conversions?
A view-through conversion is a purchase from someone who saw your ad but didn't click it, and a modelled conversion is one Meta estimates because it can't observe it directly. Shopify has neither, so both push Meta's count above what Shopify credits to Meta.
View-through. With a 1-day view window, a person who scrolled past your ad and bought later that day, perhaps by typing your store address, counts as a Meta purchase. Some of those people would have bought anyway, for example loyal customers who were going to reorder. Others genuinely bought because of the ad. Meta can't tell you which, and neither can Shopify. That's why it helps to look at click-only results next to the default and treat the view-through share as a softer number. Brands that retarget past buyers heavily usually see more view-through credit, because those people were already likely to buy (our retargeting guide covers how to keep audiences separate, using real estate examples).
Modelled conversions. When Apple's App Tracking Transparency prompt arrived, Meta said that "Statistical modeling will be used for certain attribution windows and/or metrics" to account for people it can no longer track, in the same January 2021 developer update. Meta does not publish how many of your results are modelled. Treat modelled results as an estimate that works well across large numbers of conversions and less well for a small ad set with a handful of purchases.
Neither of these is a reason to distrust Meta completely. Meta's optimisation runs on the same signals, and Shopify's last-click view hides the role of ads that start a buying journey. The point is to know which part of the gap they explain.
Is your Pixel or Conversions API counting orders twice?
If Meta shows noticeably more purchases than your store took, even on a 1-day click view, check for double counting first. The usual cause is the Pixel and the Conversions API both sending a purchase that Meta can't match, or two apps sending the same Pixel event.
Sending purchases from both the browser (Pixel) and your server (Conversions API) is good practice, because server events are less affected by ad blockers and browser limits. But Meta has to recognise them as the same order. Meta's deduplication guide says the Pixel's eventID must match the Conversions API's event_id, and the event names must match too. Duplicates are removed when they arrive within 48 hours of the first event with that ID.
On Shopify, the simplest setup is the Facebook & Instagram app with customer data sharing switched on. Shopify's Facebook data sharing page describes three levels (Standard, Enhanced and Maximum); Maximum uses the Conversions API as well as the Pixel. Problems usually start when a second app, a theme snippet or a Google Tag Manager tag sends its own purchase event on top.
- List every source of purchase events. In Events Manager, open your dataset (Pixel), select the Purchase event and see which integrations send it. Then check your Shopify apps, theme code and Tag Manager for extra Meta tags.
- Keep one browser source and one server source. Remove old apps and manual snippets once the Facebook & Instagram app is sending both.
- Check that both carry the same event ID. Events Manager's diagnostics flag purchase events that aren't being deduplicated.
- Place a test order and count it. One order should show as one purchase with the right value. Meta's Pixel reference lists
currency and value as required for the Purchase event, so check both.
The opposite problem, Meta showing far fewer purchases than Shopify credits to Facebook and Instagram traffic, usually means the server events aren't arriving or can't be matched to people. Fix that before cutting budgets, because Meta's delivery learns from the purchases it receives. Our D2C launch checklist covers the full tracking setup for a new store.
How do COD orders and RTO distort Meta's numbers in India?
Meta records a purchase the moment a COD order is placed, but some COD parcels are refused or returned to origin (RTO), so Meta's revenue is higher than the money you actually collect. Shopify shows those cancellations and refunds; Meta never hears about them unless you build something extra.
For Indian D2C brands this is often the biggest single gap, and none of the US-written guides deal with it. A COD order fires the same Purchase event as a prepaid UPI or card order. If the customer later refuses the parcel, Shopify records the cancellation, but the purchase already sits in Ads Manager with its full value. The result:
- Meta's ROAS looks better than your real return, by however much of your COD revenue doesn't get delivered.
- Campaigns that attract impulse COD buyers look like winners. An ad that brings many orders that never get delivered can beat an ad that brings fewer, prepaid orders in Ads Manager while losing you money after shipping both ways.
- Meta learns to find more people who place orders, not necessarily people who accept the parcel, because that's the signal it receives.
What to do about it:
- Report delivered revenue, not placed revenue. In Shopify, track net sales after cancellations and returns, and split it by payment method (COD versus prepaid) in your weekly sheet.
- Calculate a delivered ROAS by campaign using order tags or UTM parameters: take the orders from each campaign that were actually delivered and paid, and divide by spend.
- Confirm COD orders before shipping (by WhatsApp or SMS, with the customer's consent), and consider nudges to prepaid such as a COD fee shown clearly before checkout. Fewer refused parcels narrows the gap at the source.
- Be careful with "optimise for purchase value" on COD-heavy stores. The values Meta learns from include orders that later fail.
Our guide on D2C customer retention covers the post-purchase messages that help COD buyers accept their parcels.
Do time zones, currency and dates cause the gap?
Yes, and they're the easiest causes to fix: if your ad account and your store use different time zones or currencies, daily numbers will never line up. Check these before anything else, because they take minutes.
- Time zone. Shopify's discrepancies page lists different reporting time zones as a cause of gaps. If your Meta ad account was created on US Pacific time and your store runs on India Standard Time, an order at 10 AM IST lands on the previous day in Meta. Check the ad account time zone in Ads Manager's account settings and the store time zone in Shopify's general settings.
- Currency. If the ad account is in US dollars and the store sells in rupees, every ROAS number depends on the exchange rate and on the Pixel sending the right
currency code with each purchase. A purchase sent as "USD" with a rupee amount inflates value hugely, and a missing currency causes errors. Check a test order's value and currency in Events Manager.
- Which date a sale belongs to. Meta said in its 2021 update that offsite conversions "will be reported based on the time the conversions occur". But reports pulled through the API or third-party dashboards can use a different setting: the Insights API has an
action_report_time option where "impression" puts a purchase on the day the ad was seen and "conversion" puts it on the day it happened. If your dashboard and Ads Manager disagree for the same days, this setting is a likely reason.
- Gross versus net. Meta reports the value sent with the purchase event, which may include shipping and tax depending on your setup. Shopify reports gross sales, discounts, returns, net sales and total sales separately. Compare the same definition.
GA4 only sees visits to your website and credits sales by its own attribution model, so it never counts view-through purchases and often gives Meta less credit than Ads Manager does. A gap between Meta and GA4 is normal; a gap that suddenly changes is worth checking.
GA4 offers three reporting attribution models, data-driven, paid and organic last click, and Google paid channels last click, according to Google's attribution help page. Its attribution settings use a default lookback window of 90 days for most key events (30 days for first visits). The same help page notes that under data-driven attribution, conversions can be reattributed for up to seven days after they happen, so recent GA4 numbers move too.
The common reasons Meta and GA4 disagree:
- Different windows and models, as above. GA4 can credit a sale to a Google search that came after a Meta click; Meta credits itself.
- Missing or messy UTM tags. Without consistent
utm_source and utm_medium on your Meta ads, GA4 files Instagram and Facebook visits under referral or "unassigned". Add the same URL parameters at ad level for every campaign.
- In-app browsers and consent. Many Meta clicks open inside the Instagram or Facebook app browser, and cookie banners or blockers can stop the GA4 tag from recording the session. Shopify's discrepancies page notes that Google "can only count visitors with JavaScript and cookies activated".
- Cross-device journeys. Someone who taps an ad on their phone and buys on a laptop is hard for GA4 to join up without sign-in data, while Meta may still match the purchase to the person.
If you also run Google Ads, expect a third number again. Our guide to Google Ads for D2C brands covers its conversion setup.
How do you reconcile Meta Ads and Shopify numbers?
Fix the setup errors first, then compare like with like over complete weeks, then track the gap as a ratio instead of trying to close it. These steps take an afternoon and are worth repeating every month.
- Align time zone and currency. Note your ad account's time zone and currency and your store's. If they differ, convert one side in your reports, or plan a new ad account set up correctly.
- Audit purchase events. Place a test order with UPI or card and, separately, with COD. Each should appear once in Shopify and once in Events Manager with the correct value and currency, with the Pixel and Conversions API deduplicated.
- Choose a fixed comparison period. Use a complete week (or month) that ended at least seven days ago, so Meta's click window has closed.
- Pull three Meta numbers for that period: purchases and purchase value on your default setting, on 7-day click only and on 1-day click only (via Compare attribution settings).
- Pull three Shopify numbers for the same dates: total orders, orders credited to Facebook and Instagram in the marketing reports, and net sales after cancellations and returns, split by COD and prepaid.
- Compare and explain. If Meta's 1-day click purchases exceed Shopify's total orders, you have a tracking problem (duplicates or wrong values). If Meta's default is higher than Shopify's Meta-credited orders but its click-only figure is close, the gap is mostly attribution and view-through. If revenue differs more than order counts, look at COD failures, discounts, shipping and currency.
- Record the ratio. Write down Meta-reported purchases divided by Shopify-credited orders for the period. A stable ratio means you can read Ads Manager trends with confidence; a sudden jump means something in tracking changed.
- Make budget decisions on store revenue using MER (below), and use Ads Manager to compare campaigns and ads with each other.
Here is how to read the result of step 6:
| What you see | Most likely cause | What to do |
| Meta purchases higher than Shopify's total orders | Duplicate events or two apps sending purchases | Remove extra tags; check event IDs match |
| Meta default much higher, click-only close to Shopify's Meta orders | View-through and cross-channel credit | Normal; watch click-only numbers alongside default |
| Order counts close, revenue far apart | Currency, tax and shipping in value, or COD cancellations | Fix value and currency; report delivered revenue |
| Daily numbers off, weekly totals close | Time zone or reporting date differences | Compare weeks; align time zones |
| Meta far lower than Shopify's Meta-credited orders | Server events missing or poorly matched | Check Conversions API status and data sharing level |
If you'd rather have people do this with you, our Meta and Google ads service starts with exactly this kind of tracking check.
What is MER and why should you use it?
MER (marketing efficiency ratio) is your total store revenue divided by your total ad spend across every channel for the same period. It doesn't depend on any platform's attribution, so it can't be inflated by double counting or view-through credit.
The formula is simple: MER = total revenue ÷ total marketing spend. For an Indian D2C brand, use net delivered revenue from Shopify (after cancellations, RTO and refunds) and the total spend on Meta, Google and any other paid channel for the same dates. Some brands also calculate a new-customer version using only first-time buyers' revenue, which shows whether ads are bringing in new people or mostly reaching existing customers.
| Measure | What it tells you | Where it misleads | Use it for |
| Meta ROAS (Ads Manager) | Which campaigns, ad sets and ads Meta credits with sales | Includes view-through, modelled and undelivered COD sales | Comparing ads and campaigns inside Meta |
| Shopify last-click revenue by channel | Which channel brought the final click | Undervalues ads that start the journey | Seeing how search, email and direct close sales |
| MER (store revenue ÷ total spend) | Whether total marketing is paying back | Can't say which channel caused the result | Overall budget decisions and scaling |
The practical way to combine them: set a target MER that works for your margins and delivery costs, use it to decide whether to raise or cut total spend, and use Ads Manager to decide where inside Meta the money goes. When you increase Meta spend and MER holds steady while revenue grows, the extra spend is likely working, whatever any single dashboard claims. Testing new creative is part of that, and our guide to UGC ads for D2C brands covers it.
Before you start reconciling, it also helps to know your campaigns are healthy, because a stalled or limited ad set makes every number noisier. You can run the free Meta ads health check by BrightROAS, our Meta ads dashboard. It's free, takes about two minutes and needs no sign-up: export a CSV from Ads Manager (Reports → Export → CSV, with Breakdown set to Day and Level set to Ad, covering the last 14 to 30 days), upload it, and you get a health score out of 100 plus the problems it finds, such as creative fatigue, ads Meta has flagged, learning-limited ad sets, stalled campaigns and cost overruns. The file is read in your browser and never uploaded. BrightROAS is not affiliated with Meta.
If you run a Shopify or D2C brand and want a second pair of eyes on your tracking and ads, see how we work with e-commerce and D2C brands, or ask for a free audit and we'll go through your Pixel, Conversions API setup and reporting with you. Wider growth work sits under our e-commerce marketing service.
Sources