How does a pageview differ from a unique pageview?

Pageviews count every load, even if one person refreshes the same page ten times. Unique pageviews compress those ten into one within a session, so the figure is closer to how many sessions saw the page than to consumption volume.

Why do single-page applications report an unrealistically low pageview count?

After the initial load the browser never loads a new document, so the tracking code does not run again. The fix is for the application to send a pageview on each route change; without it a multi-page session records a single view.

Pageview

Beginner

Updated Jul 11, 2026 Shahin editorial 2 min read

PronunciationEN/ˈpeɪdʒvjuː/

A pageview is one recorded instance of a page being loaded and reported by the tracking code, counted again on every reload.

The tracking code runs on page load, so returning with the back button, refreshing, or opening the page in a second tab each add another pageview from the same person. Single-page applications change the address without a full load, and those transitions are not counted until the application sends them explicitly as virtual pageviews. The naming has also shifted between tool generations: Universal Analytics called it pageviews, while GA4 replaced it with the page_view event and a views metric that also counts mobile app screen views, so a views figure from a combined web and app property is not comparable with an older pageviews figure. The persistent error is reading pageviews as audience size, when the metric counts page loads and says nothing about how many people produced them.

How it is calculated

Pageviews = total count of page view events recorded in the selected time range

Every load counts as one and repeat views by the same person are not merged; the measure that counts each page once per session is unique pageviews. The unit is views, and unlike unique users this number is additive across time ranges.

FAQ

Sources:GA4 — Automatically collected events GA4 — Analytics dimensions and metrics