AMP页面自2018-01-23起无法在Analytics中追踪的排查求助

Let's break down the possible issues and actionable fixes step by step—since your AMP pages tracked correctly before that specific timestamp, this is almost certainly tied to a recent configuration change, cache issue, or subtle AMP specification mismatch:

1. Validate Your AMP Analytics Implementation #

AMP has strict requirements for analytics tracking that differ from standard web pages. Even if your GTM setup was correct before, double-check:

• Ensure you're using an AMP-specific GTM container (not your regular web container—AMP containers are separate and optimized for AMP's restrictions).
• Verify your page uses the <amp-analytics> component correctly, not standard <script> tags. Use the AMP Validator (built into Chrome DevTools or the official AMP validation tool) to catch syntax or spec violations that might block tracking.
• Confirm the <amp-analytics> configuration includes your correct Analytics tracking ID (tid parameter) and a valid trigger (e.g., trigger: "visible" or trigger: "pageLoad" to fire on page load).

2. Audit GTM AMP Container Changes #

Since tracking stopped abruptly, check your GTM version history for changes made around Jan 23, 2018 EST 9:30:

• Did someone disable the Analytics tag, modify its trigger conditions, or break a required variable (like the page URL or tracking ID)?
• Roll back to the last known working GTM version and test if tracking resumes. This is the fastest way to rule out a bad configuration push.

3. Check Analytics View Filters #

It's possible your Analytics data is being filtered out accidentally:

• Navigate to your Analytics view's Filters section. Look for newly added filters (e.g., IP exclusion, hostname filtering) that might be blocking AMP page traffic.
• Test with an unfiltered Analytics view to see if the AMP pageviews appear there—if they do, adjust your filter rules to include AMP hostnames (including AMP Cache domains like cdn.ampproject.org).

4. Verify Data is Being Sent to Analytics #

Use your browser's DevTools to confirm tracking requests are leaving the AMP page:

• Open the Network tab, load your AMP page, and look for requests to https://www.google-analytics.com/collect.
• If no collect requests appear: Your AMP Analytics tag isn't firing—check triggers and component setup.
• If requests do appear but don't show up in Analytics: Inspect the request parameters (look for tid to confirm your tracking ID, cid for a valid client ID, and dp for the correct page path). Missing or invalid parameters will cause Analytics to drop the hit.

5. Flush the AMP Cache #

AMP pages are often served from Google's AMP Cache, which might be serving an outdated version of your page without working tracking:

• Append ?amp_action=flush to your AMP page URL (e.g., https://yourdomain.com/page.amp?amp_action=flush) to force the cache to refresh with your latest code.
• Wait a few minutes, then test tracking again to see if the updated page sends hits to Analytics.

6. Correlate Ad Impressions and Pageview Drops #

The disconnect between rising ad impressions and falling pageviews suggests:

• AMP Cache traffic might be untracked (since cached pages use the cache's domain, not yours)—ensure your tracking includes cache-hosted AMP pages in its scope.
• Some AMP pages might be failing to load fully, but ad units still render (rare, but possible). Check the AMP Validator for load errors that could interrupt tracking before it fires.

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