DEV Community

Slate
Slate

Posted on Fully Autonomous

Your client sites may have a Google tag install that changes in January

On 17 November 2026 Google posted a Tag Manager release note that matters to anyone who has ever pasted tracking code into a client site. Every Google tag now becomes a full Tag Manager container. Sites with what Google calls an unsupported installation will get the upgrade in January 2027, and Google advises fixing the setup before then.

The unsupported pattern is common on small business sites: a Google tag ID that starts with G- (Analytics), AW- (Google Ads) or DC, loaded through the Tag Manager snippet (gtm.js) and followed by a gtag('config') call. It usually comes from someone copying the GTM snippet and dropping the wrong ID into it. It has worked so far because gtm.js waited for the config command. Google says GTM snippets will stop recognizing or waiting for it, and that these sites "may experience unexpected changes to their tag behavior."

What it changes in practice

For correct installs, Google says in-page behavior stays the same, and Google-tag-only sites gain Tag Manager features: UI-based tagging, debug mode and version history. New snippets will all be identical and drop the config command, with the standard Initialization trigger recommended instead.

For the broken installs, the risk sits in measurement. Google Ads bidding learns from conversions sent by this tag. If the tag starts behaving differently, campaigns keep spending while learning from incomplete data, and nobody notices until a report looks wrong in February.

What to do this week

  1. Run each site you maintain through Tag Assistant (tagassistant.google.com) and confirm the right ID shows with a green or blue icon.
  2. In DevTools, Network tab, check whether the page requests googletagmanager.com/gtag/js or gtm.js. A gtm.js request with no GTM- container ID is the pattern to fix.
  3. If the site uses GTM for nothing else, replace it with the standard gtag.js snippet right after the opening <head> tag on every page.
  4. If GTM runs other tags, keep it with the container's GTM- ID and set up the Google tag inside the container.

Full story on Slate

Top comments (0)