Why doesn't GA4 revenue match your store?
Google Analytics 4 (GA4) revenue rarely matches your store exactly, and it isn't designed to. The useful question is whether the gap is explained. Reconcile order counts first, then the value of each matched order: most gaps come from consent and browser loss, time zones, what value includes, refunds, currency, or orders that are missing or counted twice.
Symptom
For example, your store reports £12,400 for last month and GA4 shows £9,100, or £15,800. Or the totals are close but individual channels look wrong. Your agency reports from GA4 and your accountant from the store, and the two never agree.
Possible causes
- Cause A: orders not tracked. Consent declined, ad blockers, off-site payments, or orders created outside the online checkout. GA4 lower than the store.
- Cause B: orders counted twice. Two integrations send the purchase, or a reload re-sends it. GA4 higher than the store. See duplicate purchase events.
- Cause C: a different definition of value. Your store's sales figure may include shipping and tax, and subtract discounts and returns. GA4's purchase revenue is whatever your implementation sends as
value. - Cause D: refunds. Store reports usually net off returns. GA4 only reduces revenue if your setup sends
refundevents, and most basic setups don't. - Cause E: time zones. The GA4 property's reporting time zone differs from the store's, so orders near midnight fall on different days.
- Cause F: currency. Multi-currency stores send values in the customer's currency. GA4 converts to the property currency, and Google says
currencyis required whenevervalueis set for revenue to be computed accurately. - Cause G: attribution. Totals can agree while channel figures disagree with Google Ads or Meta, because each tool attributes conversions with its own rules.
How to check
- Fix the frame. Choose a complete week. Check the GA4 property's reporting time zone and currency in Admin, Property details, and your store's time zone and currency in its settings.
- Compare order counts, not money. Export store orders for the week. In GA4, build an Exploration with Transaction ID and Purchase revenue. Count matched, store-only and GA4-only IDs.
- Look at GA4-only IDs. Test orders, duplicates, or IDs in a different format (order name versus order ID).
- Look at store-only orders. Group by sales channel, payment method, device and country.
- Compare value on matched orders. Take ten matched orders and compare GA4 value with the store's order total, item subtotal, shipping, tax and discount.
- Check refunds and currency. Search GA4 for
refundevents. For international orders, check thecurrencysent in a test order.
Illustrative reconciliation of one matched order, with invented figures:
| Field | Store order | GA4 event |
|---|---|---|
| Items after discount | £50.00 | value: 50.00 |
| Shipping | £3.95 | shipping: 3.95 |
| VAT (included in price) | £8.33 | tax: 8.33 |
| Order total | £53.95 | not sent |
GA4 purchase revenue here is £50.00 and the store total is £53.95. Both are correct. They measure different things.
What the result means
- Most orders matched, values differ by a consistent rule: cause C. Not a bug. Document the definition so reports compare like with like.
- Store-only orders spread evenly: cause A, consent and browser loss. Some gap is normal in a consent-aware setup.
- Store-only orders concentrated in one gateway, channel or date: a real tracking fault. See Shopify purchases missing or WooCommerce purchases missing.
- GA4-only or repeated IDs: cause B.
- Gap grows month on month as returns are processed: cause D.
False positive. Comparing GA4 "Total revenue" with the store's "Total sales" can make a correct setup look broken. Total revenue in GA4 can include more than purchases, and Total sales in your store already accounts for returns, shipping and tax. Compare matched orders and defined fields, not headline totals.
How to fix it
- Fix real faults first: missing routes, duplicate sources, absent
currencyortransaction_id. - Decide what
valueshould represent and send tax and shipping as separate parameters, as Google's ecommerce documentation describes. - If you need net revenue in GA4, send
refundevents with the original transaction ID. - Align the GA4 reporting time zone with the store if you can, noting that changing it affects data from that point on.
- Agree with your team which system is the record for revenue (normally the store), and use GA4 for behaviour and trends.
What not to do
- Don't change
valueto make GA4 match the store total this week. You will break comparisons with everything before. - Don't add a second purchase route to close the gap.
- Don't expect consented tracking to measure every purchase. It can't.
When to request help
A GA4 and GTM audit reconciles orders against GA4 transactions, explains each source of difference with evidence, and separates expected gaps from faults.
Related guides:
- Why are purchase events counted twice?
- Shopify purchases not showing in GA4?
- WooCommerce purchases missing from GA4?
Not sure what's wrong?
Send us your store address. Mikael will review the visible tracking signals and explain what can be checked from your public pages.
Sources and updated date
- Google for Developers: Measure ecommerce
- Google for Developers: Recommended events
- Google Analytics Help: Currency reference
- Google Analytics Help: Minimize duplicate key events with transaction IDs
- Google Analytics Help: Introduction to user consent management
Last checked against official documentation: 18 November 2026.