← All posts

Analytics hygiene

Your pageviews stopped counting. Your sales didn’t. Here’s why that’s worse than it sounds.

One of the most expensive analytics problems I see isn’t a dramatic outage. It’s a single number that quietly stops counting while everything around it looks normal.

Here’s the pattern. A store’s Google Analytics 4 property keeps reporting sessions. It keeps reporting purchases and revenue. Month-over-month charts still move up and down in believable ways. But somewhere along the line, pageviews dropped by 99% overnight and stayed there.

Nobody notices for months, because nobody looks at pageviews on their own. And by the time someone does, there’s a hole in the data that can never be filled back in.

How one metric can break while the rest keep working

GA4 doesn’t count “visits” the way older analytics tools did. Everything is an event: a page view is one event, a purchase is another, scrolling and clicking are others. Sessions are stitched together from whatever events arrive.

So if the page view event stops firing but your checkout still sends purchase events, GA4 keeps building sessions out of those purchases and engagement pings. Sessions look fine. Revenue looks fine. Only the page-level numbers go dark.

What actually breaks

  • Page reports go empty or misleading. “Pages and screens” shows a handful of URLs instead of your whole catalog.
  • Pages per session collapses, so engagement looks worse than it is.
  • Product and category analysis stops working. You can’t tell which pages lead to sales.
  • Year-over-year comparisons lie. Next year, every page metric will appear to have exploded.

The usual causes

In my experience it’s almost never Google’s fault. It’s a change on the site that nobody connected to analytics:

  1. A tag manager change. Someone edits the Google tag in Google Tag Manager and turns off “send a page view event when this configuration loads,” often while setting up a different tag.
  2. Enhanced measurement switched off. In GA4’s data stream settings, the automatic page view setting can be disabled with one toggle.
  3. A theme, platform or app update. A new storefront theme or a checkout app can remove or duplicate the original tracking code. Purchases keep flowing because the checkout tracks itself separately.
  4. A cookie consent banner. A new or reconfigured consent tool can block the page view tag while other tags still fire.

How to check your own store in five minutes

  1. In GA4, open Reports → Engagement → Events.
  2. Set the date range to the last 13 months.
  3. Compare page_view with session_start. On a healthy store, page views run several times higher than sessions. If page views are suddenly lower than sessions, something is broken.
  4. Change the chart to show the trend by week. A cliff, rather than a slope, points to a specific change on a specific date.
  5. Write that date down and ask whoever runs the site what changed that week: a theme, an app, a tag, a consent banner.

Google’s free Tag Assistant will then show you, page by page, whether a page view is actually being sent.

Fix it, then stop it from happening again

The fix is usually small once you find the cause: turning a setting back on, restoring a tag, or adjusting the consent configuration. The data you lost while it was broken can’t be recovered, so the real value is in catching the next one quickly.

  • Set an alert. GA4 lets you create a custom insight that emails you when a metric drops sharply. Add one for page views.
  • Annotate the gap. Note the broken date range so nobody makes decisions from those months later.
  • Check the ratios monthly, not just the totals. Page views per session is the early-warning number.

This is exactly the kind of thing a monthly report should catch, and why every report I send includes a short data-quality note alongside the numbers. A chart that looks fine isn’t the same as data that is fine.