Skip to content

Why do Meta, Google and your store show different sales?

Short answer

Your store counts every order; Google Ads and Meta count only purchases they credit to their own ads, by their own rules for the day and time window. In Germany, § 25 TDDDG adds to this: people who decline in the cookie banner still order, but the ad accounts miss them or only estimate them. The numbers only become comparable with the same period, the same time zone and a shared definition of a “sale”.

Why the numbers are never the same

Your store counts orders: every completed order is in the back end, that is your store’s admin, wherever the person came from. Google Ads and Meta count something else, namely purchases they attribute to one of their own ads. This assignment is called attribution, and each platform has its own rules for it.

  • The day: in its standard columns, Google Ads assigns a purchase (called a “conversion” there) to the day of the click, not the day of the purchase⁠2. According to its developer documentation, Meta has reported website purchases on the day of the purchase since 10 June 2025⁠3. Your store counts by order date.
  • Click or view: depending on the ad set’s setting, Meta also attributes a purchase to an ad that was only viewed, not clicked⁠3. Google has such purchases too; they appear in their own columns, such as “View‑through conversions”⁠2.
  • Duplicate reports: if someone reloads the order confirmation, or a purchase arrives by two routes, it can be reported twice, unless a unique identifier such as the order number is sent with it⁠4⁠5⁠6.
  • Consent: people who decline in the cookie banner still order, but the ad accounts’ measurement scripts do not record them, or record them only without cookies⁠1⁠7.

On top of that, Google and Meta only see their own touchpoints. If someone first saw a Meta ad and later clicked a Google ad, both platforms can count the same purchase for themselves. The sum of the ad accounts therefore never replaces the number in your store.

§ 25 TDDDG, a German law on privacy in digital services, allows information to be stored on users’ devices, or read from them, only with their consent. There are exceptions, among others for what is strictly necessary for a service the user has expressly asked for to work⁠1. So stores ask for consent to advertising and statistics cookies through the cookie banner; your lawyer decides what counts as strictly necessary in your store.

For your numbers this means: if someone declines, the order still happens in the store. But the ad accounts do not see this purchase, or see it only partly. The gap grows with the share of people who decline, not with the quality of your ads.

For this, Google offers Consent Mode, a consent setting for its measurement scripts. In the basic version, Google’s scripts send nothing at all without consent; in the advanced version, they send signals without cookies, from which Google estimates missing values⁠7. Estimated values are not counted orders. So when you compare, note which version runs in your store.

Sample week: how to break down the gap

An example with round numbers, not from a real store: the store reports 100 orders in a week; Google Ads and Meta together report 84 purchases. That sounds like a gap of 16. But the real question is how many orders the ad accounts actually attribute to an ad click.

One week, 100 orders in the store

Google Ads reports (conversions by conv. time)
46
Meta reports (website purchases)
38
The same order, counted by both
12
Counted by Meta only after a view, without a click
9
Reported twice, without the order number as identifier
3
Recorded orders after an ad click
60

All figures are sample values. The other 40 orders came by other routes, such as search without an ad, the newsletter or a direct visit, or after an ad click by people who declined cookies, and so were not recorded.

Sample

Whether purchases after merely viewing an ad count is a choice, not an error. What matters is that everyone involved uses the same definition. Duplicate reports, on the other hand, are a setup error, and that can be fixed.

Who counts what, and on which day?
QuestionYour storeGoogle AdsMeta
Which day counts?Order dateDay of the click; in the “by conv. time” columns, the day of the purchase⁠2Day of the purchase for website purchases, according to Meta since June 2025⁠3
What counts?Every order in the systemPurchases Google attributes to an ad; “All conv.” also includes purchases after a mere view⁠2Purchases after a click or a view, depending on the ad set’s setting⁠3
Without consentThe order is still countedDepending on Consent Mode, no report or a report without cookies; Google estimates missing purchases with models⁠7Depends on how your cookie banner controls the measurement script
Protection against duplicatesOrder numberTransaction ID: a second report with the same ID is recognised⁠5Same event name and same event ID from the measurement script and the server within 48 hours⁠4
Time zoneStore settingSet when the account is created, cannot be changed⁠8Ad account setting

Google Analytics also counts purchases with the same transaction ID only once, but only for data from web streams, not from apps⁠6.

Let’s check this in your store.

In the free store review we look at this point too; on working days we write to you within 24 hours.

Get a review of my sales figures

Eight steps to comparable numbers

The list brings every source onto the same period and the same definition. Work through it once in full; after that, the weekly comparison with the template below is enough.

Make the numbers comparable

The weekly template to copy

Fill in the template on the same day every week, at the earliest 48 hours after the last day of the week. Google recommends waiting for this processing time before you compare final results⁠2.

Weekly sales comparison

Week: ____ to ____ Time zone: ________ Definition of “sale”: ________ Store admin: ___ orders · €___ revenue Google Ads, conversions (by conv. time): ___ · €___ Meta, website purchases (setting: ______): ___ · €___ Google Analytics, purchases: ___ · €___ Ad accounts together minus store: ___ Declines in the cookie banner, if your banner shows them: ___% Consent Mode: basic / advanced / off Notable this week: ________ Next step: ________

The template fits in a spreadsheet or a note; all that matters is that the same rows are filled in every week.

After four weeks you will see whether the difference is stable. If it suddenly jumps, look first for changes made that week: a new theme, a new cookie banner, a new app in the checkout.

Next step

We set up the counting so that your store, Google and Meta mean the same order, and check it with test orders. What the numbers say is in your report every month.

About this article

Written by
Qante Assist team
First published
Last updated

Frequently asked questions

Which number is the right one?

For orders and revenue, go by your store admin, because every order is there. The ad accounts show which purchases they attribute to their ads; that answers a different question.

How big can the difference be?

There is no fixed limit. Google writes in its help that, when you compare Google Ads with Google Analytics or Shopify, differences of up to 20% are to be expected because of different attribution models. What matters more is that the difference stays stable from week to week and that you know its causes.

Can I measure without consent?

Your lawyer decides that. In Germany, § 25 TDDDG allows access to the device without consent only in narrow exceptions, for example when it is strictly necessary for a service the user has expressly asked for. On the technical side, we set up what your cookie banner and your lawyer specify.

Sources (8)

  1. Federal Ministry of Justice and Consumer Protection, Germany (gesetze-im-internet.de)§ 25 TDDDG: Schutz der Privatsphäre bei Endeinrichtungen (opens in a new tab)Accessed: 1 October 2026
  2. Google Ads HelpConversion‑Tracking‑Daten auswerten (opens in a new tab)Accessed: 1 October 2026
  3. Meta for DevelopersMarketing API, Insights: notes on reporting time and attribution setting (Best Practices page) (opens in a new tab)Accessed: 1 October 2026
  4. Meta for DevelopersHandling Duplicate Pixel and Conversions API Events (opens in a new tab)Accessed: 1 October 2026
  5. Google Ads HelpWeniger doppelte Conversions durch Transaktions‑IDs (opens in a new tab)Accessed: 1 October 2026
  6. Google Analytics HelpDoppelte Schlüsselereignisse mit Transaktions‑IDs minimieren (opens in a new tab)Accessed: 1 October 2026
  7. Google for DevelopersConsent mode overview (opens in a new tab)Accessed: 1 October 2026
  8. Google Ads HelpEinstellungen für Sprache, Zahlenformat, Zeitzone und Währung (opens in a new tab)Accessed: 1 October 2026

The first step

Leave the store work to us

The free review shows the next three jobs and the plan that fits, within 24 hours on working days. No commitment.