Guide 53 · Reports · GA4 + Tag Manager
Read the GA4 Home report: what the first screen actually tells you, and what it hides
The Home report is a summary, not a verdict. Read its cards in order, check the date range, and confirm any surprise in the matching detail report.
After step 4, you can state, for the date range shown, total users, sessions, engagement rate, and revenue — and name the detail report each number came from.
Download the report reference: the Home report reference (JSON) (1414 bytes, MD5 955de9c20a29d141e130b19ea4c4fb4d). It holds the report or exploration definition and the worked example with the recomputed figures shown on this page.
What you need
- Viewer access or above on the property. The Home report is the first screen after sign-in; no Editor role is needed to read it.
- The date range you intend to read. The Home report defaults to the last 28 days; a number without its dates means nothing.
- One question written down before you open it — for example, did revenue change, or did traffic change. The cards answer different questions, and reading without a question turns the page into noise.
The trace
- Open Home and read the date range first. Sign in to Analytics and click Home in the left navigation. Look at the date range at the top right before any number. If it is not the range you meant to read, change it now; every card on the page follows that range.
- Read the top cards as a summary, not as the data. The Home report shows cards for users, sessions, engagement, and revenue. Each card is a summary of a detail report. Note the headline number on each card and the change beside it, and write both down with the dates.
- Open the detail report behind any card that surprises you. Click through from a card to its detail report — for example, the revenue card leads toward Monetization, the traffic card toward Acquisition. The detail report shows the rows the card summed up, and a surprise that disappears at row level was a mix change, not a real change.
- Compare with the previous period, then with the same detail report. Use the date comparison at the top of the detail report to set the previous period of the same length. A 7-day range compared with a 28-day range is not a comparison; the lengths must match.
- Check the data-quality indicator before you quote a number. A yellow or red indicator at the top of a report means sampling or thresholds are in play. A number quoted from a sampled card, or from a card with thresholds applied, is a partial number, and it should be labelled as one.
Dead ends
DEAD END — READING THE HOME REPORT AS A COMPLETE ANSWER. The Home report is a set of summary cards. It does not show which channel, page, or product moved. Any claim about a cause needs the detail report behind the card.
DEAD END — COMPARING RANGES OF DIFFERENT LENGTHS. A 28-day total next to a 7-day total looks like growth or a collapse. It is neither. Compare equal lengths only.
DEAD END — QUOTING A NUMBER UNDER A YELLOW INDICATOR. When the data-quality indicator shows sampling or thresholding, the headline number is computed from part of the data. Quote it with that caveat, or open the underlying report and check what was withheld.
End state
You can now read Home as an index: each card tells you which detail report to open next, and the date range tells you what the numbers cover. The worked example below is the arithmetic that sits behind the cards — the same division the detail reports do.
Worked example — stated inputs, recomputed results. The channels below are stated inputs for the example. Every rate in the table was recomputed from them.
| Row | Sessions | Engaged sessions | Engagement rate | Key events | Key event rate | Revenue |
|---|---|---|---|---|---|---|
| Organic Search | 1,842 | 1,107 | 60.1% | 96 | 5.2% | $1,240.50 |
| Direct | 917 | 423 | 46.1% | 41 | 4.5% | $610.25 |
| Paid Search | 634 | 389 | 61.4% | 58 | 9.1% | $905.75 |
| Total | 3,393 | 1,919 | 56.6% | 195 | 5.7% | $2,756.50 |
Revenue per session is $2,756.50 ÷ 3,393 sessions = $0.81. Engagement rate is 1,919 ÷ 3,393 = 56.6%.
Sources
- Analytics Help — Confirm that you are collecting data — many reports and explorations can take 24 to 48 hours to process data; Realtime confirms collection sooner
- Analytics Help — [GA4] About data thresholds — the data-quality indicator reports sampling and thresholding, and thresholds are system-defined
Checked 11 November 2026. The click paths above are the ones in Google's help pages, opened or read 11 November 2026 (the Explorations and detail-report pages were opened in full; the report, library, navigation and thresholds pages were read from Google's help results the same day, after the browser hit a rate limit). No step in this guide was run inside a live Analytics property, because that needs a Google sign-in and this site does not sign in as anyone. The worked-example figures on this page were recomputed in Python with decimal arithmetic, and the downloadable JSON file carries the same recomputed figures. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.