Guide 57 · Reports · GA4 + Tag Manager
Read the Pages and screens report: which pages get the views, and which get the attention
Pages and screens ranks every page by views and engagement time. Read views beside average engagement time — a page can win one and lose the other.
After step 5, you can name the top three pages by views, the top page by average engagement time per session, and the page whose views do not convert.
Download the report reference: the Pages and screens reference (JSON) (1563 bytes, MD5 4b99d1a86f6fec8542e209aaf89d2cae). 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 Pages and screens.
- The primary dimension you intend to read: Page path and screen class by default. Know whether you want the path, the title, or the full path with query string before you change it.
The trace
- Open the report. Sign in, click Reports, then Engagement, then Pages and screens. The table lists one row per page path, ranked by views by default.
- Read views, users, and engagement time together. Views is the count of page loads. Users is the people behind them. Average engagement time per session is the attention measure. A page with many views, few users, and short engagement time is being reloaded or skimmed, not read.
- Search for one page before you re-sort. Use the search bar above the table to find a single page path, for example /pricing. The search filters rows in place; sorting the table first and then searching is slower and loses your place.
- Add total revenue as a secondary view when the store matters. Scroll right or add the revenue columns to see which pages sit upstream of revenue. A page with high views and no revenue is a content question; a page with high revenue and low views is a traffic question. The report does not say which — the two columns together do.
- Check the 24 to 48 hour lag before you chase a same-day change. Standard reports can take 24 to 48 hours to process data. A page published this morning will not show its true numbers until tomorrow at the earliest. Realtime is the same-day check; this report is not.
Dead ends
DEAD END — RANKING PAGES ON VIEWS ALONE. Views reward the pages the site links to most, not the pages that hold people. Engagement time and key events decide whether a viewed page did any work.
DEAD END — SEARCHING BY PAGE TITLE WHEN THE DIMENSION IS PATH. The search matches the dimension shown. If the table shows paths, search for a path fragment, not a title.
DEAD END — CHASING A SAME-DAY DIP IN THIS REPORT. Standard reports lag 24 to 48 hours. A dip that appeared an hour after a publish is not in this report yet; it is in Realtime, or it is not measured yet.
End state
Pages and screens answers which pages earn attention, not just loads. The worked example below recomputes the engagement and key event rates for three pages so the view ranking can be set against the attention ranking.
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 | 1,840 | 1,196 | 65.0% | 176 | 9.6% | $1,880.00 |
| /features | 1,320 | 660 | 50.0% | 52 | 3.9% | $310.75 |
| /about | 410 | 328 | 80.0% | 12 | 2.9% | $0.00 |
| Total | 3,570 | 2,184 | 61.2% | 240 | 6.7% | $2,190.75 |
Revenue per session is $2,190.75 ÷ 3,570 sessions = $0.61. Engagement rate is 2,184 ÷ 3,570 = 61.2%.
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 — the search bar above the table finds one row; report filters can isolate one page
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.