The ID a container is loaded with now decides what it may run
Google changed how containers loaded through unsupported paths behave. A container loaded with a GTM- ID is not restricted; loaded with a product ID such as G- or AW-, it only permits tags and variables provided by Google.
For debugging
A Custom HTML tag or a community template that "stopped firing" may simply be in a container the page now loads by a G- ID. Check which ID the gtm.js or gtag/js request actually carries before looking at triggers.
Interface
A redesigned Overview page
The Overview page in Tag Manager has a streamlined layout meant to help both new and experienced users find their way around a setup.
For debugging
Interface only. Nothing about what a container publishes or sends changes.
Server-side
Server-to-server conversions recover what they undercounted
Server-to-server setups now pair server-side data with browser signals such as cookies when a GCLID is present, for more accurate Floodlight attribution.
For debugging
The browser half still matters in a server-side setup. If the GCLID never reached a cookie, there is nothing to pair — follow the chain from the ad click to the conversion before blaming the server.
Google tag gateway
Google tag gateway reaches more CDNs
Across the first half of 2026 the gateway gained guided or automatic setups for Akamai (29 January), Akamai and Fastly with automatic zone detection (14 May), Google Cloud’s load balancer — beta on 5 January, generally available on 1 June — and Amazon CloudFront through Tag Assistant (3 June).
For debugging
With the gateway, Google’s scripts and hits are served from a path on the site’s own domain. A tool that recognises Google by hostname sees nothing; matching the request by its path still works. How to debug the gateway.
Server-side
Server-side GTM and Google Ads-linked GA4 properties
For server-side customers whose GA4 property is linked to Google Ads, conversion tracking and attribution improve through parallel browser signals when Google Signals is enabled.
For debugging
In such a setup, Google requests from the browser running alongside your server-side hits are part of the design, not necessarily a leak — check whether Signals is on before treating them as one.
Google Ads
Google Ads collects more website events on its own
Google Ads now automatically collects a broader range of website event data, with less manual configuration from advertisers.
For debugging
Expect Google Ads requests for events nobody configured in the container. Before calling one a duplicate or a stray, check whether the Google tag sent it by itself.
Web container
Built-in variables for Client ID, Session ID and Session Number
Three new built-in variables in the Utilities category give an officially supported way to read these values in Tag Manager.
For debugging
The cookie-parsing Custom JavaScript that used to do this can go. The values should match the cid, sid and sct on the GA4 hits the same page sends — if they do not, the variable and the hit are reading different streams.
Google tag gateway
Tag Manager shows whether the gateway is active
Tag Manager now displays the active status of a Google tag gateway setup however it was configured — by hand or through a CDN such as Cloudflare.
For debugging
A status in the interface says the gateway is configured. Whether today’s hits went through it is still read from the requests: their host should be the site’s own.
Templates
Custom templates can read client and session IDs
The readAnalyticsStorage sandbox API lets custom templates read the client and session IDs safely, without reverse-engineering the cookie format.
For debugging
A template that needs these IDs now declares a permission for it, which shows in the published container alongside its other permissions.
Server-side
Server-side GTM serves gtm.js and gtag.js through the web container client
All Google scripts, gtag.js and gtm.js included, can be served with the web container client; the Google Analytics client no longer serves Google scripts as dependencies.
For debugging
On such a site the container request itself comes from the site’s own domain. The ID is still in the URL, so the container can still be identified and read.
Google tag gateway
First-party mode becomes Google tag gateway for advertisers
First-party mode was renamed Google tag gateway for advertisers and made available to everyone, covering client-side and server-side tags, with a choice of domain names.
For debugging
Articles and settings from before May 2025 call it first-party mode. It is the same thing.
Google Ads
Containers with Google Ads and Floodlight tags load a Google tag first
Announced on 10 March 2025 and effective from 10 April: containers holding Google Ads or Floodlight tags automatically load a Google tag before sending events.
For debugging
An extra gtag/js request for the Ads ID, arriving before the first conversion, is expected. It is not a second installation.
Server-side
The Google tag sends to server-side GTM through a service worker
Where a service worker is available, the Google tag now uses it to send data to server-side Tag Manager, for performance and measurement reliability.
For debugging
Some hits to your server container may start from a service worker rather than the page. In DevTools, look at a request’s initiator before deciding it came from a tag on the page.
Try it on your own site
Tag Master is free, needs no account, and collects no data.