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.
What this means
Page path is everything after the hostname in a URL: /pricing, /blog/2026/post. GA4 extracts it from the page_location reported on each page_view. Unlike landing page (session-scoped, the entry point), page path is hit-scoped — it counts every view of that path within any session.
Where it breaks
Whether the query string is part of the path depends on configuration. If kept, /post?utm_source=x and /post?ref=y become separate rows for the same content. Fragment identifiers (#section) and trailing-slash inconsistencies can also split pages. And query strings sometimes carry identifiers, so normalising them serves both clean reporting and privacy.
- Hit-scoped: counts every page_view
- Query strings can fragment one page
- Trailing slashes and fragments can split rows
How it appears in analytics and logs
A page path value is the URL path of a page_view. A bloated path list usually means tracking parameters are kept in the path, splitting one page across many rows.
Diagnostic use case
Use page path for per-page content reporting, normalising query strings so one logical page is one row rather than a long tail of parameter variants.
What WebmasterID can help detect
WebmasterID records page paths first-party and can normalise query strings at ingest, so per-page reporting stays clean and free of PII-bearing parameters.
Common mistakes
- Keeping tracking parameters in the path.
- Confusing hit-scoped page path with session-scoped landing page.
- Letting trailing-slash variants create duplicate rows.
Privacy and accuracy notes
Page path is a URL, not a person — but query strings can carry identifiers. WebmasterID can strip identifying parameters before the path is stored.
Related pages
- 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.
- 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.
- Hostname dimension
The hostname dimension records the domain that served each page_view — example.com, staging.example.com, or a domain you do not own. It comes from the host portion of the page_location URL. It is one of the most useful data-quality filters: unexpected hostnames reveal staging traffic, mis-deployed tags, or hits faked by referrer/measurement spam against your property.
- Event Explorer
Inspect page_location and the derived page path.
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.