On November 17, 2026, Google announced that every Google tag is becoming a Google Tag Manager container. If your website has Google Analytics or Google Ads tracking that someone installed years ago, you probably have a Google tag on it. Here is what the change means for a local service business, what is not changing, and how to find out whether you need to do anything before January 2027.
Key takeaways
- Google says the upgrade does not change how Google tags behave on your pages.
- Sites with what Google calls an “unsupported installation” get the upgrade in January 2027, and Google advises adjusting the setup before then.
- Google’s help page describes the unsupported setup: a Google tag ID starting with G-, AW- or DC- loaded through the Tag Manager snippet (gtm.js).
- Google says users on affected containers received an email notification, so check the inbox tied to your Google accounts.
- Most sites that use the standard Google tag snippet do not need to change anything for this announcement.
First, two quick definitions
Google tag: a small piece of code (often called gtag.js) that sends visits and conversions from your website to Google Analytics 4 or Google Ads.
Google Tag Manager: a Google tool for managing tracking codes from one dashboard. Each website setup inside it is called a container.
What is changing
Google’s Tag Manager release notes, dated November 17, 2026, say Google is bringing Tag Manager’s capabilities to the Google tag. With the upgrade, each Google tag becomes a Tag Manager container.
In practice, Google says websites that only use the Google tag will be able to use Tag Manager features such as its interface for setting up tags, debugging and version control. It is an option you gain, not a new tool you are forced to learn.
Three smaller changes are in the same note:
- All new installation snippets will be the same, and they will not include the gtag config command (the gtag(‘config’, …) line that names your tag ID in the snippet). Google recommends handling that through Tag Manager’s standard Initialization trigger instead.
- Each Google destination (each Google product your tag sends data to) will have its own tag, which Google says preserves your existing setup and triggers.
- Access to data in Tag Assistant (Google’s tag checking tool) will follow the container permissions you use in Tag Manager.
What is not changing
Google is direct about this. In its words, the upgrade “won’t change the in-page behavior of the Google tags.” If your site uses the standard Google tag snippet, your tracking is not expected to break because of this announcement.
Your Google Analytics reports and your Google Ads conversion tracking keep coming from the same tag. Google says your existing setup and triggers are preserved.
What Google means by an “unsupported installation”
The release note links “unsupported installation” to a Google help page titled “Set up your Google tag installation correctly for gtag.js.” That page describes one setup: some websites deploy a Google tag ID that starts with G-, AW- or DC- using the Google Tag Manager snippet path, called gtm.js, instead of the Google tag snippet.
Google calls this an unsupported implementation and warns that tag behavior on those sites may change unexpectedly. The same page says Tag Manager snippets will soon stop recognizing or waiting for gtag config commands.
That help page is the only description of an unsupported setup we found on Google’s pages. Google has not published a longer list, so if your setup looks unusual in some other way, ask whoever manages your site to check it against Google’s help page.
How to check which setup you have
You do not need to read code to get an answer, but it helps to know what to look for. Google’s help page shows both versions side by side:
- Supported: the code loads from an address containing googletagmanager.com/gtag/js?id= followed by your tag ID.
- Unsupported: a G-, AW- or DC- ID is loaded through the Tag Manager snippet, gtm.js, often with a separate gtag config line.
Google gives two ways to confirm the result. In Tag Assistant, add your domain and check the “Google tags found” header for your tag ID. Or, in the Chrome browser’s developer tools, open the Network tab and check that requests go to googletagmanager.com/gtag/js rather than /gtm.js.
If a website builder or plugin added your tag, ask the person who manages the site which method it uses.
What to do before January 2027
- Check your email. Google says users on containers with the unsupported setup received an email notification. Search the inboxes tied to your Google Analytics, Google Ads and Tag Manager accounts.
- Find out how your tag is installed. Use Tag Assistant, or ask your web person whether the site loads gtag/js or gtm.js with a G-, AW- or DC- ID.
- If you only use Google tracking, switch to the standard Google tag. Google’s fix is to copy your Google tag ID, paste it into the gtag.js snippet, remove the gtm.js snippet and any standalone gtag config lines tied to it, and place the new snippet right after the opening head tag on every page.
- If you use Tag Manager for other tracking, keep it. Google says to keep your main Tag Manager snippet and replace the G-, AW- or DC- ID in it with your GTM- container ID.
- Test after any change. Run Tag Assistant again and confirm your tag ID shows under “Google tags found” before you call it done.
What to ask whoever manages your website
- Is our Google tag loaded through gtag/js or through gtm.js?
- Does our gtm.js snippet use a G-, AW- or DC- ID instead of a GTM- ID?
- Did anyone on our Google accounts receive Google’s email about an unsupported implementation?
- Who has access to our Tag Manager container, since Tag Assistant data access will follow those permissions?
Frequently asked questions
Will this Google tag change break my tracking?
Google says the upgrade does not change how Google tags behave on your pages. Sites with an unsupported installation are the exception Google flags: their tag behavior may change unexpectedly.
Do I need to do anything before January 2027?
Only if your site has an unsupported installation. Those sites receive the upgrade in January 2027, and Google advises adjusting the setup before then.
What is an unsupported installation?
Google’s help page describes it as a Google tag ID starting with G-, AW- or DC- deployed through the Tag Manager snippet (gtm.js). Google has not published a longer list.
How do I check my setup?
Add your domain in Tag Assistant and look for your tag ID under “Google tags found,” or check that your site loads googletagmanager.com/gtag/js rather than /gtm.js.
Related reading: how we handle SEO and reporting for local businesses, and our earlier note on Local Services Ads moving into Google Ads. Sources: Google’s Tag Manager release notes (November 17, 2026 entry) and its help page on setting up the Google tag correctly, both read on November 18, 2026.
Not sure how your Google tag is installed? Bright Marketing Solutions, with offices in Brooklyn, NY and Dumont, NJ, can check your site’s tag setup.