Skip to content

Guide 46 · Ecommerce · GA4 + Tag Manager

Read the Monetization overview: total revenue, purchase revenue, and what the cards actually sum

Checked 11 November 2026 · Verification: reference file checked in Python (figures recomputed from the worked example) · Steps traced to Google's developer docs and Analytics Help, opened 11 November 2026 · 5-minute read

The Monetization overview is the summary cards for revenue: total revenue, purchase revenue, purchasers, and average purchase revenue. Read the cards, then click through to the detail.

Expected signal

After the events flow, Reports, then Life cycle, then Monetization, then Monetization overview shows the summary cards. In the worked day below, purchase revenue reads 102.08 and total revenue reads 60.06 after the refund.

Download the reference: the monetization-overview-report reference (JSON) (382 bytes, MD5 1f40ad08f963bb30972ade61183465d0). It holds the event parameters, the worked example, and the recomputed figures.

What you need

  • Ecommerce events flowing into the property. The overview has nothing to summarize until purchase events arrive with value, currency, and items. The gtag purchase guide covers the event itself.
  • Editor or Administrator access if the report is missing from the menu. The Monetization overview appears on the left only in the Life cycle collection, and an editor or administrator can add it to the navigation from the report library.
  • One worked day to read against. Two orders — the single-item order at 30.03 and the two-item order at 72.05 — and one partial refund of 42.02.

The trace

  1. Open the report in the Life cycle collection. In Analytics, click Reports on the left, then Life cycle, then Monetization, then Monetization overview. The overview is a pre-made overview report: it summarizes the revenue topic with summary cards, each showing information from another report. The Life cycle collection lists Monetization overview first among the Monetization reports.
  2. Read total revenue as revenue minus refunds. Total revenue shows the total amount of revenue from ecommerce purchases, in-app purchases, subscriptions, and advertisements, minus any refunds. In the worked day, the two orders total 30.03 + 72.05 = 102.08 in purchase revenue, and the partial refund of 42.02 brings total revenue to 102.08 − 42.02 = 60.06. Total revenue is the net figure; purchase revenue is the gross figure.
  3. Read purchase revenue as the ecommerce figure. Purchase revenue is the revenue from ecommerce and in-app purchases. In the worked day it reads 102.08, because both orders are ecommerce purchases. A refund does not change purchase revenue; it changes total revenue.
  4. Read the purchaser cards beside the money cards. Total purchasers counts the users who made a purchase — 2 in the worked day, one per order. Average purchase revenue per active user divides the purchase revenue by the active users in the period, so it moves with traffic as well as with orders.
  5. Click a card to reach the detail report behind it. Each summary card displays information found in another report. The purchase revenue card leads to the detail behind the number — the Ecommerce purchases report for item-level revenue, the Transaction ID report for order-level revenue. The overview answers whether revenue moved; the detail reports answer why.

Dead ends

DEAD END — TOTAL REVENUE READ AS GROSS. Total revenue subtracts refunds. A day with 102.08 in purchase revenue and a 42.02 refund shows total revenue 60.06. Reading total revenue as the day's sales overstates the day by the refund, every time a refund happens.

DEAD END — THE EMPTY OVERVIEW WITH EVENTS FLOWING. The overview stays empty if the purchase events carry no value or no currency. An event with a value and no currency cannot be placed in any currency, so the revenue metrics stay at zero while the event count rises. The fault is in the event, not in the report.

DEAD END — EXPECTING SAME-DAY NUMBERS. Standard reports can take about 24 hours to process data. An order placed today appears in the overview tomorrow. The same-day check belongs in Realtime or DebugView, not in the Monetization overview.

End state

The Monetization overview reads as four cards on the worked day: purchase revenue 102.08, refund 42.02, total revenue 60.06, and 2 purchasers. The cards summarize the detail reports, and each card leads to the report behind it. No ecommerce events means no cards, and a refund moves total revenue without moving purchase revenue.

Sources

Checked 11 November 2026. The report structure above is the one in Analytics Help, opened 11 November 2026. The worked day's figures were recomputed in Python: 30.03 + 72.05 = 102.08, and 102.08 − 42.02 = 60.06. The revenue definitions follow Google's own report descriptions. No step was run inside a live Analytics property, because that needs a Google sign-in and this site does not sign in as anyone.