GA4 Revenue Doesn't Match Shopify: Full Diagnosis

The symptom

Someone pulls up Shopify’s Sales report and GA4’s ecommerce report for the same 30 days, and the numbers don’t line up. Sometimes it’s a rounding difference nobody would notice. Sometimes it’s tens of thousands of dollars, and now finance and marketing are in a meeting arguing about which system is lying.

Neither system is lying. They’re built to answer different questions, and treating them as two attempts at the same number is where the confusion starts.

Direct answer

A small gap between GA4 revenue and Shopify’s Total Sales is structural: attribution-model differences, currency handling, and refund treatment produce some variance even in a correctly configured store. As a working rule, a gap in the low single digits is usually explainable within an afternoon of checking. A gap that runs into double digits — or keeps growing — points to something specific: missing purchase events on part of the funnel, consent blocking a segment of traffic, or a currency/filter misconfiguration. Finding out which requires matching orders one by one, not comparing two dashboard totals.

Causes, ranked

1. Missing purchase paths. The most common cause of a large gap. If the purchase event only fires reliably on the standard checkout path, orders completed through Shop Pay, Apple Pay, POS, subscription renewals, or B2B checkout can silently never reach GA4 while still landing in Shopify.
2. Consent. If a visitor declines analytics consent, GA4 never receives that purchase event — but Shopify still recorded the order. A store with meaningful EU or opt-out traffic can lose a real share of its purchase data this way without anything being “broken” in the technical sense.
3. Refunds. GA4 doesn’t automatically net out a refund unless a refund event is explicitly sent. If Shopify’s revenue figure is net of refunds and GA4’s isn’t, the gap grows with your refund rate.
4. Currency and tax configuration. A mismatched currency parameter, or inconsistent inclusion of tax and shipping between the two systems, produces a gap that behaves like a near-constant percentage rather than a shifting count of missing orders.
5. Filters. Overly broad internal-traffic exclusions, IP filters, or referral exclusion lists in GA4’s Data Settings can quietly drop real customer sessions, not just staff and testing traffic.

How to diagnose it

1. In Shopify Admin, go to Analytics → Reports → Sales over time, and pull total sales and order count for a closed 30-day window.
2. In GA4, go to Reports → Monetization → Ecommerce purchases, and pull purchase revenue and transaction count for the identical date range.
3. Before comparing, check Admin → Property Settings → Time zone in GA4 against your Shopify store’s timezone — a mismatch shifts day boundaries and skews daily comparisons even when totals are fine.
4. Export order-level data from Shopify (Orders → Export), keeping order number, timestamp, total price, and financial status.
5. Export event-level GA4 data via Explore → free-form exploration, using transaction_id and purchase_revenue as dimensions/metrics, or via BigQuery if it’s linked.
6. Match the two exports by order number / transaction_id. Flag orders present in Shopify but missing in GA4 — that’s your purchase-path or consent gap.
7. Check consent state on the purchase event in GA4 → Admin → DebugView during a live test, to confirm whether analytics_storage is granted before the event fires.
8. Check Shopify orders filtered by refund status against whether GA4 revenue drops correspondingly for those orders.
9. Compare GA4’s property currency (Admin → Property → Currency) against your store’s default currency and any Shopify Markets multi-currency setup.
10. Review Admin → Data Settings → Data Filters for internal-traffic or IP exclusions that might be scoped too broadly.

Decision table

Cause	Signal you’ll see	Fix
Missing purchase paths	Shopify order count exceeds GA4 transaction count by more than a few percent; gap concentrated on specific checkout paths	Trace the exact path (Shop Pay, Apple Pay, POS, subscriptions) and confirm the Customer Events pixel actually fires there
Consent	Gap correlates with a specific region or a cookie-banner update date	Check Consent Mode default/update signals; confirm analytics_storage is granted before the purchase event fires
Refunds	GA4 revenue stays flat when Shopify’s net revenue drops after refunds	Send a refund event to GA4, or exclude refunded orders manually from your reconciliation baseline
Currency/tax config	The delta is a near-constant percentage rather than a shifting order count	Align GA4’s currency parameter and property currency with the store; agree on tax/shipping inclusion on both sides
Filters	Known real segments (specific regions, referrers) are missing only from GA4	Review Data Filters and internal-traffic definitions for overly broad exclusions

Fix it yourself, or bring in help

You can do the first pass yourself: pulling both exports, checking the timezone and currency settings, and reviewing the Data Filters list is an afternoon of work for anyone comfortable in Shopify and GA4 admin. Where it gets harder is tracing a specific missing checkout path (which usually means digging into the Customer Events pixel or GTM setup) or diagnosing a consent implementation that’s silently blocking a whole segment. If the gap is over roughly 5–10% and doesn’t shrink after checking the items above, or if it’s tied to a checkout path you can’t fully trace yourself, that’s the point to bring in a tracking audit rather than keep guessing from dashboards.

Related reading

For the mechanics of how order-level matching works, see order reconciliation. If the gap traces back to purchases never firing at all, see GA4 not tracking purchases. If it traces back to attribution rather than revenue, see GA4 unassigned traffic.