Start free
Kunads / Guides / Why Meta, Google and Shopify never agree on sales

Why Meta, Google and Shopify never agree on sales

Updated 2026-11-16 · prices and features checked on that date

Meta, Google and Shopify never agree on sales because each counts differently. Meta credits a purchase to an ad clicked within 7 days or seen the day before, on the impression date, and models some. Google uses a 30-day click window and loses data to tags and consent. Your shop counts each order once.

This guide is for performance marketers and agency owners who need one honest number. It explains, from Meta's and Google's own documentation, why the counts differ, how to compare them, and what to steer on instead.

In short

  • Meta's default attribution credits a purchase within 7 days of a click or 1 day of a view. It reports it on the impression date and can include modelled conversions. Your shop counts each order once, on the day it happened.
  • Google Ads reports conversions on the click date with a 30-day default click window. Its number is often lower than the shop's, because tags break, consent mode limits data and enhanced conversions are off.
  • Meta and Google each give credit among their own ad interactions, so the same order can be counted by both.
  • Do not pick a winner. Look at each platform's number next to your shop's, and steer the account on blended ROAS: all revenue ÷ all ad spend.

Why Meta's number differs from Shopify's

Your shop and Meta are answering different questions. Shopify answers "how many orders were placed?". Meta answers "how many purchases happened after someone interacted with one of our ads, under the rules of this ad set?". Five rules from Meta's own help pages explain the difference.

1. The attribution setting counts views, not only clicks

Meta's default attribution setting for new ad sets is 7-day click or 1-day view. Under the standard model, Meta lists three ways an ad can earn a conversion:

Meta states the gap plainly. If a person sees an ad, does not click, and later buys on your site, Meta may attribute that purchase to the ad. Most third-party tools cannot. Shopify's own marketing reports are click-based, so they cannot see this either. Its default model is last non-direct click. A purchase made by someone who scrolled past your ad yesterday will be in Meta's number and, in Shopify, under "direct" or another channel.

2. Meta reports on the impression date, not the order date

Ads Manager reports conversions on the date the impression was served. Meta's own example: if someone clicks an ad on Monday and buys on Friday, Ads Manager reports the conversion on Monday. Shopify puts the order on Friday. Any date range you compare will have orders moving in and out at both ends. In Ads Reporting you can switch between "time of conversion" and "time of impression". Use time of conversion when you compare with your shop.

3. Some conversions are modelled

Meta says it models conversions where data is "partial or missing", for example because of user privacy choices. It also models how conversions are spread across campaigns, ad sets and ads. Modelled conversions are estimates. They can be correct on average and still not match a single order in your shop.

4. Cross-device journeys

Meta measures people, not cookies. Someone who sees the ad on a phone in Instagram and buys on a laptop can still be counted. Meta itself says cookie-based tools "may not be able to measure cross-device conversions well". Here Meta can see a journey the shop's source tracking misses. Keep this in mind: the shop's view is not the truth about cause. It is the truth about totals.

5. Duplicate events from the Pixel and the Conversions API

If you send purchases through both the Meta Pixel and the Conversions API, Meta removes duplicates only when the browser event's eventID matches the server event's event_id, the event names match, and both arrive within 48 hours. If the IDs are missing, one order can be counted twice. Meta's help pages give two more checks. A high "additional conversions reported" percentage can mean poor deduplication. And if Ads Manager reports more conversions than your other tools, check for duplicate pixel fires, which redirects can cause.

Why Google Ads shows fewer conversions than your shop

Google is not simply the stricter platform. Its default click-through conversion window is 30 days, much longer than Meta's 7. It also counts engaged-view conversions from video: by default, a web conversion within 3 days of watching at least 10 seconds of a skippable in-stream ad, or at least 5 seconds of an in-feed or Shorts ad.

View-through conversions have a 1-day default window. Google also includes modelled conversions, including modelled cross-device conversions. In practice, its number often comes out lower than the shop's. Three reasons are common.

1. Broken or partial tags

A Google Ads conversion only exists if the tag fires on the order confirmation page. A theme change, a new checkout or a Tag Manager trigger that misses one payment method can quietly drop orders. Google Ads shows a status for each conversion action, such as "Unverified", "Tag inactive" or "Needs attention". Google's fix is to run Tag Assistant from the conversions table and check that the tag covers every page, thank-you pages included.

2. Consent mode

In the EU, many visitors decline cookies. Google's developer documentation describes two modes. In basic consent mode, Google tags are blocked until the visitor interacts with the banner, and "no data is sent before a user consents". When a visitor declines, Google gets nothing and uses a general model to fill the gap. In advanced mode, tags load with consent denied and send cookieless pings, which allow an advertiser-specific model. If your banner blocks Google tags completely, expect fewer reported conversions than orders.

3. Enhanced conversions switched off

Enhanced conversions send hashed first-party data, such as the buyer's email, with the conversion. Google can then match it to signed-in Google accounts that interacted with your ads. Google describes it as improving the accuracy of conversion measurement. Without it, a conversion that lost its cookie has no other way to be matched.

Two settings change the count too. Google reports conversions by default on the date of the click, not the date of the conversion. And each conversion action counts either "every" conversion after an interaction or only "one". Purchases should normally use "every".

What to steer on instead

Because the numbers count different things, a gap between a platform and the shop is not a mistake to correct. Neither side is the full picture: the shop knows the total, the platforms see journeys the shop cannot.

Steer the account on blended ROAS (also called MER): all revenue ÷ all ad spend. It needs no attribution, so the platforms' differences do not touch it. Compare it with your breakeven. For a shop whose €25.20 average order keeps €13.57 after goods, fees and delivery:

Breakeven ROAS = average order value ÷ amount kept per order = 25.20 ÷ 13.57 = 1.86×

If blended ROAS stays above 1.86× while spend rises, the extra spend is paying. Inside each platform, compare campaigns on that platform's own numbers, used the same way every week. Try it with the MER calculator (total revenue ÷ total ad spend) and the POAS calculator (profit after ad spend).

How to compare Facebook ads conversions with Shopify orders, step by step

  1. Pick a closed period. Use at least 30 days that ended at least 7 days ago, so late conversions have arrived. Use the same time zone in the shop, Meta and Google. Meta lists time zone as a common cause of mismatches.
  2. Export your orders. Remove test and cancelled orders. Decide whether order value includes tax and shipping, and make sure the value your Pixel and Google tag send uses the same rule. Otherwise the order counts can match while the revenue does not.
  3. Pull Meta by time of conversion. In Ads Reporting, switch to time of conversion. Use "Compare attribution settings" to split purchases into click-through, view-through and engage-through. Write down each part.
  4. Pull Google by conversion time. Add the "Conversions (by conv. time)" and "Conv. value (by conv. time)" columns. Check that only your purchase action is primary, that it counts "every", and that its status has no warning.
  5. Trace each order to a source. Use the UTM parameters on your ads and the order's conversion summary in Shopify (first visit source, sessions, UTMs). Label each order Meta, Google, other or unknown. Shopify warns that blocked cookies, private browsers and some channels leave the summary empty. Count the unknowns. Do not guess them.
  6. Put them side by side. For each platform: the revenue it reports, and the orders your shop recorded from it. Do not turn the gap into a correction factor: neither side is the full picture.
  7. Check the overlap. Add Meta's and Google's numbers together and compare them with total shop revenue in the period. A total above the shop's means they count some of the same orders.
  8. Look for sudden changes. If a platform's number jumps or drops after a change, look first at the view-through share, deduplication (event_id) and duplicate pixel fires, then at tag status, consent mode and enhanced conversions. Fix tracking before you change any budgets.
  9. Steer on blended ROAS. Compare all revenue ÷ all ad spend with your breakeven ROAS. Repeat every month and after every tracking change.

Meta purchases vs Shopify orders: what each number is good for

QuestionShop ordersMeta / Google reported
How much did we actually sell?YesNo
Does it see view-through and cross-device journeys?NoYes, partly modelled
Does it avoid two platforms counting one order?YesNo
Is it good for comparing ads inside one platform?PartlyYes

Common mistakes

How Kunads handles this

Kunads connects Meta Ads, Google Ads and GA4 with your Shopify, WooCommerce or Magento orders. For each campaign, it shows each platform's number next to what the shop recorded, together with profit and POAS, and steers the account on blended ROAS: all revenue ÷ all ad spend. It does not offer a multi-touch attribution model or MMM. The comparison above works just as well in a spreadsheet.

Sources

Kunads works this out every morning from your real orders — per campaign, for Meta and Google, and its agents propose the fix. Nothing changes until you approve.

Get a free profit audit Try it free for 14 days

Questions people ask

Why does Meta show a different number of sales than Shopify?

Meta counts purchases within 7 days of a click, 1 day of a view and, where set, 1 day of an engagement, reports them on the impression date, and can include modelled conversions. Shopify records each order once, on the day it was placed, and usually credits it to the last visit with a known source.

Why do my Facebook ads conversions not match Shopify orders on the same day?

Meta's Ads Manager reports a conversion on the date of the ad impression, not the date of the order. A click on Monday and a purchase on Friday shows up on Monday in Meta and on Friday in Shopify. In Ads Reporting you can switch to time of conversion.

Why does Google Ads show fewer conversions than my shop?

The usual causes are a tag that does not fire on every order, visitors who decline cookies (consent mode then sends limited or no data), and enhanced conversions being switched off. Check the conversion action status and use Tag Assistant before you change any bids.

Should I trust Meta or Shopify?

They answer different questions, so neither is the whole picture. Shopify knows how much you sold; Meta and Google can see views and cross-device journeys the shop cannot. Look at them side by side, and steer the account on blended ROAS: all revenue divided by all ad spend.

Can Meta and Google count the same order?

Yes. Each platform assigns credit among its own ad interactions, so one order can be counted once by Meta and once by Google. Add the two platforms' numbers together and compare them with total orders to see how much they overlap.

How often should I compare platform numbers with my shop?

Once a month is enough for most shops, plus after any tracking change, such as a new checkout, a consent banner change or a Conversions API set-up. Use a period that ended at least 7 days ago so late conversions have arrived.