Your Google tag is becoming a Tag Manager container
Google is turning every Google tag into a Tag Manager container. Most tags won’t behave differently, but unsupported installs get the upgrade in January 2027.

The little snippet that feeds your website’s visits to Google Analytics and your sales to Google Ads is getting a promotion. Google is turning every Google tag into a full Google Tag Manager container.
For most sites, nothing visible changes. But if your tags were installed in a way Google doesn’t support, the upgrade arrives in January 2027 and Google wants the setup fixed first.
Google announced the change in its Tag Manager release notes on 17 November. It follows an August update that set out the merger in more detail.
Two tools become one
Until now, there were two ways to put Google’s tracking on a site. The Google tag (also called gtag.js) is a single snippet you paste in, usually to run Google Analytics 4 or Google Ads conversion tracking. Google Tag Manager is a separate tool for managing lots of tags, including ones from other companies, without editing the site’s code each time.
Google says “each Google tag becomes a Tag Manager container”. Sites that only use the Google tag get Tag Manager’s point-and-click tagging and debugging tools. They also get version control, which lets you roll back a change.
What stays the same
The release note says the upgrade “won’t change the in-page behavior” of your tags. Each Google destination, such as an Analytics property or an Ads account, keeps its own tag, along with your existing setup and triggers.
What does change is the code Google hands out. All new installation snippets will be the same, and they won’t include the “gtag config” command that older snippets used. Google recommends using Tag Manager’s initialisation triggers instead. A trigger can still wait for the old command if you want to keep a legacy setup.
Who gets the January deadline
The date applies to what Google calls an unsupported installation. That’s a site that loads a Google tag ID starting with G-, AW- or DC- through the Tag Manager snippet. Using a Tag Manager snippet with gtag config commands for those IDs is also unsupported.
Sites set up this way “may experience unexpected changes” to how their tags behave, according to Google’s help page. Tag Manager snippets will soon stop recognising or waiting for gtag config commands. Users of containers with this setup have been emailed.
Google doesn’t give an exact day in January or say what happens to a site that isn’t fixed. Its advice is to adjust the setup before then. The fix is one of two things:
- If you only use Google’s own tags, remove the Tag Manager snippet and its config commands. Paste the standard Google tag snippet straight after the opening
<head>tag on every page. - If you also use Tag Manager for other companies’ tags, keep the Tag Manager snippet. Swap the G-, AW- or DC- ID for your Tag Manager ID, which starts with GTM-, then set up the Google tag inside Tag Manager.
That second point matters for another reason. Google’s help pages say a G- or AW- ID can only run Google’s own tags. To run tags from Meta, LinkedIn or anyone else, you need a GTM- container ID.
You can check the result in Google’s Tag Assistant, where your tag ID should show a green or blue status. If you switched to the Google tag snippet, your browser’s developer tools should show the page loading googletagmanager.com/gtag/js rather than gtm.js.
Who can see your data
There’s also a quieter change. Tag Manager’s permission settings “will now apply across the board”. Access to data in Tag Assistant, Google’s debugging tool, will be managed through the container permissions you set in Tag Manager.
So anyone with access to your Tag Manager container also gets matching access to Tag Assistant data. If a former agency or freelancer is still on the list, now is a good time to remove them.
Already on Tag Manager?
Sites already using Tag Manager are offered a recommended but optional container optimisation instead. No changes are made automatically. The changes go into a workspace you can preview, and they can be rolled back.
PPC Land reports that the “Configure tag settings” link in GA4 has begun opening an automatically created GTM- container. Google hasn’t published a rollout schedule.
Measurement changes have a habit of breaking quietly. We’ve covered another one: the GA4 hostname filter that can discard data for good if it’s set up wrong.
Checklist
- Search your inbox for Google’s email. Google says it emailed users of containers with the unsupported setup; check the account that manages your Tag Manager.
- Ask who installed your tags how they did it. If a G-, AW- or DC- ID is loaded through the Tag Manager snippet, it needs fixing before January 2027.
- Use a supported snippet. Either the standard Google tag snippet after the opening head tag, or the Tag Manager snippet with your GTM- ID.
- Check with Tag Assistant after any change. Confirm your tag ID shows a green or blue status.
- Review who has Tag Manager access. Container permissions now also control who can see data in Tag Assistant.
- Preview before you optimise. If you already use Tag Manager, test the optional optimisation in a workspace before you publish it.
Tick items as you go. Your ticks stay in this browser.




