Google Analytics虚假页面浏览量：疑似自动触发的异常访问排查

Nice catch on that odd GA behavior—let’s walk through how to dig into this and fix it, since your hunch about Chrome tab recovery makes a lot of sense.

第一步：排查验证你的推测 #

• Check session and behavior metrics: Pull up the two duplicate pageviews in GA’s Explorer report first. Look at the Session ID—are they part of the same session? If yes, check the time on page for the "suspicious" hit: auto-loaded tabs often show 0 or near-0 time on page, while real user visits will have meaningful engagement. Also, check if there are any subsequent events or pageviews after this pair; auto-reloaded tabs rarely lead to further user actions.
• Replicate the browser scenario: Grab a Windows 10 machine and install Chrome 65.0.3325.181 (you can find archived versions via Chrome’s official repository). Enable "Continue where you left off" in Chrome settings, open your homepage, then restart the browser. Monitor GA’s Real-Time report to see if two pageviews fire—this will confirm if tab recovery is the culprit.
• Audit your GA implementation: Look at how your pageview is triggered. If you’re using window.onload or DOMContentLoaded to send hits, Chrome’s tab recovery will re-execute these events when restoring tabs. Check if your code has safeguards against duplicate sends—like tracking if the page was already loaded in the current session.
• Analyze request details: Compare the two pageview hits via GA’s hit details or Chrome DevTools’ Network tab. Auto-loaded hits might lack UTM parameters, have identical timestamps within a second, or no referrer, whereas real visits often have clear user-initiated context.

第二步：解决方法 #

Once you confirm the root cause, here are actionable fixes:

• Shift to user-centric triggers: Instead of sending pageviews on page load, trigger them when the user interacts with the page (e.g., scroll, click, or when the page becomes visible via the visibilitychange event). This ensures only intentional visits are counted. Example code:

  document.addEventListener('visibilitychange', function() {
    if (document.visibilityState === 'visible' && !sessionStorage.getItem('pageViewSent')) {
      gtag('event', 'page_view');
      sessionStorage.setItem('pageViewSent', 'true');
    }
  });
  

• Add client-side duplicate filtering: Use sessionStorage to track the last time a pageview was sent for the current URL. Skip sending hits if a duplicate trigger happens within a short window (e.g., 60 seconds):

  const currentUrl = window.location.href;
  const lastViewTime = sessionStorage.getItem(`lastView_${currentUrl}`);
  
  if (!lastViewTime || Date.now() - parseInt(lastViewTime) > 60000) {
    gtag('event', 'page_view');
    sessionStorage.setItem(`lastView_${currentUrl}`, Date.now().toString());
  }
  

• Set up GA backend filters: In your GA admin panel, create a custom filter to exclude duplicate pageviews from the same session/URL within a minute. Use advanced filters to compare Session ID, Page, and hit timestamps, keeping only the first occurrence.
• Target the specific browser version: Since this issue is isolated to Chrome 65, add conditional logic for this user agent. For example, delay the pageview send by 1-2 seconds to let the browser finish tab recovery, or require a small user interaction before sending the hit.

内容的提问来源于stack exchange，提问作者MandyShaw