为何GTM默认加载GA(ga.js)与UA(analytics.js)？如何禁用冗余脚本？

Let's break this down clearly—this is a common gotcha I've troubleshooted multiple times for e-commerce sites optimizing load speed.

Why GTM Loads Both Scripts #

First, the root causes behind this behavior:

1. Legacy Compatibility Logic: GTM was built to support users still on the old ga.js (Classic Analytics) when Universal Analytics launched. Even if you don’t use Classic GA, hardcoded fallback checks in GTM’s core gtm.js still scan for signs that old GA might be needed—and trigger the load if those checks aren’t explicitly blocked.
2. Hidden Legacy References in Your Container: Even if you didn’t intentionally add Classic GA tags, double-check your GTM setup. If you have any of these, GTM will auto-load ga.js to support them:
   • Tags using the "Google Analytics (Classic)" template (not the Universal Analytics one)
   • Custom variables or triggers that reference the old _gaq queue
   • Custom HTML snippets that call Classic GA methods
3. Debug Mode Side Effect: The code snippets you shared include checks for c["60"]—that’s GTM’s debug mode flag. While debug mode can trigger extra loads, even in production, the legacy fallback logic might still fire if no block is in place.

How to Disable ga.js Loading (Practical Solutions) #

Solution 1: Clean Up Your GTM Container (Most Recommended) #

Start here to eliminate the root cause:

• Audit all tags: Go through every tag in your container and delete any using the "Google Analytics (Classic)" template. Replace them with the "Universal Analytics" template if you need equivalent tracking.
• Check variables: Delete any custom variables that reference _gaq or Classic GA properties. Ensure all GA-related variables use Universal GA’s ga() method or dataLayer values.
• Scan triggers: Make sure no triggers are set to fire Classic GA-specific events or conditions.

After cleaning, clear your browser cache and test—ga.js should stop loading automatically.

Solution 2: Block ga.js with a Pre-Load Script #

If you’ve cleaned the container but ga.js still loads (thanks to GTM’s stubborn legacy fallback), use this workaround:
Create a Custom HTML Tag in GTM with the following code, set to trigger on Page View - Initialization (before any other GA tags):

// Pre-initialize the Classic GA queue to trick GTM into thinking it's already loaded
window._gaq = window._gaq || [];
// Override the push method to prevent actual Classic GA events from firing
window._gaq.push = function() {};

GTM checks for the existence of _gaq to decide whether to load ga.js. By pre-defining this object (and neutering its push method), GTM skips the ga.js request entirely.

Solution 3: Emergency Inline Block (Quick Fix) #

If you need an immediate fix without modifying GTM, add this snippet before your GTM embed code:

<script>
// Pre-empt GTM's ga.js load check
window._gaq = [];
window._gaq.push = function() {};
</script>
<!-- Your existing GTM embed code goes here -->
<script>(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start': new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0], j=d.createElement(s),dl=l!='dataLayer'?'&amp;l='+l:'';j.async=true;j.src= 'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f); })(window,document,'script','dataLayer','GTM-XXXX');</script>

Verification Steps #

After applying any solution:

1. Open Chrome DevTools > Network tab
2. Filter requests by ga.js
3. Refresh the page (use Ctrl+F5 to bypass cache)
4. Confirm no ga.js request appears, while analytics.js loads normally

内容的提问来源于stack exchange，提问作者Marcos Pérez Gude