Google Tag Manager Can Now Send Google Data Without Loading gtag.js

On 12 October 2026 Google added destination tags to Tag Manager. Until then, a Google Analytics or Google Ads tag inside a container did not send its data itself: it loaded Google’s separate gtag.js library to do it, so every page carried a second Google script beside gtm.js. Google’s release note says that extra JavaScript “could cause latency in measurement transmission”; a destination tag sends the data from the container directly. Google describes the result as “faster website performance” but publishes no figure.

Nothing changes unless you act. Existing containers show a banner on the Overview page offering the switch, and the changes land in a workspace you can test in Preview before publishing. Three things need checking there rather than accepting. Google states a destination tag sends a page view automatically, so a container that also sends page_view from a separate event tag would count every page twice. Options that used to sit inside each Google tag, user-provided data collection among them, move to one Settings tab that applies to every Google destination in the container, so confirm each is set the way you intend. And test with consent denied, then granted, to confirm hits behave as they did before.

Once published, a request to gtag/js?id=G- should no longer appear in the browser’s network panel. Rolling back a container version restores the old tags, but not permissions granted to linked Google accounts during the switch, because Google does not version them.

Sources

• Release notes for Google Tag Manager (12 October 2026), Tag Manager Help
• Optimize your Google Tag Manager container, Tag Manager Help
• Destination and destination tags, Tag Manager Help
• Major Google Tag Manager update: Optimized Tagging Experience, Analytics Mania