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.
What this means
The page title is the text in the document's <title> element at the moment the page_view fired. GA4 stores it as a dimension so reports can show human-readable names instead of bare paths.
It is useful for skimming a report, but it is a label, not an identity — the path is what stably identifies a page.
Why it splits
Titles are routinely edited, localised, templated with dynamic values, or varied across A/B tests. Each variation is a distinct title row even though the URL never changed, so one page can appear several times. Single-page apps that update document.title on route changes must set the title before the page_view fires, or the wrong title is recorded.
- Captured from document.title on page_view
- Edits/localisation/tests split one URL into many titles
- SPAs must set the title before firing page_view
How it appears in analytics and logs
A page title value is the document title sent with a page_view. Multiple titles for one URL usually mean the title changed over time, was localised, or varied by test — not that there are multiple pages.
Diagnostic use case
Use page title for readable reporting, but key durable analysis on page path, since titles change with edits, localisation, and tests.
What WebmasterID can help detect
WebmasterID records the page title alongside the path first-party, so you get readable labels while keeping the path as the stable analytical key.
Common mistakes
- Keying durable analysis on title instead of path.
- Firing page_view before the SPA updates document.title.
- Treating title variants as separate pages.
Privacy and accuracy notes
Page title describes the page, not the visitor — but dynamic titles can echo query content, so they should be reviewed for accidental PII.
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.
- Content grouping
Content grouping is a custom dimension that classifies pages into editorial groups — Blog, Product, Docs — so you can report by content type instead of one URL at a time. In GA4 it is populated by sending a content_group parameter on the page_view event. Because it is event-scoped and only as good as the values you send, untagged pages fall into '(not set)' and inconsistent naming fragments the report.
- The page_view event: the base of web analytics
page_view is the event fired when a page loads. It is the base of almost every web-analytics model: sessions, pageviews, and most reports build on it. In classic sites the tracker fires it automatically on load; in single-page apps you fire it on each route change. Its properties (path, title, referrer) drive most downstream reports.
- Events docs
How page_view carries title and location.
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.