GA4 Revenue Reports: The Complete Guide for Ecommerce

GA4 will happily show you a revenue total. The number is easy to find and almost useless on its own, because a total cannot tell you which products, devices or channels are carrying the store and which are quietly dragging it down. The value in GA4 revenue reporting is not the headline figure. It is the ability to break revenue apart and see where it is won, where it leaks, and where it could grow.

This guide covers the GA4 revenue reports and metrics that actually matter for ecommerce, how to build a custom revenue exploration that answers a real question, and the one thing every team eventually trips over: why GA4's revenue never quite matches the number in your store's backend, and which one to trust for what.

What GA4 revenue reporting is

GA4 revenue reporting is the set of built-in Monetization reports and custom explorations that show the revenue your store generates, broken down by product, channel, device and other dimensions.

It sits on top of your ecommerce tracking. The purchase events you send, with their value, currency and items, are what these reports read. So revenue reporting is only as good as the tracking beneath it, which is why this is the last step of the analytics journey, after GA4 ecommerce tracking and GA4 funnels. Track the journey, find the leaks in the funnel, then read revenue to prioritize and prove.

The GA4 revenue metrics you need to know

Most GA4 revenue confusion comes from treating different metrics as if they were the same. Get these straight and the reports become readable.

The one that trips people up most is purchase revenue versus total revenue. For a typical store, purchase revenue is the ecommerce number you want. Total revenue is broader and can mislead if you compare it to your store's sales.

The revenue reports you actually use

Monetization overview and ecommerce purchases

GA4's Monetization section gives you the overview, total purchase revenue, and the ecommerce purchases report, which breaks revenue down by item. The ecommerce purchases report is the workhorse: it shows which products are viewed, added to cart and purchased, and the revenue each generates. A product with high views and low item revenue is a product page problem, addressed in product page optimization.

Revenue by channel and source

Link your acquisition and monetization data by looking at revenue split by the default channel grouping or by source and medium. This tells you which channels bring revenue, not just traffic. It is also where attribution matters, because the model decides which channel gets credit for each sale. Read it alongside our guide to revenue attribution, and remember that attributed revenue is a modelled view, not a ledger.

Custom revenue explorations

The built-in reports answer common questions. For anything specific, build an exploration.

1. Open Explore and start a free-form exploration.
2. Add dimensions for the cut you care about: device category, session default channel group, landing page, or item.
3. Add purchase revenue as the metric.
4. Apply a segment if you want to isolate a group, such as new versus returning customers.

The most valuable single cut is revenue by device. It routinely reveals that mobile, where most traffic is, converts to far less revenue per session than desktop, which is a large and common leak hiding inside a healthy-looking total.

Reading revenue reports to find leaks

A breakdown is only useful if you read it as a hunt for leaks, not a status update.

• Revenue by device. If mobile revenue per session lags desktop badly, you have a mobile experience leak. Given mobile traffic share, it is often the biggest one.
• Revenue by product. High views and low revenue on a product points at its page. High revenue concentration in a few products tells you where merchandising and stock reliability matter most.
• Revenue by channel, net of cost. A channel with strong attributed revenue can still lose money once ad spend, discounts and returns are counted. Turn revenue into profit with the ROAS calculator and the ecommerce profit calculator.
• Revenue by new versus returning. Weak new-customer revenue is an acquisition or first-impression problem; weak returning revenue is a retention and lifetime-value one, which the customer lifetime value calculator helps size.

Why GA4 revenue does not match your backend

Every team eventually notices that GA4's revenue does not equal the number in Shopify, their payment processor, or their accounting. This is normal, expected, and worth understanding, because the instinct to declare GA4 "broken" is usually wrong.

The main reasons GA4 reads lower or simply different:

• Consent and tracking gaps. Shoppers who decline tracking, or whose analytics is blocked, complete real purchases GA4 never records. Your backend sees every order; GA4 sees consented, observed ones.
• Attribution and timing. GA4 attributes and timestamps revenue by its own logic, which can place a sale in a different period or channel than your backend does.
• Tax and shipping. Whether these are in GA4's revenue depends on what you put in the value parameter, which may differ from how your backend reports order totals.
• Refunds and cancellations. Unless you send refund events, GA4 will not net them out the way your backend does.
• Currency and multi-store setups. Conversion and configuration differences can shift totals.

The limits of GA4 revenue data

Beyond the backend mismatch, keep these in mind so you do not over-trust a figure.

• Modelled and consented. GA4 reports observed, consented activity and models part of the gap, so its revenue is directional, not a census.
• Thresholding. On small segments GA4 may withhold data to protect privacy, which can make granular revenue cuts unreliable.
• Attribution is a model. Revenue by channel reflects the attribution model, not proven causation. Validate big channel decisions with incrementality, covered in revenue attribution.

None of this makes GA4 revenue useless. It makes it a powerful tool for finding where revenue is won and lost, as long as you read it as behavioural evidence rather than as your ledger.

Common GA4 revenue reporting mistakes

Even careful teams repeat these. Treat the list as a pre-flight check.

• Confusing purchase revenue and total revenue. They are different metrics; compare the right one to your sales.
• Expecting GA4 to match the backend. It will not, by design. Use each for what it is good at.
• Reading only the total. The total is a scoreboard; the breakdowns are where decisions live.
• Ignoring the device cut. The mobile revenue leak hides inside a healthy blended number.
• Treating attributed channel revenue as profit. Net out ad spend, discounts and returns before you judge a channel.
• Trusting granular, thresholded segments. Very small cuts can be noisy or withheld.

The GA4 revenue reporting checklist

Use this to audit any store's GA4 revenue analysis in a single pass.

• Purchase revenue, not total revenue, is used as the ecommerce sales figure.
• Revenue is read by device, product and channel, not just as a total.
• The GA4-to-backend gap is known, stable, and monitored for sudden changes.
• The backend is treated as the financial source of truth; GA4 as behavioural evidence.
• Channel revenue is judged net of ad spend, discounts and returns.
• Under-earning segments are priced as leaks and ranked against each other.
• The largest priced revenue leak is fixed first, and the report is re-checked after.

Frequently asked questions

What are GA4 revenue reports?

They are the built-in Monetization reports and custom explorations in GA4 that show the revenue your store generates, broken down by product, channel, device and other dimensions. They read from the purchase events your ecommerce tracking sends.

What is the difference between purchase revenue and total revenue in GA4?

Purchase revenue is revenue from purchase events, which is your ecommerce sales figure. Total revenue adds any subscription and advertising revenue, so it is broader than store sales. For most ecommerce analysis, purchase revenue is the number you want.

Why does GA4 revenue not match Shopify or my backend?

Because they measure differently. GA4 records consented, observed purchases and applies its own attribution and timing, while your backend records every order exactly. Consent gaps, ad blockers, tax and shipping handling, refunds and currency all contribute. Expect a stable gap, and treat the backend as the financial source of truth.

What is average purchase revenue in GA4?

Average purchase revenue is purchase revenue divided by the number of purchasers, which is close to average order value. It can differ from your true average order value if refunds, tax handling or tracking gaps affect the underlying revenue figure.

How do I see revenue by channel in GA4?

Use the default channel grouping or source and medium as a dimension against purchase revenue, in a Monetization report or a custom exploration. Remember that channel revenue depends on the attribution model, so read it as a modelled view and validate big decisions with incrementality testing.

How do I build a custom revenue report in GA4?

Open Explore, start a free-form exploration, add the dimensions you care about such as device or channel, add purchase revenue as the metric, and apply a segment if needed. Revenue by device is usually the most revealing single cut for finding leaks.

Which revenue number should I trust, GA4 or my backend?

Your backend for anything financial: accounting, forecasting and exact figures. GA4 for behavioural and directional questions: which device, product or channel wins, and where the funnel leaks. They serve different purposes and are not meant to match exactly.

Does GA4 include tax and shipping in revenue?

Only if you include them in the value parameter of your ecommerce events. GA4 reports whatever value you send, so whether tax and shipping are in your revenue is an implementation decision. Be consistent, and document it so comparisons stay meaningful.

How do GA4 revenue reports help find revenue leaks?

By letting you break revenue down and spot segments that under-earn relative to their traffic: a weak mobile experience, a high-view low-revenue product, or an unprofitable channel. Each gap is a priced leak. That breakdown is the input the Revenue Intelligence framework turns into a ranked list of fixes.

What is a revenue leak?

A revenue leak is a specific, fixable point where revenue is lost, whether a shopper drops out or a segment under-earns. GA4 revenue reports help you locate and size them. See our definition of a revenue leak for the full concept.

Conclusion and next steps

GA4 revenue reporting earns its keep when you stop reading the total and start reading the breakdown. The total tells you the score; the cut by device, product and channel tells you where the score is being made and lost. Get your metrics straight, accept that GA4 and your backend measure different things, and read revenue as a hunt for the segments that under-earn.

Your next three moves:

1. Break your revenue down by device, product and channel, and find the segment that under-earns its traffic.
2. Price the gap with the revenue loss calculator, so you fix by impact rather than by which report you opened last.
3. Turn the report into action with the Revenue Intelligence framework, or run a free revenue audit that breaks down and prices your revenue leaks for you.

With correct tracking, a clear funnel, and revenue read by dimension, GA4 stops being a scoreboard and becomes what it should be: a map to your next recovered dollar.