Skip to content
weballin

weballin DIGIWIKI

Page View

Page views are the number of page loads collected through the page_view event in GA4, and are automatically counted just by installing GA4. It is the same concept as UA's page view, but is processed with an event structure and requires separate settings in SPA. Check in Reports → Engagement → Pages and screens.

weballin

In GA4, page views are collected with the page_view event name. Basic collection occurs simply by installing the GA4 tag as an automatic collection event, and is also automatically detected in SPA (History API Changes) if the 'Page Views' toggle in Enhanced Measurement is turned on. The page_view event automatically includes parameters such as page_title, page_location, and page_referrer.

Difference from UA: In UA, pageviews were an independent hit type and were the basis for session counting. In GA4, page_view was integrated as a type of event. The method of counting sessions based on page views has also changed, with GA4 sessions starting with the session_start event and ending based on 30 minutes of inactivity.

SPA Note: In SPA such as Next.js, React, and Vue.js, automatic page_view may not be triggered because the browser does not actually reload the page even if the routing changes. You must either turn on the History API change detection feature in Enhanced Measurement or add code to manually send the page_view event when routing changes.

GA4 screen path: You can check the number of views by page in Reports → Engagement → Pages and screens report. In Explorations, you can set up page funnel or path analysis based on the page_view event.

weballin's practical perspective: Monitor trends in page views on major pages (consultation reservation page, procedure detail page, cost information page) on the hospital site on a weekly basis. If you see a sudden drop in the number of views on a particular page, it could be an early sign of a technical error or a drop in SEO rankings.

Key takeaways

  • It is collected as the page_view event name in GA4, and is automatically collected just by installing the GA4 tag.
  • The page_title, page_location, and page_referrer parameters are automatically collected together.
  • Automatic detection may not be possible in SPAs (React, Next.js, etc.) and enhanced measurement or manual configuration is required.
  • Unlike UA pageview hits, in GA4 they are processed as a single type of event.
  • You can check the number of views, users, and sessions for each page in Reports → Engagement → Pages and screens.

References

Frequently asked questions

Why are the numbers different from UA when looking at pageviews in GA4?

Because GA4 and UA have different session counting methods, bot traffic filtering standards, and SPA processing methods, differences in numbers occur even during the same period. This difference must be taken into account when comparing the same period after switching to GA4, and comparing trend direction is more meaningful than simple number comparison.

Are the pages with the most views necessarily important?

Not necessarily so. The number of views shows the volume of page views, but separate indicators (bounce rate, key event completion rate, scroll depth, etc.) must be looked at to determine whether the user received the desired information on the page and converted.

Related terms