What changed on October 8
Google made a small but sharp adjustment to Google Tag Manager. From October 8, 2026, every gtm.js container snippet initializes on container load, regardless of any gtag(‘config’) commands sitting elsewhere on the page. Those config commands now appear in the dataLayer as a visible event called gtag.config.
For most marketers, this is invisible. For teams running broad wildcard triggers, it may quietly add more hits.
Google’s release note framed the update as “standardizing the behavior of tagging snippets to ensure consistency, reliability, and high performance.” The practical shift is that the old pause-and-wait behavior is gone.
Two setups that need attention
The first is the unsupported hybrid: a GTM snippet loaded with a product ID such as G-, AW- or DC-, plus a standalone gtag(‘config’) line and no gtag.js loader. Google says those pages may see unexpected tag behavior and has emailed some affected container owners.
If you run that setup, the fix is to move to the full Google tag snippet, or keep GTM for third-party tags and deploy the Google tag inside the container with your GTM- ID.
The second group is bigger and less obvious: containers that use a .* wildcard on custom event triggers. Now every wildcard-triggered tag can fire once more on pages that also run gtag(‘config’) — including the standard, correctly installed gtag.js pattern.
“The thing you need to watch for is that there’s a new Data Layer event in the timeline: gtag.config,” said Simo Ahava, co-founder at Simmer.
What to do before the next report
This is not a theoretical edge case. One extra event can mean duplicate conversion hits, inflated analytics, extra pixels, or noisy debugging logs.
- Audit wildcard triggers: find every custom event trigger using .* and decide whether it should fire on gtag.config.
- Filter or annotate: exclude gtag.config at the trigger level, or account for it in your annotation logs.
- Check your snippet pattern: if you are pairing a gtm.js loader with a loose config command, migrate to the full gtag.js snippet.
- Verify after the change: use Tag Assistant and the Chrome Network tab to confirm requests hit /gtag/js rather than /gtm.js.
Why this update is groundwork
Google has been tightening how its tagging code can be installed. In July 2026 it stopped letting a container’s loading path determine whether third-party tags could run. In May 2026 it laid out plans to merge Google Tag Manager and the Google tag, with new snippets eventually carrying no gtag config command.
This October change removes one more legacy behavior. If you standardise your tagging now, you will be ahead of the next migration instead of chasing it after the fact.
Source: PPC Land
