Field notes from the founders

Shopify vs GA4 revenue: why they never match, and which to trust

November 17, 2026
Every Monday trading meeting has a version of this. Shopify says last week's sales were $400,000. GA4 says $340,000. Someone spends the morning hunting for the missing $60,000, finds half an explanation, and the meeting moves on with nobody quite trusting either number.A Shopify vs GA4 revenue discrepancy is one of the most common questions on the Shopify and Google forums. Occasionally a tag is broken, but GA4 and Shopify are built to count different things in different ways. Most of the gap comes from how the data is collected, before attribution even starts, and once you know the reasons you can stop hunting and start using each tool for what it's good at.

Attribution can't be solved, and this gap starts before it

Attribution has no right answer. No model can say for certain which ad, email or search deserves the credit for an order, and anyone promising otherwise is selling a model with a confident name.Most of the gap between Shopify and GA4 comes from collection: which orders each tool sees at all, and what it counts when it sees one. That's the under-appreciated half of every "why don't my numbers match" question, and GA4 against Shopify is the clearest example of it.

GA4 watches the browser; Shopify keeps the ledger

Shopify records every order on its own servers, whatever happens in the shopper's browser. It's the ledger.GA4 only knows what the browser tells it. Shopify's own Google & YouTube app sends GA4 a purchase event from the browser, through Shopify's web pixel events, and Shopify's developer documentation says that event fires "typically on the Thank you page". If that page doesn't load, the purchase is never sent. Everything that follows comes from that one difference.

Why GA4 revenue is lower than Shopify

Some shoppers block it. Shopify says it plainly in its own help centre: customers can use browser extensions to block Google Analytics from tracking their sessions and purchases. Privacy-focused browsers do some of the same work. The order still lands in Shopify; GA4 never hears about it.Some shoppers decline cookies. If you show a cookie banner and use Google's consent mode in basic mode, Google's tags don't load at all until a visitor agrees, so a visitor who declines is invisible to GA4. In advanced mode the tags send cookieless pings instead, and GA4 can model the missing users and sessions, but only once a property passes Google's thresholds (at least 1,000 events a day from visitors who declined, for at least seven days, among other conditions), and the modelling covers users and sessions, not the purchases themselves. Shopify switches its banner on automatically for visitors in the UK and EEA if you have active markets there, so a US-only store may show none by default. US shoppers who opt out of data sale or sharing can still stop pixels configured as data sale from running.Some orders never touch a browser. Subscription renewals from Recharge or Skio are created by the app on Shopify's servers when it bills the customer. There's no checkout and no thank-you page, so there's nothing for the pixel to fire on. The same goes for draft orders, point-of-sale and orders created by other apps. Shopify counts them all. For a subscription brand, renewals alone can be a large share of the gap.Some purchase events get thrown away. GA4 deduplicates purchase events from the same user with the same transaction ID, which protects you from a customer refreshing the thank-you page. But Google warns that it will also deduplicate every purchase sent with an empty transaction ID. A hand-built tag that always leaves the field blank is easy to spot. A flaky one is the real risk: a tag that usually passes the order ID but sometimes fires before the order details have loaded, the classic race condition that bites shoppers on slow connections. Every purchase it sends with a blank ID can be thrown away, and nothing on the dashboard tells you.

Why GA4 can be higher than Shopify, too

Refunds never reach GA4. GA4 only subtracts refunds if you send it a refund event, and Shopify's Google & YouTube app doesn't send one. Shopify takes refunds off its sales on the day they're processed. Left alone, GA4 keeps every refunded order at full value, which partly offsets everything it missed above and makes the gap look smaller than it is.It depends which Shopify number you compare. Since April 2025, Shopify's app sends GA4 a purchase value of subtotal minus discounts, which excludes tax and shipping, in line with Google's own guidance. Shopify's net sales also exclude tax and shipping, so that's the like-for-like comparison. Shopify's total sales include tax and shipping, so comparing GA4 against total sales manufactures a gap of several per cent before anything else happens.

The small ones that still move the number

Time zones. GA4 records a visit on the day it happened in the property's time zone, and Shopify reports in the store's. If they differ, orders near midnight land on different days. Shopify's own help centre lists this as a cause of discrepancies.Currency. GA4 converts other currencies to the property's currency at the exchange rate from the day before the transaction. Shopify reports in your store currency by its own rules. If you sell in several currencies, the two will drift apart a little every day.Timing. Google says GA4 data can take 24 to 48 hours to process. Yesterday's GA4 revenue is nearly always short.

A worked example

Take an illustrative week for a $20m subscription brand, in round numbers. Shopify shows $400,000 of net sales.Add back refunds. $16,000 of refunds processed that week came off Shopify's figure. GA4 never heard about them, so on GA4's basis the week is worth $416,000.Take out the orders with no browser. $48,000 of subscription renewals were created by the subscription app. GA4 can't see them, which leaves $368,000.Take out the browsers GA4 couldn't see. Ad blockers, declined consent and a few thank-you pages that never loaded hide about 8% of online checkouts from GA4. That's roughly $29,000, leaving $339,000.Allow for the edges. Time zones, currency and late processing move it a few thousand dollars either way.GA4 shows about $340,000. A $60,000 gap, 15% of sales, and every dollar of it has an explanation. None of it is a bug.

What we'd set up

Use one GA4 integration. Either Shopify's Google & YouTube app or a hand-built setup, not both, and check that every purchase carries its Shopify order ID as the transaction ID.Match the settings. Set the GA4 property's time zone and currency to match the store, and compare GA4 with Shopify's net sales, which leave out tax and shipping just as GA4 does.Get consent right. If you show a banner, connect it to Google's consent mode through Shopify's privacy settings, and use advanced mode so GA4 can model what it can't see, if your traffic is large enough to qualify.Leave what the browser can't see to Shopify. Google's Measurement Protocol can send events such as refunds to GA4 from your server, but Google itself calls it a supplement to tagging, and in our experience the effort of patching GA4 this way rarely produces anything worth having. We'd steer clear. Accept that GA4 won't see refunds or subscription renewals, and report both from Shopify and your subscription app, where they're complete.Make the tags harder to block. Google tag gateway, launched in May 2025, serves Google's tags through your own site's infrastructure, and Google says it lifts the signals it receives. It's worth a look if a meaningful share of your customers browse with blockers.Run a monthly health check. Take last month's online-store orders from Shopify and see what share has a matching transaction ID in GA4. Renewals and other server-created orders will never match, so leave them out. The share that does match will never be 100%, and the exact level matters less than the trend. If it drops suddenly, something broke: a theme update, a checkout change, a consent banner that started blocking more than it should. Fix that before you touch a budget.

Which number to use for which decision

Shopify is the number for revenue. It's the ledger, it reconciles to the bank, and it's the only one of the two that sees every order.GA4 is the number for behaviour: which landing pages convert, where shoppers drop out of checkout, how channels compare with each other. It's also a sensible default for sharing out channel credit, reconciled to Shopify's new customers, as we described in why Meta Ads and Shopify numbers don't match. Its revenue total doesn't belong in the board pack.The same logic applies to every other tool that reports revenue. Each one counts what it can see by its own rules, whether that's Meta, Google Ads or Klaviyo.

One ledger, sensible defaults, reasons written down

What the gap costs you is the Monday morning spent hunting for it, and the doubt it leaves behind. When nobody trusts the numbers, nobody acts on them, and decisions stall.The fix for a small or mid-sized business is a shared view of the world that everyone works from: Shopify as the ledger, GA4 for behaviour and as the default for channel credit, the known reasons for the gap written down, and a monthly check that tells you when something has broken. That's what a company brain for D2C is for. We rebuild one common view of the numbers from structured data across every system you run, with sources always cited, read the business LTV:CAC first, and our agents act on that view in the open.If you're below roughly $1m in revenue, the samples are usually too small to separate signal from noise, and the setup checks above are the best place to start.If you'd like a second pair of eyes on why your Shopify and GA4 numbers disagree, book a call at signalovernoise.app/book-a-call or drop us an email at hello@signalovernoise.app.