Why pageviews drop after switching to GA4 and 3 metric checks

Part of the guide: Hotjar vs Lucky Orange: which analytics features best fit your website goals

Explore how GA4’s new tracking model and metrics transform pageview counts and learn exact checks to pinpoint real drops versus measurement changes.

What is a page view in GA4 and how it differs from UA

GA4 counts pageviews as an explicit ‘page_view’ event each time a page loads or is viewed, unlike Universal Analytics (UA) where pageviews were tracked as hits.

UA’s unique pageviews metric combines pageviews within a session, counting a single page more than once differently than GA4’s event-based approach.

GA4’s model tracks each page_view event individually, ignoring UA’s notion of uniqueness within a session, which often lowers the reported pageview totals compared to UA.

GA4’s page_view events are also influenced by enhanced measurement features that automatically track certain user interactions like scrolls and outbound clicks, which can cause discrepancies if similar events were manually tracked in UA and filtered differently. For instance, if your UA setup excluded some internal page reloads or soft navigations, GA4 might count them all, causing unexpected shifts in pageview totals. We go through tools for fast seo reports step by step elsewhere on the site.

Another key difference is that GA4’s page_view event triggers on history state changes for single-page applications (SPAs), where UA often required additional tagging or did not track SPA navigation well. This can sometimes lead to GA4 reporting more pageviews on SPAs, but if the setup is incomplete or inconsistent, it might appear lower due to missed events. Checking your SPA configuration in GA4 is crucial to avoid miscounted pageviews.

Difference between 'page_view', 'unique page views', and 'pages and screens' in GA4

'Page_view' in GA4 is a raw event tally—each page visit triggers one event regardless of session or user.

'Unique page views' in UA filtered duplicates per session, so the GA4 count may appear lower because it counts all views rather than filtered uniques.

'Pages and screens' is a GA4 report metric that aggregates page_view events across web and app, combining page paths and screen names, which may further confuse comparisons.

In GA4, the metric 'pages and screens' combines data from both web pages and app screens, unifying measurement across platforms. This aggregation means the metric can include screens from mobile apps alongside traditional web page views, which can inflate or deflate counts depending on your property setup and traffic sources. Therefore, direct comparison with UA’s web-only unique pageviews without segmenting by platform can be misleading.

Moreover, GA4 lacks a direct equivalent of UA’s unique pageviews metric, which aggregated pageviews per session to count only one per page per session. GA4’s raw page_view event counts every instance without deduplication per session. To approximate unique pageviews in GA4, you’d need to create explorations or custom reports applying filters or deduplication logic, which requires additional analysis and is not default behavior.

How to interpret new vs returning users impact on pageviews

GA4 tracks new and returning users differently than UA, often showing more new users due to its identification methods, which affects session counts and pageview attribution.

Returning users in GA4 are identified by client ID and user ID more strictly, which can reduce return sessions and lower pageviews tied to returning visitors.

If your site depends heavily on repeat visitors, GA4’s stricter user model might show an apparent drop in pageviews that is just a tracking artifact, not a real loss.

The impact of new versus returning users on pageviews becomes more apparent when considering device and cross-platform behavior. GA4’s user identification relies heavily on Google signals and user ID if implemented, which can better unify user identities across devices, sometimes increasing new user counts if users are not logged in or identified consistently.

For example, a returning user on UA identified by a cookie may be counted as new in GA4 if they clear cookies or use a different device without login, leading to a drop in returning user sessions and associated pageviews. This can skew your understanding of audience loyalty and engagement if not accounted for.

To check this effect, compare the ratio of new to returning users before and after migration, and review your user ID implementation if applicable. A sharp increase in new users with concurrent pageview drops often signals identification differences rather than real traffic loss.

Why page path vs landing page metrics matter in GA4

In GA4, page path represents every page loaded during sessions, while landing page indicates the first page of a session, but their metrics are reported separately and can differ significantly.

Landing page reports in GA4 often show fewer pageviews because they count only session entries, while page path measures every page visited across sessions.

Confusing these two metrics can mislead you into thinking pageviews dropped when it might be a shift in how sessions start or user paths change.

Page path metrics in GA4 include all page_view events, reflecting the total number of pages users visit during sessions, while landing page data specifically counts the first page loaded per session. Because GA4 sessions restart on campaign source changes, landing page counts may shift even if overall pageviews remain stable.

For example, if a user arrives via a campaign, browses multiple pages, then returns through another campaign source shortly after, GA4 may count two landing page entries but fewer pageviews if sessions are split and some page_view events are not logged due to tagging or user behavior.

This distinction means evaluating both metrics together provides insight into user journey dynamics, session fragmentation, and traffic source impact on pageview trends, avoiding misinterpretation of apparent drops when the issue lies in session or campaign parameter handling.

How time on page and session definitions affect pageview counts

GA4 defines sessions differently with a 30-minute inactivity timeout, but it also resets sessions when campaign parameters change, potentially splitting sessions and lowering pageview counts.

Time on page calculations are event-based in GA4, relying on engagement time from events, which can differ from UA’s simpler timestamp method.

Short sessions or rapid page exits may reduce session lengths and pageviews counted, especially if your site has many single-page visits.

GA4’s session definition can increase session counts by splitting sessions on campaign parameter changes, which often reduces average pageviews per session and total pageviews if events are lost or misconfigured. For example, if a campaign tag changes mid-visit, GA4 starts a new session, possibly halving pageviews recorded per session compared to UA’s more lenient model.

Engagement time metrics in GA4 use user interactions and background events to estimate time on page, which can be more accurate but also show lower times if users navigate quickly or have intermittent connectivity. This affects bounce rate and engagement reports that indirectly influence interpretations of pageview quality and volume.

Sites with high bounce rates or many short visits will see greater discrepancies in pageview counts and session durations due to these measurement changes, so analyzing engagement metrics alongside pageviews helps clarify whether drops indicate real traffic loss or measurement shifts.

• Session timeout – 30-minute inactivity resets the session.
• Session restart – Campaign change can trigger a new session.
• Engagement time – Event-driven, not time stamps.

Pageviews drop after switching to GA4: 3 metric checks to diagnose why

First, check if the ‘page_view’ event fires on every page load without filters or tag misconfigurations blocking it.

Second, compare the ‘pages and screens’ report in GA4 to your UA pageviews to understand platform-wide behavior differences.

Third, inspect user and session counts to see if GA4’s stricter user identification or session splitting triggers drop in metrics.

1. Verify your GA4 ‘page_view’ event implementation across pages.
2. Review ‘pages and screens’ report and compare to UA unique pageviews.
3. Analyze new vs returning user ratios and session counts for anomalies.

Questions people still ask

Having switched my own sites to GA4, I learned the drop is often metric semantics, not actual traffic loss.