Google tags become containers, and 9 of 24 stores get two
Published 2026-11-20 ·
primary source
What it means
Nothing fires differently on the day, but tagging now has two homes: the Google tag's own container, limited to Google tags, and the GTM container beside it on sites that run both. Decide which one holds each Google Ads and GA4 tag before someone builds the same conversion in both, move whatever your gtag('config') lines set into initialization triggers before you copy a new snippet, and check who loses Tag Assistant access when container permissions take over.
Google is turning every Google tag into a Tag Manager container. The change is in the Tag Manager release notes dated 17 November, and Google says the tags will behave the same on the page. What changes is where a tag can be edited, and who can see it. We loaded 50 store homepages today. On 9 of the 24 where we could see Google’s tags, the store already runs a Tag Manager container and a Google tag installed outside it, so after the upgrade those pages carry two containers.
What Google changed
The note makes four changes:
- Every Google tag becomes a container. A site that only has the Google tag (gtag.js) gets Tag Manager’s interface, triggers, debugging and version control. Each Google destination, such as a GA4 stream or a Google Ads account, gets its own tag in that container.
- The page behaviour stays the same. Google says the upgrade “won’t change the in-page behavior” of Google tags, and keeps the existing triggers for automation events.
- New snippets have no config line. Every new snippet is the same and leaves out
gtag('config', …). Google says to set up initialization behaviour with Tag Manager’s initialization triggers. The Initialization trigger can also make the tag wait for a config command, if you keep the old code. - Tag Manager permissions apply. Access to data in Tag Assistant goes through container permissions.
Sites with an unsupported installation
get the upgrade in January 2027. Unsupported means a G-, AW- or DC ID loaded through the
Tag Manager snippet (gtm.js) together with gtag('config') commands. The note gives no date for
everyone else.
One limit matters for what follows. A container loaded with a G- or AW- ID
can run only Google tags. Custom HTML
and third-party pixels need a GTM- container. So the Google tag’s new container is a second place
for Google Ads and GA4 tags, and not a replacement for Tag Manager.
What we checked
We loaded the homepages of 50 US retailers and direct-to-consumer brands in Chromium today, waited
eight seconds, and logged every request for gtm.js and gtag/js. We also read each page’s
dataLayer for gtag('config') commands. 20 sites blocked the headless browser or timed out (403,
429, 502 or no response). 6 loaded but made no Google tag request in the eight seconds. That leaves
24.
| Setup on the homepage | Sites | gtag('config') in the dataLayer |
|---|---|---|
| Tag Manager container only | 8 | 0 of 8 |
| Tag Manager container and a Google tag loaded outside it | 9 | 9 of 9 |
| Google tag only, no Tag Manager | 7 | 7 of 7 |
G- or AW- ID through gtm.js (unsupported, January 2027) | 0 | – |
We counted a Google tag as “outside the container” when the page requested gtag/js without the
cx=c parameter. The tags that a container loaded in our logs carried that parameter. That is how
the requests looked, not a rule Google documents.
Three more things showed up:
- No site used the unsupported setup. The January 2027 group is not visible in a sample of
large stores. It is more likely to be hand-built sites where someone pasted a
G-ID into a Tag Manager snippet. - 16 sites set their Google tags with
gtag('config'). That is every site with a Google tag outside a container. These are the lines the new snippet leaves out. - A dead tag is still configured. Home Depot’s homepage ran
gtag('config')for a Universal Analytics ID,UA-32593878-1, and loaded gtag.js for it. Standard Universal Analytics stopped processing hits on 1 July 2023. One store with two Tag Manager containers, Allbirds, would get a third.
We did not see inside any container, so we cannot say which tags each site keeps where. We also could not test the upgrade itself. None of these sites had it yet, as far as the requests showed.
The read: two places for one conversion
On day one, nothing in the numbers moves. Google says page behaviour stays the same, so a report that steps up on the upgrade date has a cause outside this change.
The risk comes later, from edits. On the 9 sites that run both, a Google Ads conversion tag can
now be added in either container. The Tag Manager team audits the GTM- container. The paid media
team opens the Google tag in Google Ads and finds a container with triggers. If both build a purchase
tag, the purchase fires twice. Google Ads drops the second one as a duplicate only when both send
the same transaction ID for the same conversion action. Smart Bidding then learns from orders that did not
happen. The 8 October change showed how
quietly an extra event reaches a conversion tag. A second container is a bigger version of the same
problem.
The config line holds settings. On the 16 sites with config commands, those lines can carry
send_page_view, cookie settings, user IDs and custom parameters. Copy the new snippet into a new
theme or a Black Friday landing page and those settings are gone, unless they live in the
Initialization trigger first. A site that sets send_page_view: false and sends its own page views
could start counting two per page, the same kind of step up as
Tag Manager’s bfcache change on 9 November.
Access moves to Tag Manager. Tag Assistant data now follows container permissions. An agency that debugs Google Ads tags through its Google Ads access may lose that view until someone grants it on the container.
What to do
- Pick one home for each Google tag. On a site that runs Tag Manager, decide whether Google Ads
and GA4 tags live in the
GTM-container or the Google tag’s container, and write it down. Third- party tags can only go in theGTM-one. - List what your
gtag('config')lines set before you copy a new snippet anywhere. Move each parameter into the Initialization trigger, or set the trigger to wait for the config command. - Check Tag Assistant access for agencies and anyone who debugs tags without Tag Manager rights.
- Annotate the date your Google tag shows as a container. Google gives none, so watch the tag settings in Google Ads and GA4.
- Remove dead IDs. A
UA-config line still loads a script and sends nothing anyone can read.
Both containers still run in the browser, so both still miss what the browser never sees: blocked scripts, closed tabs and orders that close offline. Where should the purchase event start, if not in a tag?
Sources
- Google Tag Manager release notes, 17 November 2026, 'Google tag and Google Tag Manager unification': Google is bringing all the capabilities of Tag Manager to the Google tag, so that each Google tag becomes a Tag Manager container, and websites that only use the Google tag gain Tag Manager's interface-driven tagging features, debugging and version control.
verified 2026-11-20 - The same release note says the upgrade won't change the in-page behavior of Google tags, and that each Google destination will have its own tag, preserving the existing setup and triggers for automation events.
verified 2026-11-20 - The same release note says all new deployment snippets will be the same and won't have the gtag config command; it recommends configuring initialization behavior with the standard Tag Manager initialization triggers, and says the Initialization trigger can configure the tag to wait for the config command to preserve a legacy setup.
verified 2026-11-20 - The same release note says Tag Manager permission settings will apply across the board, so access to data in Tag Assistant will be managed through Tag Manager container permissions.
verified 2026-11-20 - The same release note says sites with an unsupported installation will receive the upgrade in January 2027 and are advised to adjust their setup before then. It gives no date for other installations.
verified 2026-11-20 - Google's help page 'Set up your Google tag installation correctly for gtag.js' defines the unsupported implementation as a Google tag ID that does not start with GTM-, such as G-, AW- or DC, loaded through a Tag Manager snippet path (gtm.js) with gtag('config') commands, and says users on containers with it received an email notification.
verified 2026-11-20 - Google's help page 'Manage tagging behavior using the container ID' says a container whose ID starts with GTM- allows all tag types, including custom HTML and JavaScript tags, while a container whose ID starts with a product prefix such as G- or AW- is limited to Google tags and can send data only to Google services, whatever the installation path.
verified 2026-11-20 - Google Tag Manager release notes, 8 October 2026: gtag('config') commands surface in the dataLayer as visible gtag.config events, which may cause tags on wildcard custom event triggers to fire.
verified 2026-11-20 - Google's Universal Analytics sunset page says standard Universal Analytics properties stopped processing hits starting 1 July 2023, and that from the week of 1 July 2024 there is no access to any Universal Analytics data.
verified 2026-11-20 - Google Ads help page 'Use a transaction ID to minimize duplicate conversions': if there are two conversions for the same conversion action with the same transaction ID, Google Ads treats the second as a duplicate and does not count it; a transaction ID does not resolve duplicate view-through conversions.
verified 2026-11-20