According to DEV Community, Google posted a Tag Manager release note on 17 November 2026. Every Google tag will now become 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 described as common on small business sites. It uses a Google tag ID starting with G- (Analytics), AW- (Google Ads) or DC. The ID is loaded through the Tag Manager snippet (gtm.js) and followed by a gtag('config') call. The article says this usually happens when someone copies the Tag Manager snippet and puts the wrong ID into it.
The setup has worked so far because gtm.js waited for the config command. Google says Tag Manager snippets will stop recognizing or waiting for it. Affected sites "may experience unexpected changes to their tag behavior."
For correct installs, Google says in-page behavior stays the same. Sites that only use the Google tag gain Tag Manager features: tagging through a user interface, debug mode and version history. New snippets will all be identical and will drop the config command. Google recommends the standard Initialization trigger instead.
Why it matters
The risk lies in measurement. The article points out that Google Ads bidding learns from conversions sent by this tag. If the tag behaves differently, campaigns could keep spending while learning from incomplete data. The author says nobody may notice until a report looks wrong in February.
If you build or maintain sites for others, a copied snippet from years ago could be sitting on pages you have forgotten about. A change in January is easy to miss, so checking now is cheaper than untangling bad data later.
Source: DEV Community. This brief summarises their reporting; read the original for the full detail.