Google is finishing the conversion of standalone Google tags into full Google Tag Manager containers, according to a LinkedIn post published today by Julius Fedorovicius, founder of analyticsmania.com. In Google Analytics, the "Configure tag settings" link on a web data stream now opens a Tag Manager container created for that stream, identified by a GTM- ID and topped by a banner that reads "Your Google tag has been upgraded to a Tag Manager container."
In Short
Google is moving the tag behind each Google Analytics web stream into its own Google Tag Manager container, and the latest batch of accounts is now being converted. It matters to anyone who set up Analytics or Google Ads with the plain Google tag and never opened Tag Manager, because the tag's settings now sit inside a container with workspaces, versions and container-level permissions. Google says the upgrade does not change how the tag behaves on the website; what changes is where its settings are kept and who can edit them.
What Fedorovicius reported
The post runs to three short paragraphs and one image. It opens with a line in quotation marks - "Your Google tag has been upgraded to a Google Tag Manager container" - and then describes where the change appears.
"Google is finalizing its update with the latest batch. If you're in Google Analytics and go to 'Configure tag settings' inside the Data Stream, you will be taken directly to the new GTM container that was created for that stream," Fedorovicius wrote.
The second observation concerns properties that are still being built. "The flow for creating a new data stream has changed slightly, too (where the UI checks if any GTM container is already installed on a website and it suggests using that container)," according to the post.
Two details stand out. The first is the word "batch": Google has been converting accounts in waves rather than all at once, and Fedorovicius describes the current wave as the one that finishes the job. The second is the phrase "created for that stream". The container is not one the account owner set up. Google generated it, named it and linked it to the stream.
Fedorovicius describes himself on LinkedIn as a Google Tag Manager and Google Analytics enthusiast. His site, analyticsmania.com, publishes guides on both products, including one on the separate container optimization flow discussed below.
What the upgraded container shows
The image in the post places two screens side by side. On the left is the Google Analytics panel titled "Web stream details". An arrow points at the section headed "Google tag", and a box surrounds the "Configure tag settings" entry. Other entries in the panel, partly hidden behind the second screen, cover modifying and creating events, redacting data, managing tags connected to the stream and viewing tag instructions.
On the right is the Tag Manager container that the link now opens. Its contents, as visible in the image, are recorded below.
| Element | What the image shows |
|---|---|
| Product header | Tag Manager |
| Container name | Website |
| Container ID | GTM-MVRZP4GH |
| Top tabs | Workspace, Versions, Admin |
| Banner, first line | "Your Google tag has been upgraded to a Tag Manager container" (cut off at the right edge) |
| Banner, second line | "now have access to advanced features like better debugging and" (cut off) |
| Current workspace | Default Workspace |
| Left navigation | Overview, Settings, Tags, Triggers, Variables, Folders, Templates, Show less |
| Main panel | "Welcome to Google Tag M..." (cut off) |
| Container quality | "No Recent Da..." (cut off) |
| Workspace card | Default Workspace, Pending Changes |
The container quality line matters more than it looks. "No Recent Data" is a status Google introduced in October 2024 for tags that had not been detected in the previous 48 hours, alongside the older Excellent, Good, Needs Attention and Urgent levels. The same diagnostics now sit on a container that, until the upgrade, the account owner may never have opened.
The navigation follows the redesigned layout. When Google first described the new interface, Triggers, Variables, Templates and Folders were grouped under a collapsible Advanced section. In the image all four are listed in the left-hand menu with a "Show less" control beneath them, which indicates that section has been opened.
How the path works
According to Fedorovicius' post and Google's Analytics Help Center page "Configure your Google tag settings", the route from a Google Analytics property to the new container has four steps.
- In Google Analytics, the Admin area lists the property's data streams. Google's Help Center describes opening Admin, then Data streams, then selecting the stream.
- The "Web stream details" panel for the selected stream includes a section headed "Google tag".
- That section contains the "Configure tag settings" entry, which until now led to the Google tag's own settings.
- According to Fedorovicius, the entry now takes the user "directly to the new GTM container that was created for that stream", where the upgrade banner appears above the Workspace tab.
For new properties the order is different. According to the post, the data stream creation flow now checks whether a Tag Manager container is already installed on the website and proposes using that container. Google has not published documentation of this detection step in the Analytics or Tag Manager help pages reviewed by PPC Land.
What Google said in May and August
None of this arrives unannounced. Google set out the plan on May 20, 2026, the same day as Google Marketing Live, in a Help Center page that PPC Land examined at the end of May. That page, "Updates to Google tag and Google Tag Manager", now carries a date of August 20, 2026; when it reappeared, PPC Land found it was the May text re-dated, with no new capability added.
The page is organized under three headings: "Simplified user interface", "Google tag and Google Tag Manager unification" and "Visual tagging". The unification section opens with the sentence that Fedorovicius' post now confirms in practice: "Your Google tags will be upgraded to fully capable Google Tag Manager containers."
Google's next paragraph sets the limits of the change. "This upgrade will not change the in-page behavior of the Google tags. Rather, advertisers who use Google tag will gain the option to use Google Tag Manager features," according to the page. "Each Google destination will have its own tag, preserving your existing setup and triggers for automation events."
A note follows on code. "With this change, all new deployment snippets will be the same. Additionally, they will not have the gtag config command," the page states. Google recommends handling initialization with the gtm init trigger instead.
| Item | What Google's Help Center page says |
|---|---|
| Google tags | "will be upgraded to fully capable Google Tag Manager containers" |
| Behavior on the website | "This upgrade will not change the in-page behavior of the Google tags" |
| Destinations | "Each Google destination will have its own tag, preserving your existing setup and triggers for automation events" |
| Google tag settings | "will be brought into the new Settings tab and your event tags will remain unchanged" (under the optimization section) |
| New deployment snippets | Identical for all; no gtag config command |
| Initialization | gtm init trigger recommended |
| Existing Tag Manager containers | Optimization recommended, not applied automatically |
| Who can start optimization | Users with edit, approve or publish permissions on the container |
| Account links | Read access granted by default; adjustable in user management |
| Visual tagging | Beta, purchase conversions in Google Ads only, more use cases "throughout the year" |
| Timing of the upgrade | Not stated |
Upgrade versus optimization
Two processes share one vocabulary, and the difference is easy to miss. The first is the upgrade of standalone Google tags - the gtag.js site tag that Google Ads and Analytics setup screens have handed to advertisers for years. The second is the optimization of containers that already exist in Tag Manager.
Google's sentence about choice belongs to the second. Under the heading "Optimize your Google Tag Manager container", the page reads: "It's recommended for advertisers to upgrade and optimize their Google Tag Manager containers. However, no changes will be made automatically, and you can choose whether to adopt the new configuration." Advertisers who use Tag Manager are prompted through an optimization banner. Once optimized, a container sends data directly to Google destinations instead of loading gtag.js as a separate library, and the Google tag's settings move into the container's Settings tab.
Fedorovicius' own guide to that optimization flow, on analyticsmania.com, makes the same point: the migration is not done automatically, and it is tested in a workspace before anything is published.
The standalone tag upgrade is different. The banner in the post is written in the past tense - the tag "has been upgraded" - and Google's page offers no opt-out for it and no schedule. Google explained the reasoning in a Tag Manager release note dated October 12, 2026, titled "Optimizing Google Tag Manager containers". The Google tag that was loaded alongside a container "had its own settings and permissions, which sometimes made troubleshooting difficult", according to the note, which says destinations and tags now have a clear relationship inside the container.
Container IDs and what is allowed to run
The ID in the image deserves attention. The container opened from the Analytics stream carries a GTM- prefix, not the G- prefix of a Google Analytics measurement ID. In Google's tagging system, the prefix is not cosmetic.
A release note dated July 9, 2026, "Updates to container behavior for unsupported installation paths", made the loading ID the deciding factor for what a container may execute. "Moving forward, the ID used to load the container will control this behavior, regardless of the path used," according to Google. "Containers loaded with a GTM-XXXX ID won't be restricted, while product-specific ID types like G-XXXX or AW-XXXX will only permit tags and variables provided by Google."
| ID used to load the container | What the container may run (July 9, 2026 release note) |
|---|---|
| GTM-XXXX | Not restricted |
| G-XXXX (Google Analytics) | Only tags and variables provided by Google |
| AW-XXXX (Google Ads) | Only tags and variables provided by Google |
PPC Land reported at the time that the rule replaced a path-based restriction that had locked down some GTM- containers by mistake. Three months later, on October 8, Google stopped gtm.js container snippets from waiting for gtag('config') commands, which now appear in the dataLayer as gtag.config events. Read together with the May note on identical snippets without a config command, the sequence points in one direction: a single container snippet, with the Google tag's settings held inside the container rather than in code on the page.
What the post does not establish is which ID a website loads after its stream has been upgraded. Google says in-page behavior does not change, which suggests sites keep loading the tag they already have. Whether owners are expected to switch the snippet to the new GTM- ID, and what the July 9 restrictions mean for a container reached through a G- ID, is not addressed in either source.
Why the change matters
For a large share of advertisers, the Google tag was the whole of their tagging setup. They copied a snippet from Google Ads or Analytics, pasted it into a website template and managed events from inside the ad or analytics interface. Tag Manager was a separate product with its own learning curve - one that PPC Land described in May as far more complex than most marketers think, spanning six domains from tag configuration to security and compliance.
The upgrade puts those accounts inside that product without a migration project of their own. Workspaces, version history and preview mode become available to tags that never had them. So do the permission model and the risk that comes with it: anyone with publish rights on the new container can now change what runs on the site.
The move also fits a pattern of Google pulling tag management closer to its advertising products. In May, Tag Manager began appearing inside the Google Ads interface through Data Manager, with a no-code flow for upgrading existing tags; at least one practitioner questioned at the time whether embedding the tool in an ad platform undermines its independence. Visual tagging, the no-code event builder announced alongside the merge, is in beta for Google Ads purchase conversions. Tag Manager Italia's Matteo Zambon argued in August that it covers the easy 70 to 80% of cases, leaving data layer design, server-side setups, consent and cross-domain tracking to specialists.
Agencies face a practical question. Who owns a container that Google created automatically for a client's Analytics stream, and which users inherited access to it? Google's page says account links are created with Read access by default and that permissions can be changed in Tag Manager's user management. It does not say how access to an auto-created container is assigned in the first place.
What remains unclear
Google has not published a schedule, a batch count or the number of tags converted, and neither Google nor Fedorovicius says which Tag Manager account holds the auto-created container or who receives access to it. The data stream detection flow is not described in Google's help pages reviewed by PPC Land. No source states whether websites should, or can, load the new GTM- ID in place of the original G- or AW- tag, or how the July 9 ID-based restrictions apply to an upgraded stream container.
Key facts
- Source: LinkedIn post by Julius Fedorovicius, founder of analyticsmania.com, published November 16, 2026: https://www.linkedin.com/posts/fedorovicius_your-google-tag-has-been-upgraded-to-a-google-share-7528106898680668160-DFdF/
- Banner text shown in Tag Manager: "Your Google tag has been upgraded to a Tag Manager container"
- Entry point in Google Analytics: "Web stream details", "Google tag" section, "Configure tag settings"
- Example container in the post: "Website", GTM-MVRZP4GH
- Google Help Center page: "Updates to Google tag and Google Tag Manager", dated August 20, 2026 (first published May 20, 2026): https://support.google.com/tagmanager/answer/17079602
- Google Analytics Help Center page: "Configure your Google tag settings": https://support.google.com/analytics/answer/12131703
- Tag Manager release notes: July 9, 2026, "Updates to container behavior for unsupported installation paths"; October 8, 2026, "Standardizing gtag('config') command behavior for Google Tag Manager"; October 12, 2026, "Optimizing Google Tag Manager containers": https://support.google.com/tagmanager/answer/4620708
- Container optimization: optional, started from an optimization banner by users with edit, approve or publish permissions
- Visual tagging: beta, purchase conversions in Google Ads
Timeline
- October 11, 2024 - Google adds Tag Manager diagnostics for tags that stop sending data, including the "No Recent Data" status
- May 3, 2026 - PPC Land maps Google Tag Manager across six domains of complexity
- May 2026 - Google Tag Manager starts appearing inside Google Ads through Data Manager
- May 20, 2026 - Google publishes its plan to upgrade Google tags into full Tag Manager containers, on the day of Google Marketing Live
- July 9, 2026 - Google makes the loading ID decide what a container may run: GTM- unrestricted, G- and AW- limited to Google tags
- August 20, 2026 - The "Updates to Google tag and Google Tag Manager" page is re-dated, with visual tagging in beta
- October 8, 2026 - gtm.js snippets stop waiting for gtag('config') commands, which now surface as gtag.config events
- October 12, 2026 - Google's release note "Optimizing Google Tag Manager containers" lets containers send data directly to Google destinations
- November 16, 2026 - Julius Fedorovicius reports that Google is finishing the upgrade with its latest batch; "Configure tag settings" in a Google Analytics data stream now opens an auto-created GTM container, and the data stream creation flow suggests an existing container
Related PPC Land coverage
- Google Tag Manager and Google tag are merging - what actually changes - The May 31 analysis of Google's plan to turn every Google tag into a Tag Manager container, including the new Settings tab and snippets without a config command.
- Google's visual tagging covers the easy 70 to 80% of cases, Zambon says - How the re-dated August 20 Help Center page framed visual tagging, and where a Tag Manager specialist sees its limits.
- Google forces sites mixing GTM snippets and gtag('config') onto gtag.js - The October 8 change to container initialization and the new gtag.config dataLayer event.
- Google blocks script bypass that hit GTM container restrictions - The July 9 rule that lets the container ID, not the loading path, decide which tags may run.
- Google Tag Manager moves inside Google Ads Data Manager - what changes - The gradual May rollout that put Tag Manager controls inside the Google Ads interface.
- Google Tag Manager in 2026: far more complex than most marketers think - A map of the six domains a Tag Manager setup now spans.
- Google tag gateway now lets advertisers hide GTM container IDs - How server containers can serve GTM- containers under random paths to avoid identification.
- Google Tag Manager: New diagnostics for data gaps and tag placement - The 2024 diagnostics that introduced the "No Recent Data" status now visible on upgraded containers.
Summary
Who: Google, which is converting standalone Google tags into Google Tag Manager containers, and Julius Fedorovicius, founder of analyticsmania.com, who documented the change. Affected are advertisers and site owners who set up Google Analytics or Google Ads with the Google tag rather than Tag Manager.
What: The "Configure tag settings" link in a Google Analytics web data stream now opens a Tag Manager container that Google created for that stream, with a GTM- ID and a banner stating that the Google tag has been upgraded. The data stream creation flow also checks for an existing Tag Manager container on the website and suggests using it. Google says the upgrade does not change in-page tag behavior.
When: Fedorovicius reported the change today, November 16, 2026, describing it as Google finalizing the update with its latest batch. Google first announced the upgrade on May 20, 2026, and its Help Center page is dated August 20, 2026.
Where: Inside Google Analytics and Google Tag Manager, on web data streams; Google has given no regional limits or schedule for the upgrade.
Why: Google says merging the Google tag into Tag Manager gives Google tag users Tag Manager features such as debugging and version control, and an October 12 release note says the separate settings and permissions of the old Google tag made troubleshooting difficult. The change also moves tag settings, permissions and ownership questions into a container that many account owners did not create.
Discussion