Guide 56 · Reports · GA4 + Tag Manager
Read the Engagement overview: events, pages, and time, before you open any detail report
The Engagement overview is a card summary of events, pages, and conversions. Use it to pick which detail report deserves the next hour.
After step 4, you can name the top event by count, the top page by views, and whether engagement time moved with them — and which detail report to open for each.
Download the report reference: the Engagement overview reference (JSON) (1551 bytes, MD5 580dedb23b25fc4f958f589404af9621). 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 report path: Reports, then Engagement, then Engagement overview.
- A fixed date range. Every card on the overview follows the range at the top right.
The trace
- Open the overview and read the cards in order. Sign in, click Reports, then Engagement, then Engagement overview. The cards sum up events, pages and screens, and conversions. Read each card's headline and its change against the previous period before clicking anything.
- Open the Events detail report from the top event. Click through to the Events report. The overview tells you which event fired most; the detail report tells you how many users fired it and how often per user. An event with a high count and few users is one user firing it repeatedly.
- Open Pages and screens from the top page. The overview's page card names the most-viewed page. The detail report adds average engagement time per session for that page, which is the number that says whether the views were attention or bounce-through.
- Check the conversion card against the Conversions detail report. The overview's conversion card is a sum of key events. Open Reports, then Engagement, then Conversions, and read the same total by event name. If the two disagree, the date ranges differ — set them equal and read again.
Dead ends
DEAD END — READING EVENT COUNT AS USER COUNT. Event count is the number of times the event fired. Users is the number of people who fired it. A count of 12,000 with 400 users is a different fact from 12,000 users.
DEAD END — READING VIEWS AS ATTENTION. A page can lead on views and trail on average engagement time. Views say it was opened; engagement time says it was read.
DEAD END — COMPARING THE OVERVIEW WITH A DETAIL REPORT ON DIFFERENT DATES. The overview and the detail report each carry their own date range. A mismatch is a date error, not a data error.
End state
The overview is a triage page: it tells you where to look next. The worked example below recomputes engagement and key event rates for three pages, to show what the page card's headline hides.
Worked example — stated inputs, recomputed results. The pages 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 |
|---|---|---|---|---|---|---|
| /pricing | 920 | 604 | 65.7% | 88 | 9.6% | $940.00 |
| / | 2,410 | 1,205 | 50.0% | 96 | 4.0% | $610.50 |
| /guides/start | 715 | 512 | 71.6% | 121 | 16.9% | $1,280.25 |
| Total | 4,045 | 2,321 | 57.4% | 305 | 7.5% | $2,830.75 |
Revenue per session is $2,830.75 ÷ 4,045 sessions = $0.70. Engagement rate is 2,321 ÷ 4,045 = 57.4%.
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] Traffic acquisition report — detail reports group data by dimensions such as channel and page; the search bar above the table finds one row
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.