Google tags are becoming Tag Manager containers
Google is moving tag management into GTM. Supported installations keep their on-page behaviour, but one legacy setup needs attention before January 2027.
What changes in Tag Manager
In its 17 November 2026 release notes, Google says existing Google tags are being upgraded to Tag Manager containers. Sites that only used the Google tag gain GTM’s interface, debugging and version control. Container permissions also govern access to data in Tag Assistant.17 November GTM release notes ↗
The Google tag connects your site to measurement products such as Google Ads and GA4. A GTM container manages tags and controls when they fire through triggers. After the upgrade, each Google destination has its own tag, preserving your existing setup and automation-event triggers. For a supported installation, the upgrade itself leaves on-page behaviour and data collection as they were.
If you already use GTM, Google also offers an optional container optimisation. That is a separate change you can preview before publishing.Optional GTM container optimisation ↗
Meltzer Media
Tag settings move. Measurement stays in place.
Google Tag Manager · 17 November 2026 release
The exception to check before January 2027
Google says unsupported installations will receive the upgrade in January 2027. One example is a site that loads a G-, AW- or DC- ID through the GTM snippet path, gtm.js, and relies on gtag('config'). If you find that combination or received an email from Google, follow the official remediation guide before the upgrade.Google’s guide for unsupported installs ↗
New deployment snippets use one format without the gtag('config') command. Google recommends using GTM’s Initialization trigger for startup behaviour. It can also wait for the legacy config command where needed. If you have a working, supported installation, the interface change alone does not call for a code swap.
What to verify after the upgrade
Start with access. Confirm your team can open the right container and use Tag Assistant. Then test one action that matters, such as a completed enquiry form. Check that it fires once, reaches the intended destination, and behaves as expected when consent is granted or denied.
A fired tag shows the trigger ran. For a lead that matters to bidding or reporting, check receipt in the relevant destination too, such as GA4 DebugView for a GA4 event.
Meltzer Media
Three checks for your tagging setup
Identify the install
Check the snippet and ID. A GTM snippet with a G-, AW- or DC- ID is a warning sign.
Review the exception
Using an unsupported install? Follow Google’s guidance before January 2027.
Test one conversion
Check the trigger, destination and behaviour with consent granted and denied.
The January 2027 timing applies to unsupported installations.