Pageview
A pageview is a single instance of a page loading or reloading in a browser. Each time a visitor opens a page, analytics records one pageview. Google Analytics 4 logs it as a page_view event and reports it under the broader “Views” metric.
Why Pageviews Matter
Pageviews measure content volume. They show which pages get the most traffic, how often people view them, and where attention concentrates across a site.
That makes pageviews the base metric for content and publisher reporting. Ad impressions, most-read articles, and pages-per-visit all derive from pageview counts. The first pageview of a visit is also the landing page, which is where Google Analytics 4 assigns the source and medium from your UTM tags. If you tag campaign links, linkutm’s analytics dashboard shows click data next to the pageviews GA4 records.
Pageviews are a volume metric, not a quality one. High pageviews with low engagement can signal confusing navigation rather than strong content.
How GA4 Counts a Pageview
GA4 fires a page_view event every time a page loads, including reloads. Open a page, refresh it twice, and GA4 records three pageviews. The total “Views” count equals the number of page_view events.
GA4 combines two event types under “Views”:
page_viewfor websitesscreen_viewfor mobile apps
Enhanced Measurement fires the page_view event automatically on most sites, so no manual tagging is needed. Single-page applications are the exception. Their content changes without a full reload, so they often need extra configuration to log a pageview on each route change.
Pageviews vs Sessions
A pageview and a session measure different layers of the same visit. A session is one visit. A pageview is one page load inside that visit.
One session usually contains several pageviews. A visitor who lands on your homepage, opens two product pages, and reads a blog post generates one session and four pageviews. Dividing total pageviews by sessions gives views per session, a simple depth metric.
The hierarchy runs three levels deep:
- User: one unique visitor
- Session: one visit by that user
- Pageview: one page load inside that session
Counting pageviews as visitors overstates audience size. A single person refreshing a page ten times is one user, one session, and ten pageviews.
Pageviews vs Unique Pageviews
A unique pageview counts a page once per session, no matter how many times it loads. Universal Analytics reported this metric to strip out repeat views of the same page within a single visit.
GA4 retired unique pageviews. The closest equivalents are “Views” for raw loads and “Sessions” for visit-level counts. To approximate the old number, GA4 users now look at views alongside the sessions that contained them.
Frequently Asked Questions
What is a pageview in Google Analytics?
A pageview is one instance of a page loading in a browser, recorded in GA4 as a page_view event. GA4 groups these events under the “Views” metric. Every load and reload counts as a separate pageview.
What is the difference between pageviews and sessions?
A session is a single visit, while a pageview is a single page load within that visit. One session can contain many pageviews. Sessions count visits; pageviews count page loads.
Do page refreshes count as pageviews?
Yes. Each refresh fires a new page_view event, so reloading a page three times records three pageviews. This is why refresh-heavy behavior can inflate pageview totals.
What replaced pageviews in GA4?
GA4 renamed the metric to “Views” and merged web page_view and app screen_view events into one count. It also removed the “unique pageviews” metric from Universal Analytics.
To attribute every landing pageview to the right campaign, build your links with the free UTM builder at linkutm.