Guide · Revenue attribution

GA4 Revenue Attribution: Why Your Stripe Sales Go Missing

GA4 often shows less revenue than Stripe or Lemon Squeezy. Here is why purchases go missing, how to patch it, and when webhook attribution is simpler.

· 3 min read

Traffic lines leading to a revenue target, with a payment card beside it

You open GA4, look at revenue by source, and the total is 30% lower than your payment provider says. Nothing is broken in the obvious sense. GA4 can only report the purchases it sees, and for many online businesses it doesn't see them all.

Why GA4 misses purchases

GA4 learns about a purchase when a purchase event fires in the browser or arrives through the Measurement Protocol. Sales go missing when that event never happens:

  • The payment happens on another domain. Stripe Checkout, Lemon Squeezy and Paddle host the payment page. Unless the buyer returns to your thank-you page and it fires the event, GA4 never hears about it.
  • The buyer closes the tab. Many people never wait for the redirect back.
  • Consent banners and ad blockers. If the visitor declined analytics cookies, or a blocker stopped the GA script, the purchase event is lost too.
  • Renewals. A subscription renewal happens on the provider's servers. No browser, no event.
  • Refunds. GA4 needs a separate refund event, which few setups send.

How to patch it inside GA4

If you want to stay on GA4, the fix is to send purchases from your server:

  1. Store GA4's client_id (from the _ga cookie) with the order when checkout starts.
  2. When your provider's webhook confirms the payment, call the Measurement Protocol with that client_id, the transaction id and the value.
  3. Send refunds the same way.
  4. Mark the server event so it isn't counted twice if the thank-you page also fires.

This works, but it's real engineering: webhook handling, retries, deduplication, and keeping it working as providers change their events.

The webhook-first alternative

Revenue attribution tools start from the payment instead of the page. Every payment the provider sends is recorded, then matched to a visitor:

  1. 1Visitor arrivesSource and visitor id are recorded
  2. 2CheckoutThe visitor id travels in the payment's metadata
  3. 3WebhookThe provider sends every payment, renewal and refund
  4. 4MatchThe payment joins the visitor, so revenue joins the source
Webhook-first attribution

Because the record starts at the provider, renewals and refunds are counted even when no browser is involved. That is how DataFair works. How to track revenue by traffic source explains each step.

GA4 vs webhook attribution

GA4 purchase eventsWebhook attribution (DataFair)
Records payments on the provider's domainOnly if the buyer returns or you send server eventsYes, from the webhook
Subscription renewalsServer events you buildYes
RefundsSeparate refund eventsYes
SetupTag configuration, often a developerScript plus one webhook per provider
PriceFreePaid, from $5.99 a month at launch

GA4 is free and powerful for traffic and ads analysis. If revenue is the number you care about most, a webhook-based tool is less work.

You don't have to choose

Some teams keep GA4 for Google Ads reporting and add DataFair for revenue. Others move fully and bring their GA4 history with them, so the charts don't start from zero.

Related guide: A Google Analytics alternative built around revenue.

Questions

Why is my GA4 revenue lower than Stripe?
Usually because purchases happen on Stripe's domain and the purchase event only fires when the buyer returns to your site. Renewals and refunds also need server events.
Does GA4 attribute subscription renewals?
Not on its own. You need to send renewal events from your server with the Measurement Protocol.
Which attribution model does GA4 use for revenue?
GA4 defaults to data-driven attribution for conversions, and also offers last click. Reports such as traffic acquisition use the session's source. DataFair credits the last visit that came from somewhere.

Related