On August 20, 2026, Google announced a major update to Google Tag Manager (GTM) and the Google tag (gtag.js). It is one of the biggest changes to Google’s tagging tools in years, and it has been rolling out in stages ever since.
In short, Google is bringing its two tagging products together. Until now, you either added the Google tag directly to your site or managed your tags in GTM. Going forward, every Google tag becomes a full GTM container, so everyone works in the same tool.
The update has three parts:
- A cleaner GTM interface, with a new Settings area and the more technical features tucked into an Advanced tab.
- Unification of the Google tag and GTM, which also lets GTM send data to Google products without loading extra scripts.
- Visual tagging, which lets you set up events and conversions by clicking on elements of your website instead of writing code.
The good news first: nothing breaks overnight, and the biggest change is opt-in. Below we explain what is changing, what is already live, and what you should check before you act.
What the update means
The update changes how your tags are delivered and managed, not what data they collect. Here is what each part does in practice.
Every Google tag becomes a full GTM container
If your site uses only the Google tag (for example a GA4 G- ID or a Google Ads AW- ID added to your site), that tag is being upgraded to a full Tag Manager container. You will be able to manage it in the GTM interface and use GTM features such as preview and debugging, version history, and interface-based tags and triggers.
Google states the upgrade will not change how your existing tags behave on your pages. Each Google product you send data to (Google calls these destinations, such as a GA4 property or a Google Ads account) keeps its own tag, so your existing setup and automatic events stay in place.
The container ID now decides what can run
Since July 9, 2026, the prefix of your ID determines what a container is allowed to do, even when it is loaded in a non-standard way:
- A GTM- ID gives you the full toolkit, including third-party tags (such as Meta or LinkedIn) and custom HTML tags.
- A product ID like G- or AW- limits the container to Google tags that send data to Google products only.
The G- mode is useful if your organization wants tighter control over what can run on the site. But if your marketing team relies on non-Google tags, make sure they load through a GTM- ID. Installations using Google’s standard snippets are unaffected, and Google says it has emailed administrators of significantly affected containers.
New installation snippets
Google is also changing the installation code. All new snippets will be identical and will no longer contain the gtag(‘config’, …) line you may recognize from older setups. Instead, Google recommends controlling start-up behavior with a new initialization trigger in GTM (gtm init). It can be set to wait for an old-style config command if you need to keep a legacy setup working.
The new snippet only affects new installations. However, since October 8, 2026, all GTM containers initialize on page load regardless of gtag(‘config’) commands. Those commands now appear in the data layer as a gtag.config event. More on what that means for you below.
Faster data sending
Today, when GTM fires a Google Analytics or Google Ads tag, it loads an extra script (gtag.js) in the background for each Google product. A container running GA4, Google Ads and Floodlight therefore loads three extra libraries on top of GTM itself.
After you optimize your container, GTM sends data directly to each Google destination from the single container script. Fewer scripts means less to download and quicker data sending. Google hasn’t published a speed figure, so measure your own pages before and after to see the real gain.
Optimizing also moves your shared Google tag settings into one place and links your container to your Google Ads and Analytics accounts, so it can be viewed from within those products too.
A cleaner Google Tag Manager interface
The GTM Overview page has been redesigned to be easier to navigate. Nothing you use today is removed, but things move around:
- Settings is a new tab for settings that apply to the whole container, such as your shared Google tag settings. It also shows a data flow map of which Google destinations those settings apply to.
- Advanced is a collapsible tab that now holds Triggers, Variables, Templates and Folders.
If you or your colleagues wonder where triggers and variables went, look under Advanced.
AI-suggested version names
Since September 17, 2026, GTM suggests a version name and description when you submit changes, based on what changed in the workspace. It’s a helpful start, but add the why yourself. Clear version notes make it much faster to find the last working version if tracking ever breaks.
Visual tagging: set up conversions without code
Visual tagging lets you create events and conversions by clicking elements on your live website, for example a “Buy” button or an order confirmation. GTM then creates the technical pieces, such as selectors and triggers, in the background.
To use it, you need a Google Ads account with at least one conversion action, a sitewide Google tag, and edit access to the GTM container. If you don’t have access, the setup flow asks you to request it from your GTM administrator. If your container already tracks purchase conversions, the flow warns you about possible double counting.
Visual tagging entered beta on Aug. 20, 2026, and it covers Google Ads purchase conversions only. Google plans to extend it to more events and Google products through the rest of 2026 but has not set a release date for any of them. The rollout reaches accounts at different times, so check the Conversions Summary in your Google Ads account to see if it is available to you. We update this section as new use cases go live.
What you need to do
The short answer: nothing is required right now. Your current setup keeps working, and the main change, container optimization, is opt-in. But a little preparation will let you benefit from the update without surprises.
Do I have to act?
No. Google is clear that no changes are made to your container automatically. If you don’t optimize, your existing GTM container keeps working as it does today. You decide if and when to adopt the new setup.
Do I need to reinstall my GTM script?
No. The GTM snippet already on your site keeps working. The new snippet format (without the config command) only matters when you generate new installation code, for example for a new website, a site rebuild or a platform migration. If that happens, ask your developer to check that nothing on the site depends on the old gtag(‘config’, …) line, such as custom scripts or a cookie banner integration.
Do I need to change my data layer?
Your data layer structure doesn’t change, and your existing dataLayer events and variables should keep feeding your tags as before. There is one thing to check: since October 8, old gtag(‘config’) commands show up in the data layer as a gtag.config event. If you use wildcard or regex custom event triggers, confirm in Preview mode that they aren’t firing on this new event.
Do I need to re-implement my tags?
No. When you optimize, your shared Google tag settings move into the new Settings tab and your event tags and triggers stay as they are. You don’t need to rebuild GA4 events or conversion tags. It is, however, a good moment to clean up.
Can I undo the optimization?
Yes. Changes land in a workspace first, so you can discard them before publishing. After publishing, you can roll back to a previous version. One exception: account permissions are not versioned, so a rollback won’t undo the account links the optimization created.
Your pre-optimization checklist
When the optimization banner appears in your container, take these steps before you publish:
- Note your current version. Write down the published version number so you know exactly where to roll back to.
- Audit your Google tags. Containers that have passed through several agencies or colleagues often contain old or duplicate tags. Remove what nobody can explain.
- Check for per-tag exceptions. If some tags use settings that differ from the rest, make sure the new central Settings don’t override them.
- Check advanced settings. Compare the new Settings tab with your old Google tags. Look for anything configured there before, such as a server-side tagging URL or cross-domain measurement.
- Test in a separate workspace. Run the optimization flow there and use the built-in preview to check every change before publishing.
- Verify consent. Test your key events with and without consent to confirm your cookie banner and Consent Mode still behave as expected.
- Review access. Optimization automatically links your container to your Google Ads and Analytics accounts with Read access. On shared or agency-managed containers, check who can now see what. Adjust permissions under External Account Links in the container’s admin settings.
- Brief your team. Let colleagues know triggers and variables now live under the Advanced tab.
- Monitor after publishing. Compare event and conversion numbers in GA4 and Google Ads with the weeks before.
- Try visual tagging if you run Google Ads purchase conversions and want a code-free setup. It’s still in beta, so compare the results with your existing conversion tracking.
If your site only uses the Google tag (no GTM), there is nothing to do. You simply gain the option to use GTM features when you are ready.
What this means for HubSpot, Drupal and WordPress sites
The update works the same on every platform, but where your tags live affects how you prepare.
- HubSpot sites. GTM often runs alongside the HubSpot tracking code. Optimizing your container doesn’t touch HubSpot tracking, but retest your cookie banner and Consent Mode together. Make sure both Google and HubSpot tags still respect visitor consent.
- Drupal and WordPress sites. Google tags are often added through modules, plugins or theme settings rather than directly in GTM. Before optimizing, list every ID on the site and where it is installed. That avoids duplicate tags firing from two places.
- Site rebuilds and migrations. If a redesign, relaunch or platform migration is on your roadmap, add the new GTM snippet and the gtm init trigger to your build checklist. Getting tracking right at launch is far easier than fixing it afterward.
- Multiple sites or containers. If your organization runs several websites, optimize one container first. Confirm everything works before rolling the change out to the rest.
What are the benefits of this update?
For most site owners and marketers, the update makes life easier:
- Lighter pages. Fewer scripts to load can help page speed and the experience of your visitors. Measure before and after to see the gain on your own site.
- One tool instead of two. No more choosing between the Google tag and GTM, or juggling settings in different places. Shared settings now live in one Settings tab.
- A friendlier interface. The everyday view is simpler, while advanced features remain one click away.
- More control for Google tag users. Sites that only used the Google tag get preview, debugging and version history, so changes can be tested and rolled back.
- Less dependence on developers. Visual tagging lets marketers set up conversions by pointing and clicking. It is limited to Google Ads purchases for now, but more use cases are on the way.
- Easier collaboration. Linking your container to Google Ads and Analytics makes your tagging setup visible where your team already works.
Our advice
Don’t rush, but don’t ignore it either. When the optimization banner appears, plan time to audit, test and publish. You’ll end up with a cleaner, faster setup.
Not sure if your container is ready? Digital Polygon can audit your GTM setup, run the optimization in a test workspace, and verify your tracking and consent before anything goes live. Get in touch with our team.
