What Is a Pageview? (And What Counts as One)
The pageview defined precisely: full loads, SPA route changes, reloads, and the edge cases that make tools report different numbers.
A pageview is one load (or virtual load) of one page by one visitor. It is analytics' atomic unit — and the reason two tools never report the same number is that 'load' has edge cases, and every tool resolves them slightly differently.
What counts
- Full page loads: the classic case — HTML document requested and rendered.
- SPA route changes: in React, Vue, or Next.js apps, client-side navigations are virtual pageviews — counted only if the tracker instruments the History API. This is the biggest source of cross-tool disagreement.
- Reloads: each refresh is a new pageview (it is a new load).
What does not (or should not)
- Iframe loads inside a page, prefetches and prerenders the visitor never saw (modern trackers wait for actual visibility), bot traffic (filtered with varying aggressiveness), and HTMX/Turbo fragment swaps that do not change the URL.
Pageviews vs visits vs visitors
One visitor makes one or more sessions; each session contains one or more pageviews. Pages-per-session (pageviews ÷ sessions) is the classic depth metric — useful directionally, gameable by pagination.
The useful upgrade
A pageview with context beats ten bare counts: Clycyo records each pageview with its load time, referrer, and UTM context on the visitor's timeline — so the unit of analysis can be the journey, not the hit. Raw counts are for trends; joined records are for decisions.