GA4 revenue vs Stripe and Shopify: why they never match

GA4 records revenue when the purchase event fires on your site. Its revenue equals the value that event carried, converted to the property currency, and Google Analytics reports tax and shipping as separate monetary metrics alongside it. Shopify records every order your store made from every channel, and its total sales figure adds taxes, shipping and fees on top. Stripe records the money that actually moved: charges captured, refunds processed, fees taken. Three systems, three definitions, so the totals differ even when nothing is broken.

• GA4 only sees visits where its tag ran. A purchase in a checkout that never fires the event, or from a browser that blocks the tag, never reaches GA4 even though Shopify and Stripe recorded it.
• Shopify total sales includes taxes, shipping and checkout fees. If your store sends GA4 only the item total of each purchase, GA4 runs lower by exactly that difference.
• Refunds move at different times. Shopify and Stripe reduce the period the moment a refund is processed; GA4 keeps the original purchase unless a refund event is sent.
• GA4 converts spend to its reporting currency, processes in daily batches in the property's time zone, and can withhold small rows behind privacy thresholds.

GA4 measures what its tag sends. For a web store that is normally one purchase event on the checkout confirmation step, with four monetary fields: value, tax, shipping and currency, plus a unique transaction ID. Google's own ecommerce guide populates metrics such as item revenue and total revenue from those fields.

• GA4 revenue equals the value the purchase event carried, with tax and shipping as their own metrics. Google's currency reference lists purchase revenue, tax and shipping as separate monetary metrics, and notes that if you set a value, currency is required for revenue metrics to be computed accurately.
• Values are converted to the property's reporting currency. Google converts using the prior day's exchange rate, so a store that sells in several currencies can look different inside GA4 than on its payment reports.
• Google deduplicates purchase events that share the same transaction ID, so a reloaded confirmation page does not double count an order by itself. It counts again only when the repeat event carries a missing, empty or changing transaction ID.
• Only visits that ran the tag count. Visitors who block JavaScript, decline analytics consent, or leave before the confirmation page loads send no purchase event at all.
• GA4 works in daily batches in the property's time zone. Google says data processing can take 24 to 48 hours and reports can change during that time, with some late events arriving up to 7 days late.
• Privacy thresholds can withhold rows. Google applies data thresholds so nobody can infer an individual user, and small rows can be hidden from reports and explorations.

GA4 answers one question well: what did my site's tag see, from every route a visitor took. That is why its revenue starts from the tag and never from the shopping cart or the bank.

Shopify records what the store knows: orders from every channel, plus returns. Its finance reports separate gross sales, discounts, sales reversals, shipping, taxes and fees, and its total sales figure describes how much customers spent overall.

• Total sales is not the same as product revenue. Shopify defines it as gross sales minus discounts minus sales reversals, plus taxes, shipping and fees. Net sales is a smaller figure with shipping and taxes removed.
• Refunds appear the day they are processed. Shopify shows a return as a negative value on the refund date, so the current month simply shows less revenue from that day on.
• Shopify counts every channel it recorded: online store, point of sale, draft and manual orders, buy button, subscriptions and wholesale. Orders that never touched your website show in Shopify but can never appear in GA4.
• Shopify reports are near real time. Help Center states finance reports are up to date within about a minute, where GA4 is still processing daily batches.

Shopify answers a different question: what did my store sell, across every way a customer could buy. That is why its total is built from orders, not from web visits.

Stripe records money movement: charges, captures, refunds, disputes, fees and payouts, at the moment each one happens. Its own revenue recognition documentation treats a payment as recognized when it occurs and refunds and disputes as negative revenue.

• Charges are counted when they are captured, and refunds are subtracted the moment they are processed. A charge declined or refunded later never stays in the net.
• Fees are separate. Stripe reports what the customer paid and what you received after its fees, and both differ from GA4's event value.
• Stripe only sees payments that went through its gateway. Cash, bank transfers, other wallets and manually settled orders show in Shopify but not in Stripe, while GA4 may have fired for those web orders either way.
• Balance and payouts are cash movement. As Shopify notes for its own Stripe-powered balance report, such a report reflects funds received, not revenue for accounting purposes.

Stripe answers the most financial question of the three: what money actually moved. That is why it is the natural reference point for a monthly reconciliation.

The reasons below follow the vendors' own reference pages from the sections above. Each cause is a definition or a timing difference, and several can stack in a single store:

• Different definitions of one order. Shopify total sales adds taxes, shipping and fees; Stripe reports captured money minus refunds and fees; GA4 reports the value the purchase event carried. The same order can legitimately be three different amounts.
• GA4 only sees tracked web visits. Point of sale, draft and manual orders, subscriptions and phone orders show in Shopify and often in Stripe, and never in GA4. This is the classic reason GA4 runs below the monthly store total.
• Missing or blocked events. Consent declines, ad blockers, a redirect after checkout, or a confirmation page without the tag mean the order never sends. Shopify and Stripe still show the sale.
• Timing and time zones. GA4 batches daily in its property time zone and can take 24 to 48 hours to settle. Shopify is near real time and Stripe records the capture as it happens, so any day boundary splits orders differently between the tools.
• Refunds at different moments. Shopify and Stripe apply a refund on the day it is processed. GA4 keeps the original purchase until a refund event is sent, and many stores never send one, so GA4 stays higher after a refund-heavy month.
• Currency conversion. GA4 converts values to its reporting currency with the prior day's exchange rate. A multi-currency store can see GA4 totals drift from its payment reports in every market.
• Privacy thresholds and batch processing. GA4 withholds small rows from reports to protect individual users, and the newest days are still settling, so a fresh comparison always looks worse than a settled one.
• Purchase events without a stable transaction ID. Google Analytics deduplicates purchase events that share the same transaction ID, so the same order firing again is not double counted. GA4 runs above the payment report when repeat purchase events carry a missing, empty or changing transaction ID, for example when a page reload generates a fresh ID, because the same order is then counted again.

None of these is a bug in any tool. Each one is counting its own defined thing, accurately. The gap only needs investigating when it changes suddenly, when almost no web orders reach GA4, or when GA4 runs above the payment report for days.

• Compare the same thing. Pair GA4 purchases and revenue with the online store orders in Shopify or the matching captures in Stripe, not with the all-channels store total. Point of sale and manual orders should be on neither side of the comparison.
• Compare the same window, a few days back. Skip the newest day or two on both sides so GA4 daily processing has settled, and use identical dates.
• Check the purchase event. It should fire exactly once on the confirmation page with a stable transaction ID. Then check what your integration puts in the value field: if it sends the item subtotal only, GA4 runs below Shopify total sales by the taxes and shipping that never reached it. That is a definition difference, not a leak.
• Adjust for refunds before judging. Shopify net sales and Stripe net amounts already have them; subtract refunded purchases from GA4 or send a refund event so both sides describe the same money.
• Watch the direction, not the day. A stable weekly gap is normal and definitional. A sudden jump, a month where GA4 shows almost no orders, or GA4 consistently above the payment report is what deserves a tag and transaction ID review.

If GA4 shows far fewer orders than Shopify's online store for the same settled week, check that the tag loads on the checkout and confirmation pages and that the purchase event fires once per order. Google's own ecommerce guide covers the recommended event setup.

If you want a second, independent view of your site, add a tracking code you own. Hitsteps uses a single tag on the site that starts a real-time visitor list with pages, countries and referrers, UTM and ad attribution, actions, goals and revenue, all in one dashboard. It records the visits its tag sees as they happen, and it runs alongside GA4, Shopify and Stripe for as long as you want all three.

That gives you a revenue view that comes from your own site, next to the Google and payment numbers, with the same attribution caveat. Like any tag, it only sees visits where the tag loads and JavaScript runs, so treat it as a second view, not a perfect total. Where your GA4 revenue and your payment data disagree, you can open the individual visits and see which orders actually arrived from your tracked pages.

Definitions and reasons above follow the vendors' own documentation, checked 12 November 2026:

• Google: Set up a purchase event (developers.google.com, set up a purchase event)
• Google: Measure ecommerce (developers.google.com, measure ecommerce)
• Google Analytics Help: Currency reference (support.google.com, answer 9796179)
• Google Analytics Help: Data freshness (support.google.com, answer 11198161)
• Google Analytics Help: About data thresholds (support.google.com, answer 9383630)
• Google Analytics Help: Set up Analytics for a website and/or app, property time zone (support.google.com, answer 9304153)
• Google Analytics Help: Troubleshooting purchase events, transaction ID deduplication (support.google.com, answer 12313109)
• Shopify Help Center: Finance reports (help.shopify.com, finance reports)
• Shopify Help Center: Shopify Payments activity report (help.shopify.com, payouts activity report)
• Stripe Documentation: How Revenue Recognition works (docs.stripe.com, revenue recognition)