Landing page dimension
The landing page dimension records the first page a visitor saw in a session — the entry point. GA4 derives it from the page_path (and optional query string) of the session's first page_view event. It is a session-scoped dimension, so pairing it with hit-scoped metrics, or ignoring how query parameters split the same page, are the usual ways it misleads.
What this means
The landing page is the entry point of a session: the page_path of the first page_view GA4 attributes to that session. It answers 'where did this visit start?' and is the natural unit for judging acquisition pages, ad destinations, and SEO entry points.
Because it is session-scoped, it pairs cleanly with session and user metrics (sessions, engaged sessions) but mixes awkwardly with hit-scoped metrics that count every pageview.
Where it breaks
If query strings are kept, the same page arrives as many distinct landing pages — /post and /post?utm_source=x are different rows. Redirects can also shift the recorded entry point to the redirect target. In GA4 a session with no page_view (an app or event-only session) may show '(not set)' for landing page.
- Session-scoped: first page_view of the session
- Query strings fragment one page into many rows
- Redirects can change the recorded entry point
How it appears in analytics and logs
A landing page value is the first page_view of a session. Many near-duplicate landing pages usually means query strings (utm_*, fbclid) are being kept in the path, fragmenting one page into many rows.
Diagnostic use case
Use landing page to evaluate entry points and acquisition pages, while keeping its session scope in mind and deciding whether query strings belong in the value.
What WebmasterID can help detect
WebmasterID captures the session's first page first-party and can normalise query strings, so a single landing page is one row rather than a long tail of tagged variants.
Common mistakes
- Leaving utm_*/fbclid in the path so one page splits into many.
- Pairing landing page with hit-scoped pageview totals.
- Reading '(not set)' as an error rather than a page_view-less session.
Privacy and accuracy notes
Landing page is a URL path, not a person. WebmasterID records it first-party and can strip identifying query parameters before the path is stored.
Related pages
- Page path dimension
The page path dimension is the path portion of a viewed URL — /blog/post — excluding the hostname and, by configuration, the query string. GA4 derives it from the page_location of each page_view. It is hit-scoped, so it counts every view of a page, and the most common pitfall is query strings (utm_*, session IDs) fragmenting one logical page into many distinct paths.
- Page title dimension
The page title dimension records the document title (the <title> text) of each viewed page. GA4 captures it from the page_view event. It is convenient for human-readable reports, but titles are editable and dynamic: the same URL can carry different titles over time or across A/B tests, splitting one page into several title rows and making path a more stable key.
- UTM parameters explained: the five tags and how to use them
UTM parameters are query-string tags you add to a link so analytics can attribute the visit to a campaign even when the referrer is missing. This page explains the five tags, a consistent naming convention, and the hard rule that UTM values are public — so they must never contain personal data or secrets.
- Event Explorer
Inspect the first page_view that defines a session entry.
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.