The good news is that Google isn't forcing anything. No changes happen automatically, and you can preview everything before publishing. The less good news is that a related change on October 8, 2026 is already live for everyone, and it can cause some tags to fire when they shouldn't.
Here's what's changing, and five things to check before you click that button.
What's actually changing
Google announced the merger on May 20, 2026, and has been rolling it out since. The main changes:
- Google tag-only sites get full GTM containers. Sites that used the Google tag without GTM gain GTM's interface, debugging and version control.
- A redesigned interface. GTM has a new Overview page, a Settings section for container-wide configuration, and an Advanced tab that holds Triggers, Variables, Templates and Folders.
- Direct sending to Google products. Since October 12, 2026, optimized containers can send data straight to Google destinations like GA4 and Google Ads, without loading a separate
gtag.jsscript. Google says this improves page performance and makes troubleshooting clearer. - The optimization banner. For users with edit, approve or publish permissions, the banner moves your Google tag settings into the new Settings section, links the container to your Google accounts, and lets you preview the result.
Google says the upgrade doesn't change how Google tags behave on your pages, keeps your existing event tags and triggers, and removes no functionality. For simple setups, that's likely true. For complex ones, it pays to check.
Check 1: Back up your container first
Before touching anything, export your current container. In GTM, go to Admin > Export container, choose your current live version, and save the JSON file somewhere safe.
Then note your current Google tag settings: which measurement IDs your Google tags use, any configuration parameters, and any settings like cross-domain linking or ignored referrals. These are the settings that move into the new Settings section. If something looks different afterward, you'll want a record of what it was.
GTM's version history also lets you republish an earlier version, but an exported file is a simple insurance policy that costs one minute.
Check 2: Look for wildcard triggers that may now double-fire
This one doesn't depend on the banner. It's already live.
On October 8, 2026, Google changed how GTM handles gtag('config') commands. Container snippets now initialize when the container loads, and config commands now appear in the data layer as visible gtag.config events.
That matters if you use wildcard custom event triggers: Custom Event triggers set to match any event name, usually with a regular expression like .*. Google warns that these may now fire tags unexpectedly, because gtag.config is a new event they'll match.
How to check:
- Go to Triggers (now under the Advanced tab) and look for any Custom Event trigger that uses regex matching with a broad pattern such as
.*. - Open Preview mode, load a page, and look for
gtag.configin the event list on the left. - Click that event and see whether any tags fired on it.
If tags fire that shouldn't, add a condition to the trigger, such as Event does not equal gtag.config, or tighten the regex so it matches only the events you intend. Double-firing can inflate GA4 event counts and, worse, ad platform conversions, so this is worth fixing quickly.
Check 3: Confirm initialization and consent still work
Google now recommends configuring Google tag initialization with the gtm init trigger, and new snippets no longer include a gtag('config') command. If you want to keep your existing setup, Google says the init trigger can be set to wait for the config command.
Any change to initialization order is a reason to retest consent. If you use a consent management platform and Consent Mode, verify in Preview mode that:
- Your consent defaults are still set before any Google tags fire, typically on the Consent Initialization trigger.
- Tags respect consent updates when a visitor accepts or declines.
- Nothing fires before consent that shouldn't, especially in regions where consent is required.
Consent problems are easy to miss and costly to discover later, so test both the accept and decline paths.
Check 4: Review account links and permissions
During optimization, GTM automatically links your container to the Google destinations it sends data to, such as your GA4 properties and Google Ads accounts. Those links grant read access by default and make the container visible in those products.
That's convenient, but review it:
- Are the linked accounts the ones you expect? Old or test properties sometimes linger in a container.
- Who has access? Check user permissions in GTM's user management settings, especially if agencies or former team members still have access.
Check 5: Preview, compare, then publish carefully
When you do run the optimization, treat it like any significant container change:
- Review the preview of proposed changes before publishing.
- Test key journeys in Preview mode: page views, key events, form submissions and purchases.
- Publish at a quiet time, not on a Friday afternoon or during a big campaign.
- Monitor for a week. Compare GA4 event counts and Google Ads conversions with the week before. A sudden jump or drop points to a problem.
- Know your rollback. If something breaks, republish the previous version from GTM's Versions tab.
GTM will also now suggest an AI-generated version name and description when you publish. It's handy, but edit it so your team knows exactly what changed and why.
Should you optimize now or wait?
For a simple site with standard GA4 and Google Ads tags, the optimization is likely a quick win: a cleaner setup and potentially faster pages. For complex containers with custom triggers, consent logic, server-side tagging or multiple teams, there's no rush. Nothing is forced, so run these checks first, test in a staging container if you have one, and optimize when you're confident.
The bottom line
The merger of the Google tag and GTM should make tagging simpler over time. But "simpler" changes can still break carefully built setups. Back up your container, fix any wildcard triggers affected by the October 8 change, retest consent, review account access, and publish with a plan to monitor and roll back. Ten minutes of checking now can save weeks of questionable data.
If your container has years of custom triggers, consent logic and tags from teams that have since moved on, these checks are much easier with a clean inventory in hand. Our Google Tag Manager consulting service can audit your container for duplicate firing, consent gaps and zombie tags, then run the optimization and testing for you.
Sources: Tag Manager release notes · Google: Changes to the Google tag and Tag Manager · PPC Land: Google Tag Manager and Google tag are merging
