Why GA4, Meta, Google Ads and the store don't match

GA4, Meta, Google Ads and your store measure different things. See what each counts, why the totals don't add up, and how to compare them.

GA4, Meta Ads, Google Ads and your store almost never show the same sales number. That is expected: each one answers a different question. The store counts the orders it recorded. GA4 counts the purchase events the site managed to send. Meta and Google Ads count the conversions each platform can attribute to its own ads, under its own rules.

If you open the four dashboards on the same day and the totals do not line up, start with what each side is counting.

What is each source measuring?

SourceWhat it countsThe question it answers
StoreOrders recorded at checkout, with status (paid, pending, cancelled, refunded)How many orders did the store receive in this period?
GA4Ecommerce events sent by the site or the app, such as purchase. Google Analytics does not collect these events automatically.How do the sessions and purchases measured on the site split across channels?
Meta AdsConversions Meta can attribute to its ads, according to the ad set's attribution settingHow many purchases does Meta credit to these ads?
Google AdsConversions Google Ads can attribute to its ads. In the default report, the conversion is dated to the ad interaction, not to the order date.How many conversions does Google Ads credit to these ads?

The store is the record of what arrived at checkout. GA4 only sees what the browser or the app sent. Meta and Google Ads only credit what fits each platform's attribution rules. Meta itself says conversion counts in Ads Reporting can differ from third-party tools, because the tools detect, define and calculate conversions in different ways. See About Conversion Count Differences Between Meta Ads Reporting and Third-Party Reporting Tools.

In Google Ads, Data discrepancies: Factors and troubleshooting lists frequent causes of gaps with Analytics and with internal reports: conversion date, windows, counting settings, view-through conversions and the attribution model.

Why does adding Meta and Google exceed the store's total?

Because each platform only sees its own ads and can credit the same purchase.

A common example. Someone clicks an Instagram ad, leaves without buying, comes back two days later through a paid Google search and places the order. Meta can credit the purchase if it still falls inside the ad set's attribution window. Google Ads can credit the search click. The store records one order. The two dashboards added together come out higher than the store's total.

In Meta's Help Center, About Attribution Models and Attribution Settings describes the default windows for website conversions, including click-through credit and view-through credit (when the person only saw the ad, without clicking). The guide Why Meta Ads sales don't match your store covers that rule and the gap between report date and order date.

Google Ads help also draws a clear limit: Google Ads only reports conversions when there are Google ad interactions from the same account. Another tool may assign the same sale to a different channel, or add up clicks from several accounts. Each dashboard answers its own question. The sum is not the total of paid orders.

Why doesn't GA4 match the store either?

GA4 is not the store's cash register. It measures what the site or the app sends.

In the Ecommerce purchases report, Google Analytics states that events such as add_to_cart and purchase are not collected automatically. You have to send them from the site or the app. If the purchase event does not fire, the sale does not enter the report, even when the order is already in the store. That happens when the thank-you page does not load, when a blocker stops the tag, or when a consent banner blocks Google tags. On Unblock Google tags when using consent mode, Google says that if tags are blocked, they send no information at all.

Revenue in GA4 also depends on what the event carries. In Fix missing revenue data, Google Analytics explains that revenue metrics come from purchase event parameters such as value, currency and transaction_id. If those fields are missing, wrong or repeated, GA4 revenue drifts away from the store even when the event fires.

The channel GA4 assigns the purchase to can also differ from Meta and Google Ads. In Get started with attribution, Google Analytics says the default model is data-driven attribution: credit for the key event is distributed across touchpoints, with a calculation specific to the property. There are also last-click models (paid and organic, or Google paid channels only). Changing the model changes the channel in the report, without changing the order in the store.

A UTM helps label the visit, but it does not make GA4, Meta and the store start counting the same thing. How to Use UTM Parameters for Meta Ads covers the labelling part.

Server-side tracking can increase the events a platform receives when the browser fails. That does not turn the Meta or Google number into the store's order total. What Is Server-Side Tracking? explains the reach and the limits.

Why don't the report dates line up?

The store usually shows the order on the day it was created or paid. A click on Monday, a delayed payment on Tuesday and confirmation on Wednesday already spread the same order across three windows.

Google Ads' default report does not use that date. Data discrepancies: Factors and troubleshooting explains that Google Ads reports conversions on the ad impression date, while other tools attribute them to the conversion date. To bring the comparison closer to the company's own sales, Understand conversions by time with new columns describes the "Conversions (by conv. time)" column, which records the conversion at the moment it happened.

On Meta, How Conversions Are Attributed in Commerce Manager states that Ads Manager reports based on the impression date, not necessarily the day of payment. Ads Manager's "yesterday" and the store's "yesterday" are rarely the same slice.

Pending orders also throw the comparison off. A delayed payment can create the order before the money arrives. If the store shows created orders and the ad dashboards show Purchase, you are comparing different things. Separate created, awaiting payment and paid.

Google Ads help asks you to wait 24 to 48 hours before comparing results with Analytics, and notes that after significant changes, conversion data can take up to 7 days to appear in full.

How can I compare these numbers without fooling myself?

Use a short, repeatable method. The aim is to explain most of the gap, not to zero it out.

  1. Pick a closed week, not "yesterday". Recent days still change as older conversions arrive.
  2. In the store, use only paid orders, or the net report you use for cash. Note cancelled and refunded orders separately.
  3. Do not add Meta + Google + GA4 to match the order total. Each one can credit the same purchase.
  4. In Google Ads, compare with the "Conversions (by conv. time)" column when the target is the store's order day. Note the account time zone.
  5. In Meta, note the ad set's attribution setting, for example 7-day click or 1-day view, and the account time zone. The Meta and store guide already linked above covers that step.
  6. In GA4, check that the purchase event is being sent and that value, currency and transaction_id are correct. Note the property's attribution model.
  7. Separate the decisions. For cash, use paid store orders and total ad spend. To compare campaigns inside one platform, use that platform's report, always with the same attribution rule. To understand behavior on the site, use GA4.

When does it make sense to start from store orders?

When the question is "how much did the store actually sell, and which ad brought the paid order?", not only "how many conversions did each platform attribute?".

You need the order coming from the store, with status, and a way to connect that order to the clicks and visits. Independent attribution tools exist for that. Clakta is one of them: it brings the numbers Meta and Google Ads report and the orders the store confirmed into one place, side by side, so you can compare them without opening several dashboards. Revenue comes from the same store orders, with status; each order enters that total once; a pending delayed payment does not count as revenue yet; refunds and cancellations update the same order. The pixel and GA4 stay in place: Clakta runs beside them, does not change the platform reports and does not replace GA4 (What is Clakta, How attribution works). The credit models, if you want to switch them, are in What Is Multi-Touch Attribution?. For stores, see the ecommerce page.

The store, GA4, Meta and Google Ads remain different numbers. In Clakta, store orders and the figures Meta and Google Ads report appear on the same screen.

Frequently asked questions

Is it normal for the four numbers to be different?

Yes. Each source measures something different, with its own date and rule. The gap only becomes a tracking problem when, after you align the period, time zone, order status and model, a hole remains that you cannot explain, for example a purchase event that does not fire.

Which number should I use to decide budget?

Use two. For the health of the business: paid store orders and total media spend. To optimize inside Meta or Google Ads: that platform's own metrics, always with the same attribution setting across the campaigns you compare.

Can I add Meta and Google to reach the store's total?

No. Both platforms can credit the same order. The sum often exceeds the total of paid orders.

Does GA4 replace the store report?

No. GA4 shows the events the site or the app sent. The store shows the orders it recorded. They are different reports, and both can be useful at the same time.

Are modeled conversions in Google Ads the same as store orders?

No. In About consent mode modeling, Google Ads describes modeling as an estimate of conversions from people who declined cookies, based on observable journeys. That estimate can appear in the Conversions column and be used for bidding. It is not the list of paid store orders.

Do UTMs make the four numbers match?

No. A UTM labels the visit. You still need the order and a way to connect the two. UTMs help with checking; they do not replace attribution or payment status.

Is there a way to see all of these numbers in one place?

Clakta brings the numbers Meta and Google Ads report and the store's orders into one place, side by side. You can compare the two ad reports with what the store recorded, without moving from one dashboard to another. GA4 stays in Google Analytics: Clakta does not replace that report and does not show its data.

Can I zero out the gap between the dashboards and the store?

Not honestly. The useful aim is to explain most of the gap and to decide spend with a clear paid-order rule.