![\"Two](\"https:\/\/www.lukaswojcik.com\/blog\/wp-content\/uploads\/diagrams\/zwei-kennungen-en.png\")
What a destination is<\/h2>\n
Until now a container loaded a separate library for every Google product: The gain therefore does not lie in file size. A container serving three destinations is larger than one serving none. What disappears is a round in the loading sequence: the document finds the container, the container finds the library, the library reports the first hit. Remove the middle step and everything after it moves forward.<\/p>\n On 9 July 2026 Google published a note on container behaviour for unsupported installation paths. The decisive sentence is that the ID used to load the container controls this behaviour, regardless of the path used. A container loaded with This is the point at which a setup can quietly become narrower. Upgrading an existing Google tag while leaving the old snippet with the measurement ID in place produces a fully capable container in the interface and a restricted execution on the page. Custom HTML tags, third-party vendors and hand-written variables are then missing – not because they were deleted, but because the ID in the source does not permit them.<\/p>\n New deployment snippets will be uniform and will no longer contain the Wherever a consent solution currently holds back or reorders the Google’s page is explicit: no changes will be made automatically, and adopting the new configuration remains a choice. Existing containers, tags, triggers and variables keep working unchanged, and third-party tags remain fully supported.<\/p>\n Optional does not mean without consequence, though. New snippets look different from old ones, and a team looking after two sites may from now on be looking after two different installation styles. The instructions written down in the internal wiki then apply to one site and no longer to the other.<\/p>\n The benefit of an upgrade can be established on the site itself within minutes, before anything is changed. The browser’s network panel, filtered to The second number sits in the interface: how many custom-built tags the container holds. It determines how painful a wrong ID in the source would be.<\/p>\n The upgrade is new, it is optional, and its gain is one round in the loading sequence. That does not justify surgery on a setup that works – but it does justify a preview on a minor site, so that the new snippet, the trigger and the execution have been seen once before the decision arrives.<\/p>\n What pays off immediately is a look at the ID in the source. It is already there, it controls more than it did before 9 July 2026, and it is the one place in this entire change where a silent loss of capability is possible.<\/p>\n","protected":false},"excerpt":{"rendered":" Google is merging the Google tag and Tag Manager: containers gain destinations, new snippets drop the config command, and a release note from 9 July 2026 makes the loading ID decide what the container may do. The upgrade is optional; the ID is not.<\/p>\n","protected":false},"author":1,"featured_media":11509,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[91258,91267,91315],"class_list":["post-10539","post","type-post","status-publish","format-standard","hentry","category-digital-analytics","tag-google-analytics-4","tag-google-tag-manager","tag-web-performance"],"yoast_head":"\ngtag\/js<\/code> once for the measurement ID, once for the ads account, possibly once more for Floodlight. After the upgrade those products are destinations on the container, and the container file itself handles delivery. Google’s description notes that each Google destination still gets its own tag – what is consolidated is the delivery, not the configuration.<\/p>\nThe ID decides, not the path<\/h2>\n
GTM-\u2026<\/code> works as before. A container loaded with a product ID such as G-\u2026<\/code> or AW-\u2026<\/code> is restricted to tags and variables provided by Google.<\/p>\nWhat becomes of the config command<\/h2>\n
gtag('config', \u2026)<\/code> command. In its place comes a trigger named gtm init<\/code>, through which start-up behaviour is configured. For existing setups, that trigger can be told to wait for the old command so that an established order is preserved.<\/p>\nWhat disappears from the snippet\n\n gtag('js', new Date());\n gtag('config', 'G-XXXXXXX'); <- no longer part of the new snippet\n\nWhat takes its place\n\n trigger \"gtm init\" inside the container\n controls when initialisation happens\n can wait for the old config command where an\n existing setup still sends it\n\nWhat the ID controls (release note, 9 July 2026)\n\n loaded with GTM-\u2026 full feature set\n loaded with G-\u2026 only tags and variables provided by Google\n loaded with AW-\u2026 only tags and variables provided by Google<\/code><\/pre>\nconfig<\/code> command, that is precisely the place to inspect before any upgrade. The trigger can reproduce the same ordering, but it does not do so by itself.<\/p>\nWhat optional means here<\/h2>\n
What can be counted beforehand<\/h2>\n
googletagmanager.com<\/code>, shows how many libraries are actually loaded. A single container with one measurement ID often loads only two files; there is little to gain there. A setup grown over years, with an ads account, Floodlight and a separately installed Google tag, loads four or five, and there the arithmetic is worth doing.<\/p>\nWhere waiting is the better move<\/h2>\n