Pageviews / Views

A view — what Universal Analytics called a pageview — counts every time a page loads. GA4 records it through the page_view event, which fires on each load. Reload the same page three times and that's three views, even though one person saw it. GA4 renamed "pageviews" to "views" so the metric could cover both websites and apps, but the meaning is unchanged: it counts loads, not people.

Why it matters

Views are the oldest and most intuitive web metric, and they still answer a useful question: how much is a given page being looked at? For content-driven sites, the views report shows which articles pull attention and which sit untouched. It's a fine measure of reach. What it is not is a measure of audience size or quality — and confusing the two is where most trouble starts.

A concrete example

Your blog shows 5,000 views this month, up from 4,000. Encouraging. But views count repeat loads and the same person returning, so those 5,000 views might come from far fewer users. If you also check sessions and users for the same period and they didn't rise, the extra views may just be existing readers refreshing or revisiting — not new reach.

The common misreading

The big mistake is treating views as a proxy for people, or for value. High views with flat enquiries usually means reach without relevance — plenty of looking, little doing. Always read views next to sessions, users, and your key events. On its own, a rising view count tells you a page is being loaded more, nothing more than that.