GA4 revenue after refunds: why the number won't drop, and how to send a refund.
- “GA4 refunds not showing”
- “GA4 revenue doesn't go down after refund”
- “GA4 purchase revenue ignores refunds”
- “GA4 revenue higher than Shopify because of refunds”
- “how to send refund event to GA4 Shopify”
Baris Asa, tracking consultant, London · Last checked: November 2026
GA4 purchase revenue doesn’t drop after a refund because GA4 hasn’t been told about it. It subtracts a refund only when it receives arefund event with the same transaction_id as the original purchase. Shopify takes the refund off its sales on its own, so Shopify goes down and GA4 stays where it was. Usually nothing is broken: a step was never built.
This is a common reason GA4 runs ahead of Shopify when the order counts match. If GA4 has more purchases than orders, that is a different problem: the purchase firing twice. If GA4 and Shopify show the same orders and the same gross sales, and only net revenue differs, this is your problem. The wider comparison is in GA4 revenue higher than Shopify.
Why doesn’t GA4 revenue go down when an order is refunded?
Shopify and GA4 keep separate books. Shopify’s sales report defines a sales reversal as an order adjustment with a negative value, and refunds count. It shows the reversal as a negative amount on the day it was processed, not on the day of the sale. Net sales is gross sales minus discounts minus reversals.
GA4 has no link to Shopify’s order records. It only knows what the tags send. Google defines Purchase revenue as revenue from purchases “minus any refunds given”, and Refund amount as the total from refunds given. Both depend on refund events actually arriving. With none, Purchase revenue and Gross purchase revenue show the same number, and every refund the store has made is still counted as income.
How do I check whether GA4 receives refunds at all?
Do this in the GA4 interface, no developer needed:
- Look for the metric. In Reports, Monetization, Ecommerce purchases or Transactions (add it from the report Library if it’s missing), add Refund amount as a column. If it is zero or absent for a period when the store refunded orders, nothing is sending refunds.
- Compare the two revenue columns. Purchase revenue equal to Gross purchase revenue for a month with known refunds says the same thing.
- Check one named order. Refund one test order in Shopify, wait a day, and find its Transaction ID in the Transactions report. If the refund never appears, the sender is missing or its ID doesn’t match.
What has to be in the refund event?
Google’s developer reference for the refund event requires a transaction_id. value and currency go together: if you set value, currency is required for revenue metrics to be computed correctly. items is optional, but Google recommends it so that item-level refund metrics show in GA4.
The transaction_id must be the same one the purchase carried. A refund sent with a different ID, or none, can’t be matched to the sale and does nothing useful. This is why the purchase has to send the Shopify order number in the first place, and why a purchase with an empty or changing ID causes trouble twice.
| MEASURE | GA4 | SHOPIFY | NOTE |
|---|---|---|---|
| Orders | 300 | 300 | match |
| Gross sales / gross purchase revenue | £30,000 | £30,000 | match |
| Refunds | £0 | £1,800 | never sent |
| Net sales / purchase revenue | £30,000 | £28,200 | GA4 +6% |
Counts match, gross matches, and the whole gap is the refund line. That shape, a gap that equals the refund total and none of the other columns, is the test. If the gap is bigger than the refunds, something else is adding to it.
How do I send refunds to GA4?
There are three routes. Pick by who owns the shop’s tracking.
- An app or connector that already sends GA4 events. Some apps send
refund, some don’t. Refund one test order and look for the event. - Server-side, from the store’s refund webhook. The store can notify a URL you control when a refund is made (Shopify’s webhooks; check its developer docs for the current refund topic). A small service, or a custom client in a Google Tag Manager server container, turns that into a GA4
refundevent through the Measurement Protocol. Store the order’s originalclient_idwith the order, or the refund can’t be tied to the same user. Google’s reference includes a workedrefundexample for it. It needs aclient_id(orapp_instance_idfor an app stream), theapi_secretand the measurement ID. - Batch, once a day. A scheduled job that reads yesterday’s refunds and sends one event per order. It is the least elegant. It also needs no real-time plumbing, so there is less to break.
Two limits from Google’s Measurement Protocol documentation matter here. Events can be backdated up to 72 hours. Older ones are either stamped 72 hours ago or rejected, depending on validation_behavior. So a refund processed ten days after the order is not dated to the sale. Sent with no timestamp, it is dated when GA4 receives it. Sent with an older timestamp_micros, it is stamped 72 hours back (or rejected under ENFORCE_RECOMMENDATIONS). Either way, a month-end comparison can still show a small refund gap after you build this.
What goes wrong when refunds are sent?
| What you see | Likely cause |
|---|---|
| Refund amount stays at zero | The refund event never fires, or the Measurement Protocol call is rejected |
| Refund shows but Purchase revenue doesn’t change | transaction_id doesn’t match the purchase |
| Refund amount appears under the wrong currency | currency missing or different from the purchase |
| Refund smaller than expected | Only some items sent, or shipping and tax not in their own parameters |
| Item revenue unchanged after refund | items not included in the refund event |
If purchases themselves are missing items or value, fix that first: F-301 . If the same order is counted twice, the refund can only remove one copy: F-101 .
Shopify refunds: what changes on the store side
A refund can be partial: Shopify marks the order Partially refunded until the total available to refund is reached. Shipping can be refunded separately. In Shopify’s sales report, each of those is a reversal dated when it was processed. In Google’s reference, a refund’s value is price times quantity for the items; shipping and tax have their own optional shipping and tax parameters. Google doesn’t say whether those change Refund amount, so test one order that had shipping refunded before trusting the total. Until then, compare item amounts, not the order total.
Which number should I trust?
For revenue, Shopify, as the record of what was charged and returned. GA4 purchase revenue is only comparable once refunds are sent. Until then, use Gross purchase revenue against Shopify gross sales minus discounts, which should match closely, and treat refunds as a known gap. Whether to send refunds at all is one of the six decisions in the reconciliation chapter.
If you want the refund route built and the remaining gaps named, that is a reconciliation. Email [email protected] with one closed month of GA4 purchase revenue and Refund amount next to Shopify’s net sales and sales reversals.
Common questions
Why doesn’t GA4 revenue drop when I refund an order?
GA4 only subtracts a refund when it receives a refund event carrying the order’s transaction_id. Shopify takes the refund off its own sales on the day it is processed, but it doesn’t tell GA4 unless an app, a tag or a server call sends the event. No refund event, no change in GA4.
Which GA4 metric is net of refunds?
Google defines Purchase revenue as the sum of revenue from purchases, minus any refunds given. Gross purchase revenue is the same sum without refunds taken off, and Refund amount is the refunds on their own. If no refund events arrive, Purchase revenue and Gross purchase revenue show the same figure.
Can I send a partial refund to GA4?
Google’s refund event takes the same transaction_id as the purchase, a value and currency, and optionally the items refunded. Google’s page doesn’t describe partial refunds in detail. For a part refund I send the value and the items actually refunded, then check one order in the Transactions report before trusting the rest.
Can the Measurement Protocol send refunds to GA4?
Yes. Google’s Measurement Protocol reference includes a refund event example. Events can be backdated up to 72 hours; older ones are either given a timestamp 72 hours ago or rejected, depending on validation_behavior. A refund processed days after the order is still a refund, but it isn’t dated to the sale: with no timestamp it is dated on receipt, and an older timestamp is stamped 72 hours back.
Sources
Read on 10 November 2026:
- Google Analytics developer reference, recommended events: refund (
transaction_idrequired;valueandcurrencytogether;itemsrecommended for item-level refund metrics) - Google Analytics Help, dimensions and metrics (Purchase revenue, Gross purchase revenue, Refund amount, Ecommerce purchases)
- Google Analytics Measurement Protocol, events reference (refund example,
client_id,api_secret) and sending events (72-hour backdating,validation_behavior, 48-hour guidance) - Shopify Help Center, sales reports (sales reversals, dated when processed, net sales formula) and refunding orders (partial refunds, shipping refunds)