Unique pageviews vs pageviews
Unique pageviews count how many sessions included at least one view of a given page, collapsing repeat views of the same page within one session into a single count. It was a Universal Analytics metric; GA4 does not report it and uses 'Views' (closer to raw pageviews) instead. Knowing the difference avoids comparing a de-duplicated UA number to a non-de-duplicated GA4 one.
What this means
A pageview counts every load of a page. A unique pageview counts a page only once per session no matter how many times it was loaded in that session. So if a visitor reloads the same article three times in one visit, that is three pageviews but one unique pageview.
Why GA4 dropped it
Unique pageviews was a Universal Analytics concept. GA4's data model is event-based and reports 'Views' (the count of page_view and screen_view events), without a built-in session-level de-duplication metric of the same name. Migrating dashboards that relied on unique pageviews therefore requires rebuilding the de-duplication logic or accepting that GA4 Views behaves like total pageviews.
- Pageview: every load
- Unique pageview: once per session per page (Universal Analytics)
- GA4 reports 'Views', not unique pageviews
How it appears in analytics and logs
Unique pageviews tell you reach within sessions, not total loads. A gap between pageviews and unique pageviews signals repeat views of the same page inside single sessions.
Diagnostic use case
Use unique pageviews to gauge how many sessions touched a page at least once, and avoid comparing it to GA4 'Views', which is not de-duplicated the same way.
What WebmasterID can help detect
WebmasterID stores raw page_view events, so you can derive both total and session-deduplicated page counts first-party without third-party cookies.
Common mistakes
- Comparing UA unique pageviews to GA4 Views as if identical.
- Assuming GA4 de-duplicates page views per session by default.
- Reading unique pageviews as unique people.
Privacy and accuracy notes
De-duplication happens within a session grouping, using event counts rather than personal identity. No personal data is required.
Related pages
- Pageviews: what the metric counts
A pageview is recorded when a page is loaded (or a virtual page is rendered in a single-page app). It is the oldest web-analytics metric and the easiest to misread: pageviews count loads, not people, and modern apps and prefetching can inflate or hide them. This page defines the metric and its caveats.
- Users: counting people vs identifiers
The users metric estimates how many distinct visitors a site had, but it actually counts distinct identifiers, not individuals. GA4 reports several user metrics — Total users, Active users (its headline), and New users — that mean different things. Because a person on three devices is three identifiers, and a cleared cookie is a new one, the count diverges from the real number of people.
- Sessions: what a session is and when it resets
A session is a group of interactions from one visitor within a bounded time window. It starts on the first event and ends after a period of inactivity (commonly 30 minutes, configurable). The reset rules differ by tool — and historically Universal Analytics also restarted sessions at midnight and on a new campaign — so the same traffic produces different session counts in different products.
- Event Explorer
Derive views and unique views from raw events.
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.