Google Made Your GA4 Tag a GTM Container, and It Didn't Ask Who Should Publish
Google has started converting the standalone Google tag behind GA4 web data streams into full Google Tag Manager containers, with a new batch reported by Julius Fedorovicius on November 16, 2026. In-page tag behavior does not change, but each upgraded stream now has an auto-created container with its own users, versions, and publish rights. Audit who can publish it before your Black Friday code freeze.
The visible change is small. In GA4, you go to a web stream, click "Configure tag settings" under the Google tag section, and instead of the old settings panel you land in a GTM container that Google made for you. PPC Land's write-up shows the example: a container called "Website," ID GTM-MVRZP4GH, with Workspace, Versions and Admin tabs and a banner saying the tag was upgraded. No email, no opt-in screen that anyone has documented.
On paper, that sounds like an upgrade. And honestly, for most sites it probably is. Workspaces, preview mode and version history are things a lot of GA4-only sites never had. The part that bugs me is that a new place to publish code just showed up in your stack eleven days before Black Friday, and nobody on your team decided who gets the keys.
Google says nothing changes on the page (and that's probably true)
Google's Help Center page on the Google tag and Tag Manager updates is pretty direct: "This upgrade will not change the in-page behavior of the Google tags." Your existing tags keep running, each Google destination keeps its own setup and automation triggers, and the settings you used to edit in GA4 move into a Settings tab inside the container.
That matters, and I don't want to oversell the risk here. If you do nothing, your conversion tracking on November 27 should look the same as it does today. The press release version of this story is "you got better tooling for free," and that's mostly accurate.
There are two separate things happening, though, and people keep blurring them:
- The upgrade. Google converts the stream's Google tag into a container. Neither Google's page nor PPC Land's reporting describes an opt-out for this part, and there's no published schedule or batch size.
- The optimization. A banner offers to switch existing GTM containers so they send data straight to Google destinations instead of loading gtag.js as a separate library. Google says "no changes will be made automatically" for this step, and only users with edit, approve or publish permissions can start it.
The first one happens to you. The second one is a button somebody on your team might click on a Tuesday afternoon because the banner looked official.
The access question nobody has answered yet
This is where it gets a bit messy. PPC Land notes that neither Google nor Fedorovicius says which Tag Manager account holds these auto-created containers or who receives access to them. Google's Help Center does say that when containers get linked to Google destination accounts, "Read" access is granted by default and can be changed in user management. That's about account links, though, and it doesn't quite answer how humans get added to a container Google created on its own.
Think of it like your landlord installing a second front door. It's a nicer door. It probably locks fine. But you'd still want to know who got a copy of the key before you leave for the holidays.
GA4 property access tends to be loose in a lot of companies. Former agency staff, a freelancer from a 2024 site migration, three people who left in the last reorg. If container permissions end up mirroring or inheriting any of that (and again, nobody has confirmed how it works), the set of people who can publish to your site's tagging layer just grew without a single approval.
Publish rights on a GTM container are a big deal. Anyone with them can push a tag that fires on every page. That's why careful GTM teams limit publish to two or three named people and route everything else through workspaces.
The G- versus GTM- ID trap
The other wrinkle is which ID actually loads the container. Back in July, Google changed how restrictions work so that the loading ID, not the loading path, decides what a container can run. Per PPC Land's coverage of the July 9 release note, containers loaded with a G- (Analytics) or AW- (Google Ads) ID can only run Google-provided tags and variables. Custom HTML, third-party pixels, anything not made by Google: blocked. GTM- containers have no such restriction.
So your upgraded container has a GTM- ID, but your site is almost certainly still loading Google's tag through the G- ID in your gtag snippet. If I'm reading the July rule correctly, that seems to mean anything non-Google you add inside that container won't run. Someone sees the shiny new container, drops a Meta pixel or a TikTok tag into it, publishes, and nothing fires. No error in the interface that anyone has reported. Just missing data.
The obvious "fix" is swapping your site snippet to the new GTM- ID. Whether you should do that at all is one of the open questions PPC Land flagged, and I would not be the person testing it in the last two weeks of November.
This also stacks on top of the October change. Since October 8, gtm.js snippets no longer wait for gtag('config') calls, and those calls now show up in the dataLayer as gtag.config events. We covered how that makes wildcard triggers double-fire. Any site that ends up running both an existing GTM container and a newly upgraded one, without someone mapping out what loads where, is a good candidate for that exact problem.
A 20-minute audit that fits before code freeze
None of this needs a migration project. It needs one person and about 20 minutes per GA4 property. This is the order I'd go in:
- Check each web stream. In GA4 Admin, open Data streams, pick each web stream, and click Configure tag settings. If you land in a container, write down its GTM- ID and which Tag Manager account it sits in. Google's Analytics help page on Google tag settings is the starting point if your UI looks different.
- Open User Management on that container. Count everyone with Publish. Your benchmark: two or three named people, all current employees or contracted partners. Anyone else gets downgraded to Read or removed. If you can't see the container's users at all, that tells you something about ownership, and it's worth a support ticket now rather than in December.
- Do not click the optimization banner yet. It's optional. Fedorovicius recommends testing it in a workspace before publishing anyway. Put it on the January list.
- Leave your site snippet alone. Keep loading with the ID you load today until Google clarifies how the July restrictions apply to upgraded containers.
- Write one rule in your team channel. Something like: "No tags in the new GA4 container until January. Non-Google pixels go in our existing GTM container only." That one sentence prevents the silent-pixel failure above.
- Name every version. Any publish to the new container between now and December 2 gets a version name and a reason. If conversions look weird on Cyber Monday, you'll want that trail.
If you already run a proper GTM setup with a GTM- snippet, most of this is a five-minute check. The sites I'd worry about are the GA4-only ones, which are often small ecommerce brands with the least tagging help and the most Black Friday revenue at stake.
Google is slowly folding everything into GTM
Zooming out a bit. This is one more step in a plan Google announced in May, when it said the Google tag and Tag Manager would merge. PPC Land's breakdown of that merger laid out the end state pretty clearly: one container, one snippet, Google destinations running through it. Tag Manager has also shown up inside the Google Ads interface through Data Manager, and the sGTM full-IP change in January feels like part of the same drift.
I think that direction is fine, mostly. Fewer libraries, one place to debug. What I don't love is the rollout style: auto-created containers, no published schedule, the access model undocumented, and an open question about which ID to load. And to be fair, Google's tagging changes have often landed like this. It's just that this one lands right before the busiest two weeks in ecommerce.
My guess: by the end of Q1 2027, at least half of GA4-only sites will have an upgraded container, and Google will start nudging people to load the GTM- ID directly. When that happens, the sites that already cleaned up container permissions will have a boring migration. Everyone else will be finding out who had publish rights the hard way.
For this week, though, it really is just a door count. Find the container, see who has a key, and quietly take the extra copies back.