Your Google tag becomes a Tag Manager container
Your Google tag becomes a Tag Manager container
Google is merging the Google tag and Google Tag Manager into one product, with a fixed date for the setups that need attention first.
On 17 November 2026 Google documented that every Google tag becomes a Google Tag Manager container. Measurement on the page behaves as before, but tagging, debugging, version history and permissions move into Tag Manager for everyone, including sites that have never used it.
New deployment snippets will be identical for all users and will no longer contain the gtag config command. Installations Google classes as unsupported, where a Tag Manager snippet is used to load a Google Analytics, Google Ads or Floodlight tag ID together with gtag config commands, will receive the upgrade in January 2027, and Google advises adjusting them before then.
What's New
1. One container
Each Google tag becomes a fully capable Tag Manager container. Sites that only ran a Google tag gain interface driven tagging, preview and debugging, and a version history of every change. Google states that the in-page behaviour of the tags does not change.
2. New snippets
All new deployment snippets will be the same and will no longer carry the gtag config command. Google recommends setting initialisation behaviour with the standard Tag Manager initialisation triggers, which can also be set to wait for a config command where an older setup has to be preserved.
3. Permissions
Tag Manager permissions apply across the board, and access to data in Tag Assistant is governed by the container permissions already used in Tag Manager. Who can debug a tag and who can see its data become the same question.
4. January 2027
Unsupported installations, meaning a Tag Manager snippet used to load a Google Analytics, Google Ads or Floodlight tag ID with separate gtag config commands, receive the upgrade in January 2027. Google advises changing them before that date.
What you can do with it
Faster pages: an optimised container sends data directly to Google Analytics, Google Ads and Floodlight instead of loading an additional gtag.js file for them, which removes a request that previously added latency.
Settings live in one place. Google tag settings move into a container level Settings area that applies to every connected destination, so cross domain measurement and similar switches are reviewed once rather than tag by tag.
A real change history: sites that were never on Tag Manager gain versioning, a preview mode and the ability to roll back, without running a migration project to get there.
Access becomes auditable in one system, because container permissions now also govern who can see tag data in Tag Assistant.
Existing containers are not changed for you. Google states that no changes are made automatically and that you choose whether to adopt the new configuration, so the move can be planned and tested.
Current limitations
January upgrade: Google states that unsupported installations receive the upgrade, but not what happens to an installation that has not been adjusted by then.
Timing: There is no published start date for supported installations and no completion date for the conversion, so the state of an individual account has to be checked rather than assumed.
Ownership: Which Tag Manager account receives an automatically created container, and who is granted access to it, is not documented.
Settings conflicts: Container level settings are shared across destinations and a mismatch with a tag's previous settings is not flagged anywhere in the interface.
Scope: The upgrade does not remove Google tags installed outside Tag Manager by a site template or plugin, it does not replace your consent banner, and it does not replace server side tagging.
On the roadmap: Visual tagging, which creates events and conversions without manual code, is in beta for Google Ads purchase conversions and is being rolled out progressively to further use cases. No date is given.
What we recommend
Act now on mixed installations: If a Tag Manager snippet on your site loads a Google Analytics, Google Ads or Floodlight tag ID with gtag config commands next to it, this is the group with a date. Identify it and correct it well before January 2027.
Plan the optimisation: For everyone else, treat the container optimisation as a change with a test cycle: compare the settings that will be imported, check conversions and consent behaviour in preview, then publish. Nothing is applied for you.