The technical details.

We verify that the automatic page_view event actually fires on every page, check the dataLayer for proper push events, and confirm the network request to Google's collect endpoint actually completes — not just queues.

Why your business cares.

Page views are the spine of GA4. Sessions, navigation paths, landing page reports, exit reports, top content, scroll depth, and almost every funnel rely on page views firing reliably. If page views are missing or unreliable, the entire reporting layer above them is wrong.

What you're missing.

  • Top-pages reports under-report your most-visited URLs, making it impossible to know what content actually drives the business.
  • Single Page Application (SPA) sites are especially prone — virtual page views from React/Vue/Next.js routing often don't fire by default.
  • Funnel reports break — a customer who really went home → product → cart → checkout looks like they teleported directly to checkout.

What this looks like in different businesses.

A property listing site is a React SPA. Virtual page views aren't configured, so GA4 only sees the homepage view. Every property listing — what users actually browse — shows zero pageviews. The team can't tell which listings get attention, so listing strategy is pure guesswork.

A consulting firm's blog has gtag.js, but the page_view event was disabled during a 'consent mode' fix. Blog visitors are tracked as sessions but the specific articles they read aren't. Content marketing investment can't be tied to lead generation.

A course platform uses lesson modals that change the URL but don't trigger page views. The instructor sees 'course homepage' as the top page and assumes nobody finishes lessons — when actually 70% complete, the data just doesn't track lesson views.

Curious about your site?

Find out if this is happening on your site.

A free audit runs all 12 detectors — including Page View Tracker — on every page of your site.

Request a Free Audit