Short answer: Google has introduced an optimized tagging experience in Google Tag Manager. Your GTM container can now act as the Google tag itself and send data directly to Google destinations such as GA4, Google Ads and Floodlight, without loading a separate gtag.js file for each one. That means fewer scripts, faster pages and one place for settings and access. Nothing changes until you run the upgrade in GTM, test it in Preview and publish.
For most businesses this is good news. For accounts with messy tracking, it is also a moment where data can quietly break. Here is what you need to know.
What is changing
| Before | After optimization | |
|---|---|---|
| How Google products load | GTM loads a Google tag, which loads gtag.js for each product | The container carries the settings, no separate gtag.js per destination |
| Tag types | Google tag plus event tags | New destination tags for GA4, Google Ads and Floodlight |
| Settings | Spread across each Google tag | Shared container settings, managed in one place |
| Conversion Linker | Separate tag | Handled by the destination tags |
The old Google tag and the Conversion Linker become legacy. They keep working, but the direction is clear.
The benefits
- Faster pages. One less loading step for every Google product.
- More reliable data. Fewer scripts means fewer things that can fail or be blocked.
- One place for settings. Things like user provided data collection are set once for the container.
- Easier troubleshooting. Diagnostics and access live in GTM instead of being spread across products.
The risks
- Settings conflicts. Destinations inherit the container settings and can only make them stricter, not looser. If your GA4 tag and your Google Ads tag had different settings before, one of them will change after migration.
- Consent and data rules. If one product collected user provided data and another did not, check carefully which rule you want for the whole container. This links directly to your Consent Mode v2 setup.
- Access. Linked Google tag users can be given read access to the container, but container users do not automatically get access to the linked products.
- No warning for conflicts. Today there is no clear alert that tells you settings clashed. You have to check yourself.
How to migrate safely
- Back up first. Export your current container version so you can roll back.
- Click the upgrade banner in GTM to start the optimization wizard.
- Choose which Google tags to link. Anything you leave unchecked stays as a legacy Google tag.
- Decide whether linked users get read access to the container.
- Choose shared settings: use identical settings, copy one tag as the blueprint, or set them from scratch.
- Open Show details and read the before and after list line by line.
- Click Add to workspace. Nothing is live yet.
- Test in Preview mode: page views, key events, purchases or leads, and Google Ads conversions.
- Publish, then check GA4 real time and Google Ads conversion status over the next 48 hours.
- Move the remaining legacy Google tags to destination tags one by one.
If something breaks, publishing a previous container version rolls the optimization back.
What about server side GTM?
Server side containers have also been reported to get much more room for configuration, which helps larger setups that hit size limits. Google has not shared exact numbers publicly, so check your own container before planning around it. Server side tagging works well with Google tag gateway, which I cover in the Data Strength guide.
Who should migrate now and who should wait
Migrate soon if your setup is simple: one GA4 property, one Google Ads account and clean tags.
Plan carefully if you have several GA4 properties, Floodlight, different consent rules per product, or agencies sharing access. Do it in stages and test each one.
Fix first if you already have duplicate tags or broken conversions. Migration will not clean up a messy container. Start with my Google Ads conversion tracking guide for GA4 and GTM.
Frequently asked questions
What is the optimized tagging experience in Google Tag Manager?
Do I have to migrate?
Will this make my website faster?
Can migration break my tracking?
How do I undo the change?
Who can migrate my GTM container?
Need your GTM checked?
I can audit your container, plan the migration and test every conversion before it goes live. See my web analytics service, or request a free ads audit.
Want help applying this in your own account? See my Google Ads management service or request a free ads audit.