Guide 75 · Reports · GA4 + Tag Manager
Read the Landing page report: where each session started, and what the first page did
The Landing page report shows the first page of each session. Read it to find which entry pages engage and which ones send people straight back out.
After step 5, you can name the top three landing pages by sessions, the landing page with the best engagement rate, and the one whose sessions rarely lead to a key event.
Download the report reference: the Landing page reference (JSON) (1520 bytes, MD5 02a09c3b3454128f56a060bdad56d0ba). 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 Landing page.
- The difference from Pages and screens, fixed in your head first: Pages and screens counts every view of a page; Landing page counts only sessions that started on it.
The trace
- Open the report. Sign in, click Reports, then Engagement, then Landing page. The table lists one row per landing page, ranked by sessions.
- Read sessions beside engagement rate. Sessions is the number of visits that started on the page. Engagement rate is the share of those sessions that lasted 10 seconds or longer, or had a key event, or two or more page views. A landing page with many sessions and a low engagement rate is an entry that does not hold people.
- Read key events beside sessions. A landing page's job is to start a session that ends in something — a purchase, a sign-up, a lead. Divide key events by sessions for the landing page's key event rate; the worked example below does that division for three pages.
- Search for one landing page before you re-sort. Use the search bar above the table to find a single page. The search filters in place; re-sorting first loses the row.
- Check the lag before you judge a new landing page. Standard reports can take 24 to 48 hours to process data. A landing page published yesterday is barely in this report; give it two days before you call it a failure.
Dead ends
DEAD END — READING LANDING PAGE AS PAGES AND SCREENS. A page can rank first in Pages and screens because it is linked everywhere, and rank nowhere in Landing page because nobody enters through it. The two reports answer different questions.
DEAD END — JUDGING A LANDING PAGE ON SESSIONS ALONE. Sessions say the entry was found. Engagement rate and key event rate say the entry worked. A high-session, low-engagement landing page is a leak at the front door.
DEAD END — CALLING A NEW LANDING PAGE A FAILURE ON DAY ONE. The processing lag means a new page's first day is incomplete here. Judge it after two days of data, not after one morning.
End state
The Landing page report answers where sessions begin and whether the beginning works. The worked example below recomputes engagement and key event rates for three landing pages, so the entry ranking can be read beside the outcome ranking.
Worked example — stated inputs, recomputed results. The landing 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 |
|---|---|---|---|---|---|---|
| / | 1,980 | 990 | 50.0% | 79 | 4.0% | $610.50 |
| /pricing | 920 | 604 | 65.7% | 88 | 9.6% | $940.00 |
| /guides/start | 715 | 512 | 71.6% | 121 | 16.9% | $1,280.25 |
| Total | 3,615 | 2,106 | 58.3% | 288 | 8.0% | $2,830.75 |
Revenue per session is $2,830.75 ÷ 3,615 sessions = $0.78. Engagement rate is 2,106 ÷ 3,615 = 58.3%.
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 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.