Google Tag and Tag Manager Are Merging: A Tracking Check for Multi-Location Brands
Google is bringing Tag Manager features to every Google tag. Most sites keep working as they are, and sites with an unsupported setup get upgraded in January 2027. Here is the quick check.
· 4 min read

The short answer
Google is bringing Google Tag Manager's capabilities to the Google tag. With this update, every Google tag becomes a Tag Manager container, so a site that runs only the Google tag gains Tag Manager's interface-driven tagging, debugging and version control.
Google says the upgrade keeps the in-page behavior of your Google tags the same. Each Google destination keeps its own tag, along with your existing setup and the triggers behind automated events. Most advertisers simply gain new options.
The one group with homework: sites running an unsupported installation. Google upgrades those in January 2027 and advises adjusting the setup before then.
What is changing
Google listed the changes in its Tag Manager release notes on November 17, 2026.
| Change | What it means for you |
| Every Google tag becomes a Tag Manager container | Tag Manager features open up inside the Google tag you already have |
| Tag Manager tools for Google tag sites | Interface-driven tagging, debugging and version control |
| One snippet format | All new deployment snippets look the same |
| New snippets drop the gtag config command | Google recommends Tag Manager's Initialization trigger, which can also wait for the config command to keep a legacy setup |
| Unified permissions | Tag Manager container permissions now control access to Tag Assistant data |
Search Engine Land covered the update on November 18.
Who needs to act before January 2027
Google's help page defines an unsupported installation as a site that loads a Google tag ID starting with G-, AW- or DC- through the Tag Manager snippet (gtm.js) and then relies on gtag('config') commands to set up the tag. Google says containers with this setup received an email notice.
Two clean setups keep you in good shape:
- Google tag only. Use the standard Google tag (gtag.js) snippet for your G- or AW- ID, placed right after the opening head tag on every page.
- Tag Manager for everything. Keep your Tag Manager snippet with your GTM- container ID, deploy the Google tag inside Tag Manager, and manage settings in the Tag Manager interface.
Why this matters for dental groups, childcare brands and clinics
Multi-location brands often build their sites over years, with different developers, landing page tools and booking widgets for different offices or centers. That is exactly how mixed tag setups happen. One location page may run a clean Google tag while another loads the same Google Ads ID through an older Tag Manager snippet.
Your Google Ads bidding learns from the conversions those tags send. Form fills, calls from the site and tour or appointment requests all depend on them. A quick check now keeps that data steady through the January upgrade, and keeps each location's lead counts accurate. Our guide to conversion tracking for lead generation covers which actions to count.
The unified permissions are worth a look too. If an outside developer or a past agency still has container access, that access now also reaches Tag Assistant data. Review who has access while you are in there.
A simple check for every site you run
- 01Open your inbox. Search for Google's notice about unsupported installations, and note every container it names.
- 02List every domain and landing page tool. Include main sites, location pages, booking pages and any landing page builder.
- 03Scan each site in Tag Assistant. Add the domain, connect, and confirm your tag ID shows a green or blue status.
- 04Check the Network tab. In Chrome Developer Tools, confirm Google Ads requests go to googletagmanager.com/gtag/js and googleadservices.com.
- 05Fix any unsupported setup. Switch to the standard Google tag snippet, or move the Google tag inside your Tag Manager container.
- 06Review container access. Keep current team members and partners, and remove everyone else.
- 07Confirm conversions after any change. Submit a test lead per location, then watch conversions in Google Ads for a few days. Our post on primary vs. secondary conversions shows which ones feed bidding.
Running server-side tagging as well? Our post on Google Ads server-side tagging and IP addresses covers the other tagging change landing in January 2027.
How SalesX handles tracking changes
SalesX runs Google Ads only, for U.S. advertisers spending $50k to $500k+ per month, and much of that work is multi-location lead generation. We audit tags site by site, keep one clean setup per domain, and confirm every location's leads reach Google Ads before and after each platform change. See our multi-location Google Ads services for how we structure those accounts.
A multi-location dental group (DSO) we partner with under NDA saw 40–50% more leads at the same ad spend within 60 days, and 80% of those leads became new patient visits.
Want a senior strategist to review your tags and conversion tracking across every location? Request a free X-Audit. It is built for U.S. advertisers spending $50k+ per month, and the analysis typically takes three to five working days after access is approved.
The bottom line
Every Google tag is becoming a Tag Manager container, with more tools and the same in-page behavior. Check each site for the unsupported gtm.js plus gtag('config') setup, fix it before January 2027, and confirm your leads still reach Google Ads.
Sources and further reading
- Google Tag Manager Help, Release notes (November 17, 2026: Google tag and Google Tag Manager unification)
- Google Tag Manager Help, Set up your Google tag installation correctly for gtag.js
- Search Engine Land, Google unifies Google tag and Tag Manager with new tagging and debugging features
Related reading
FAQ
- What is the Google tag and Tag Manager unification?
- Google is turning every Google tag into a Tag Manager container. Sites that use only the Google tag gain Tag Manager features such as interface-driven tagging, debugging and version control.
- Will the update change how my Google tags work?
- Google says the upgrade keeps the in-page behavior of Google tags the same. Each Google destination keeps its own tag, along with your existing setup and the triggers behind automated events.
- What is an unsupported Google tag installation?
- Google defines it as loading a Google tag ID that starts with G-, AW- or DC- through the Tag Manager snippet (gtm.js) and relying on gtag('config') commands to set it up. Google upgrades these installations in January 2027.
- How do I check my Google tag setup?
- Scan your site in Google Tag Assistant and confirm your tag ID shows a green or blue status. In Chrome Developer Tools, confirm requests go to googletagmanager.com/gtag/js, plus googleadservices.com for Google Ads.
- Who can see Tag Assistant data after the update?
- Access to Tag Assistant data is now managed through your Google Tag Manager container permissions, the same ones you use in Tag Manager today.
Next step
Want this analysis run on your account?
SalesX audits Google Ads programs spending $50k–$500k+ per month and returns a prioritized roadmap, not a checklist.
Request a Free X-Audit


