Pageview
A pageview is an event recorded when a user loads or reloads a webpage. In GA4, pageviews are tracked as the page_view event (part of automatically collected events) and each page_view contributes to a session.
§ 1 Definition
A pageview is recorded when a browser loads a page on your website. In GA4, the page_view event is an automatically collected event that fires when a page loads or the browser history state changes (for single-page applications). Each page_view event includes parameters like page_title, page_location (the full URL), and page_referrer. Unlike Universal Analytics where pageviews were one of several hit types alongside events and transactions, in GA4 the page_view is just another event. It counts toward event volume, contributes to session tracking, and can be used in segments and audiences like any other event. GA4 also tracks page_view events differently than UA tracked pageviews. In UA, a single page reload counted as two pageviews (the original and the reload). In GA4, a page_view fires on the initial load and additional page_views fire on navigation.
§ 2 How pageview is measured in GA4
The page_view event fires automatically when gtag.js or GTM's GA4 configuration tag is present on your site. Enhanced measurement is not required. The page_view carries parameters including page_title, page_location, and page_referrer. For single-page applications, GA4 uses the history_change event to detect URL changes and fire additional page_view events. This means SPAs are handled more natively in GA4 than they were in UA.
§ 3 Pageview vs event distinction
In UA, pageviews and events were separate hit types with different quotas (pageviews counted toward the 10 million monthly hit limit, events were cheaper). In GA4, there is no distinction. A page_view is an event like any other. All events count toward the same event volume. This changes the economics of tracking: in UA you might have minimized event tracking to avoid hitting hit limits; in GA4 every interaction (including pageviews) consumes the same budget.
§ 4 Tracking pageviews accurately
To get accurate pageview data, ensure your GA4 configuration tag or gtag.js fires on every page. Use GTM's 'All Pages' trigger with the GA4 event tag. For SPAs, use history change triggers or push virtual pageviews to the data layer. Watch out for duplicate pageviews caused by multiple GA4 tags firing on the same page, tag firing priority issues, and page_view events firing from both GTM and hardcoded gtag.js simultaneously.
§ 5 Note
§ 6 Common questions
- Q. Does GA4 track unique pageviews?
- A. GA4 does not report 'unique pageviews' as a metric in the same way UA did. Instead, use the 'Views' metric which counts the number of app screens and web pages users viewed, repeated views of the same screen or page are counted multiple times.
- Q. Why are my GA4 pageview numbers lower than UA?
- A. GA4 does not restart sessions at midnight and handles reloads differently. If users are active across midnight, UA counted a new session with new pageviews. GA4 counts one continuous session. This causes lower pageview totals.
- Q. Can I track PDF downloads as pageviews?
- A. You should not. Track PDF downloads as a custom event (file_download is an enhanced measurement event in GA4). Treating downloads as pageviews inflates your numbers and misrepresents user behavior.
- Pageviews are page_view events in GA4, not a separate hit type
- GA4 has no 'unique pageview' metric; use 'Views' instead
- SPA pageview tracking is handled via history_change events
- Do not compare GA4 pageview counts to UA pageview counts directly
- Avoid duplicate page_view events from multiple GA4 configurations
We set up and QA your GA4 pageview tracking to eliminate duplicates, configure SPAs correctly, and ensure your data reflects real traffic. Contact us for a tracking audit.
Get in touchA pageview is an event recorded when a user loads or reloads a webpage. In GA4, pageviews are tracked as the page_view event (part of automatically collected events) and each page_view contributes to a session.
Category: Analytics
Author: Atomic Glue Analytics Team
## Definition
A pageview is recorded when a browser loads a page on your website. In GA4, the page_view event is an automatically collected event that fires when a page loads or the browser history state changes (for single-page applications). Each page_view event includes parameters like page_title, page_location (the full URL), and page_referrer. Unlike Universal Analytics where pageviews were one of several hit types alongside events and transactions, in GA4 the page_view is just another event. It counts toward event volume, contributes to session tracking, and can be used in segments and audiences like any other event. GA4 also tracks page_view events differently than UA tracked pageviews. In UA, a single page reload counted as two pageviews (the original and the reload). In GA4, a page_view fires on the initial load and additional page_views fire on navigation.
## How pageview is measured in GA4
The page_view event fires automatically when gtag.js or GTM's GA4 configuration tag is present on your site. Enhanced measurement is not required. The page_view carries parameters including page_title, page_location, and page_referrer. For single-page applications, GA4 uses the history_change event to detect URL changes and fire additional page_view events. This means SPAs are handled more natively in GA4 than they were in UA.
## Pageview vs event distinction
In UA, pageviews and events were separate hit types with different quotas (pageviews counted toward the 10 million monthly hit limit, events were cheaper). In GA4, there is no distinction. A page_view is an event like any other. All events count toward the same event volume. This changes the economics of tracking: in UA you might have minimized event tracking to avoid hitting hit limits; in GA4 every interaction (including pageviews) consumes the same budget.
## Tracking pageviews accurately
To get accurate pageview data, ensure your GA4 configuration tag or gtag.js fires on every page. Use GTM's 'All Pages' trigger with the GA4 event tag. For SPAs, use history change triggers or push virtual pageviews to the data layer. Watch out for duplicate pageviews caused by multiple GA4 tags firing on the same page, tag firing priority issues, and page_view events firing from both GTM and hardcoded gtag.js simultaneously.
## Note
Misconception: pageviews in GA4 work exactly like pageviews in UA. They do not. GA4 counts pageviews differently (no midnight split, no reload counting as two), so pageview numbers will differ. Also: in GA4's Realtime report, 'Page Views' refers to the number of page_view events, not unique pageviews.
## Common questions
Q: Does GA4 track unique pageviews?
A: GA4 does not report 'unique pageviews' as a metric in the same way UA did. Instead, use the 'Views' metric which counts the number of app screens and web pages users viewed, repeated views of the same screen or page are counted multiple times.
Q: Why are my GA4 pageview numbers lower than UA?
A: GA4 does not restart sessions at midnight and handles reloads differently. If users are active across midnight, UA counted a new session with new pageviews. GA4 counts one continuous session. This causes lower pageview totals.
Q: Can I track PDF downloads as pageviews?
A: You should not. Track PDF downloads as a custom event (file_download is an enhanced measurement event in GA4). Treating downloads as pageviews inflates your numbers and misrepresents user behavior.
## Key takeaways
- Pageviews are page_view events in GA4, not a separate hit type
- GA4 has no 'unique pageview' metric; use 'Views' instead
- SPA pageview tracking is handled via history_change events
- Do not compare GA4 pageview counts to UA pageview counts directly
- Avoid duplicate page_view events from multiple GA4 configurations
## Related entries
- [Google Analytics 4 (GA4)](atomicglue.co/glossary/google-analytics-4-ga4)
- [Event Tracking](atomicglue.co/glossary/event-tracking)
- [Session](atomicglue.co/glossary/session)
- [Bounce Rate](atomicglue.co/glossary/bounce-rate)
Last updated July 2026. Permalink: atomicglue.co/glossary/pageview