About cookies on this site

We use cookies to collect and analyse information on site performance and usage, to provide social media features and to enhance and customise content and advertisements. Learn more

Cookie settings

About cookies on this site

Cookies used on the site are categorized and below you can read about each category and allow or deny some or all of them. Learn more

Necessary

Some cookies are required to provide core functionality. The website won't function properly without these cookies and they are enabled by default and cannot be disabled.

Preferences

Preference cookies enables the web site to remember information to customize how the web site looks or behaves for each user. This may include storing selected currency, region, language or color theme.

Analytical cookies

Analytical cookies help us improve our website by collecting and reporting information on its usage.

Marketing cookies

Marketing cookies are used to track visitors across websites to allow publishers to display relevant and engaging advertisements. By enabling marketing cookies, you grant permission for personalized advertising across various platforms.

🔥 Black Friday/Cyber Monday: save up to 42% on our courses. Ends December 3rd.

See the deals
  • Courses
    • 👉 SALE
    • Paid courses
    • Course bundles
    • Free courses
  • Blog
  • Resources
    • Youtube channel
    • E-books and Guides
    • Free courses
    • GTM Recipes
    • View All Resources
    • GTM Community
    • GA4 community
  • Services
  • About
    • About
    • Contact
  • Login
  • Courses
    • 👉 SALE
    • Paid courses
    • Course bundles
    • Free courses
  • Blog
  • Resources
    • Youtube channel
    • E-books and Guides
    • Free courses
    • GTM Recipes
    • View All Resources
    • GTM Community
    • GA4 community
  • Services
  • About
    • About
    • Contact
  • Login

October 27, 2026

Major Google Tag Manager Update: Optimized Tagging Experience

If you opened Google Tag Manager recently, you might have noticed a new Settings section, a diagram of your Google tags, and an invitation to optimize your container. There are also changes to the tag types you use for Google Analytics and Google Ads.

In a nutshell, Google is bringing Google tag and Google Tag Manager together. The Optimized Tagging Experience lets GTM send data to Google destinations without loading the additional Google tag libraries, and moves shared tag settings into the container.

The migration wizard handles much of the work. But you still need to choose which settings to keep, review who gets access, and test your tracking before publishing.

Subscribe and Get the Ebook - Real Book Img - GTM for Beginners

Table of Contents

Here’s what you will learn in this article

  • Why Google is changing the tagging setup
  • What are destinations in Google Tag Manager?
  • How to migrate to the Optimized Tagging Experience
  • What happens to your existing tags?
    • What happened to the old Google tag and Conversion Linker?
  • Shared settings in the GTM container
    • How to add another destination
  • How to test the migration
  • Can you undo the optimization?
  • Should you migrate now?
  • Frequently asked questions
  • Final words

 

Video tutorial

If you prefer video content, watch this tutorial from my YouTube channel.

 

Why Google is changing the tagging setup

In the previous setup, your GTM container loaded a Google tag for Google Analytics. If you also used Google Ads, you could have another Google tag for that product, with your Google Ads conversion tags using its library.

That meant extra JavaScript for the browser to load and process. Adding more Google tags could increase the work your website was asking the browser to do.

In my demo container, I have two Google tags, one for Google Analytics and one for Google Ads. You can see the extra step between the GTM container and the destinations in the Overview diagram.

With the optimized setup, GTM handles those Google destinations directly. The extra Google tag library loads are removed for the destinations you optimize.

I welcome that change. However, I wouldn’t promise a specific improvement in page loading speed without measuring it on your website. The effect depends on your current tagging setup and everything else the page loads. But on the other hand, you would most likely to notice at least a small improvement.

 

What are destinations in Google Tag Manager?

One of the main messages of this migration is that “Google Tags are now replaced by Destinations”. So what are they?

A destination is the Google product receiving your data, such as a Google Analytics 4 data stream or a Google Ads account. The new destination tag types are called Google Analytics, Google Ads, and Google Floodlight.

For example, the Google Analytics destination tag contains the GA4 Measurement ID. Your GA4 event tags still send events such as purchase to that destination. Visually, a destination tag looks very similar to good ol’ Google Tag.

And you will still work with tags, triggers, and variables. The main change is how the Google destination is initialized and where its shared settings are managed.

These shared settings apply to the Google destinations using the optimized setup. They don’t configure your Meta Pixel, Snapchat tags, or other vendors’ tags.

 

Which permissions do you need for the migration?

Before we start, be aware that certain permissions are required to complete the migration.

You will need at least Edit permission in the Google Tag Manager container to start the migration and add the changes to a workspace. Publishing those changes requires Publish permission. So if you can prepare the migration but cannot click Submit, check your container permissions.

Linking Google Analytics to the GTM container is a separate part of the process. For the linking flow, you will need Publish permission in GTM and Administrator access to the Google Analytics property. Having enough access to edit tags does not automatically give you enough access to create the external account link.

If hovering over a Google tag in the Overview diagram does not show the migration popup, check your permissions first. Another cause I ran into was a Lookup Table variable in the Google tag’s Tag ID field. I will explain the workaround a bit later in this blog post.

Note: linking Google Tag Manager to Google Analytics (or Google Ads) via External Account Link is optional. You should do it only if you want to quickly access Google Tag Manager from the GA/Google Ads interface.

 

How to migrate to the Optimized Tagging Experience

This is not done automatically for you. You will need to be involved, at least to some extent.

Luckily, the migration is a workspace change that you can test before publishing. And that’s good. You’ll have more control that way. I would start by checking your existing Google tag settings, particularly if your GA4 and Google Ads configurations differ.

The walkthrough below uses a container with separate Google Analytics and Google Ads tags. Google’s container optimization documentation also covers the shorter flow for containers whose Google tags already use the same settings.

 

#1. Open the optimization wizard.

Go to your container’s Overview page and look for the Optimize your Tag Manager container banner. Depending on your setup, the button can say Review details or Get started.

In the screenshot below, I hovered my mouse over one of the Google Tags in the workflow chart.

Another option is Settings > Google destinations: hover over “No” in the Optimized column and click Get started.

 

#2. Choose the Google tags to migrate and review access.

The wizard lists the Google tags available for optimization. In my example, I select both the Google Analytics tag and the Google Ads tag.

Also, check the access setting beside each tag. Keeping Read access allows users with access through that linked Google tag or destination to view the GTM container.

Read access means that if a person has access to Google Analytics or Google Ads, they will be able to see what’s inside the Google Tag Manager container, too. They won’t be able to make changes, though.

If you don’t want to grant that visibility, select No access. Don’t leave the default selected without checking who can access the linked Google products.

Subscribe and Get the Ebook - Mastering GA4 event tracking

#3. Choose the container settings.

When your Google tags have different settings, the wizard asks which tag’s settings should become the GTM container settings. Use View settings to inspect the options before choosing.

In my demo, I select the Google Analytics tag as the source. Its Google tag settings are copied into the GTM container and become the shared settings for the optimized destinations (this means that they would also apply to Google Ads tag).

This is the part where I would slow down. Choosing a tag here is more than choosing a name from a list: you are deciding which configuration the destinations will inherit.

Review settings such as your cross-domain configuration, automatic event detection, and user-provided data collection. If your Google Ads tag and Google Analytics tag have intentionally different configurations, check what the shared setup will do to each destination.

If some differences are a deal-breaker for you, maybe you should postpone the migration until we get more clarity from Google.

The wizard also has a Do not import Google tag settings option. Choose that only if you intend to configure the container settings yourself.

 

#4. Review the changes and add them to the workspace.

Open Show details in the top right corner of the wizard. Check which tags will be modified and review the permission changes.

The before-and-after diagram is useful here. It shows which destinations will connect directly to the GTM container after optimization.

Once you have verified everything and are ready to migrate, click Add to workspace. The tagging changes are now in your workspace, ready for testing.

Don’t click Submit yet. First, check the updated tags and the shared settings.

 

How to migrate a Google tag that uses a Lookup Table variable

Things get a bit trickier if you use a Lookup Table variable as a Measurement ID in the Google Tag.

A Lookup Table variable can choose a GA4 Measurement ID based on the website’s hostname. For example, one GTM container can send data from website A to one GA4 property and data from website B to another, without duplicating the tags.

However, Google Tag Manager’s migration wizard does not like that. If you are using the variable and try to hover your mouse over a Google Tag (in the container’s Overview section), the migration popup will not appear.

A solution for that is to temporarily replace the variable with a static Measurement ID. Then complete the migration and switch back to the Lookup table variable. I explain the exact steps in the video below (starting at 8:01)

Before doing this, decide which Google tag’s shared settings you want the GTM container to inherit. Check things such as cross-domain tracking and user-provided data collection. Those settings will apply to all optimized destinations in the container.

#1. Open the existing Google tag and temporarily replace the Lookup Table variable in the Tag ID field with the chosen Measurement ID. Save the tag, but don’t publish this temporary change.

#2. Return to Overview, hover over the Google tag, and click Get started. Complete the migration wizard and add the changes to the workspace.

#3. Open the migrated Google Analytics destination tag. Replace the static Measurement ID with the original Lookup Table variable and save the tag.

#4. Open Settings and check the destinations. In my test, both Measurement IDs appeared as optimized after I add the lookup table variable back to the destination tag. Check the External account link status too (in the Settings tab of the container), because the wizard did not link the second destination automatically (so, you will need to do this manually).

#5. Test each hostname and confirm that events reach the intended GA4 property. Publish only after restoring the Lookup Table variable and checking the routing. You do not need to replace the variable in your GA4 event tags for this migration.

 

A destination warning when using a Lookup Table variable

After migration, a GA4 event tag can still warn that it cannot detect the destination when its Measurement ID comes from a Lookup Table variable. But you can ignore it. The destinations are connected, and the variable works. The warning appears because that check does not evaluate the IDs inside the lookup table.

Check Settings and test the resolved Measurement ID in Preview mode. If the destinations are present and the events reach the correct properties, this warning alone does not mean the setup is broken.

If you later add another Measurement ID to the Lookup Table variable, GTM will detect it and add it to the destination list (the Settings tab of the GTM container). The destination list will take a few seconds to update, and the new destination’s external account status will be Not linked. So, you will need to link GA and Google Tag Manager yourself.

 

What happens to your existing tags?

After migration, the tags you optimized use the destination tag types. In other words, tags with “Google Tag” template are now migrated to use “Google Analytics”, “Google Ads” or “Floodlight” tag templates. Destination tags replaced Google Tags.

Open the Google Analytics tag (personally, I still prefer calling it “GA Config tag”) and you will still find familiar options, including the Measurement ID, configuration settings, and shared event settings. Review the existing values and the firing trigger.

The GA4 event tags (and all non-google tags) remain in place. In my purchase event tag, the interface now confirms that a destination was found in the container, where it previously referred to a Google tag.

You don’t need to recreate every event tag just because you migrated. Still, include those events in your tests. A successful migration dialog doesn’t prove that a purchase event sends the right data.

 

What happened to the old Google tag and Conversion Linker?

When you create a new tag, you will find the destination types under their respective Google products. For Google Analytics, select Google Analytics for the destination, or the GA4 event tag when you need to send an event.

The old Google Tag is still available under Other Google. Conversion Linker is also there, and it’s marked as Legacy in the tag picker.

The optimized destination tags handle the conversion-linking functionality. Once your relevant destinations are migrated and tested, you are free to delete the Conversion Linker.

However, if you are migrating only part of a container, check the remaining setup before removing tags. Keeping a tag temporarily is better than deleting something you haven’t checked.

 

Shared settings in the GTM container

Open Settings in the left sidebar of Google Tag Manager. At the top, Google destinations lists the configured destinations and shows whether each one is optimized. If you have a Google tag in the container which was not migrated, then “Optimized” will display “no” next to it.

Below that list are the shared settings. These include options such as Manage automatic event detection, Configure your domains, and Allow user-provided data capabilities. It’s pretty much the same list that you are used to seeing in Google Analytics > Admin > Data Streams > Web stream > Configure tag settings.

All optimized Google destinations in the same GTM container inherit the shared settings in this section. If you change those settings, you are changing the shared configuration for all of those destinations.

For example, suppose you use Google Analytics and Google Ads on two domains that are part of the same measurement setup. Go to Settings > Configure your domains and add both domains there. You can manage the domain list in one place instead of maintaining it separately in each Google tag. That’s convenient.

The migration wizard copies the settings from the Google tag you selected. That selection becomes the starting configuration for the container. After migration, use GTM’s Settings section to manage the shared configuration.

This also changes how you publish those settings. Saving a change adds it to the workspace, where you can review it and test it in Preview mode. The settings change goes live only when you publish the container, and it becomes part of the container’s version history.

For example, after updating your domain list, test the cross-domain setup before publishing. The shared configuration affects every optimized destination in the container, so check both Google Analytics and Google Ads if you use both.

The Configuration settings and Shared event settings inside an individual destination tag are separate controls from the container’s Settings page. If you change something in the tag (e.g., add a “linker” parameter there, it will overwrite whatever is configured in the “Settings” tab of GTM container.

 

How to add another destination

If you ever need to add more destinations to the GTM container, you can do it through Tags > New > Tag Configuration and select Google Analytics, Google Ads, or Google Floodlight. Creating a tag there adds the destination.

Another option is a shortcut under Settings > Add destination. Select the destination you want to configure, and GTM opens the same tag creation flow.

Subscribe and Get the Ebook - Increase data accuracy in google analytics 4

 

Optimized and Linked are separate statuses

In GTM’s Settings section, a destination can be optimized while its External account link still says Not linked. I saw this when migrating a Google tag that used a Lookup Table variable: both destinations became optimized, but only one was linked automatically.

Note: linking Google Tag Manager to Google Analytics (or Google Ads) via External Account Link is optional. You should do it only if you want to quickly access Google Tag Manager from the GA/Google Ads interface.

To review the missing link, hover over Not linked and click Add link. You can also open Admin > External account links. Select the relevant GA4 data stream and complete the linking flow with the required GTM and Google Analytics permissions.

Pay attention to when this takes effect. Tagging changes wait in the workspace until you publish, but an external account link takes effect immediately. If you grant Read access through the link, people with access to the linked Google Analytics property can view the container before you publish the migration.

They can reach it from Google Analytics > Admin > Data streams > the web stream > Configure tag settings, then select the linked GTM container. That link grants read access, not permission to edit or publish tags. A person who already has higher GTM permissions keeps those permissions.

 

Does the migration change Consent Mode?

The optimized destination tags continue to use your Consent Mode configuration. You do not need to rebuild Consent Mode just because you replaced a Google tag with a destination tag.

In my test, the default consent state denied analytics_storage and ad_storage. As a result, the outgoing GA4 page view included gcs=G100 (which is expected). After I sent a consent update granting both storage types, a subsequent user_engagement request included gcs=G111 (which is also correct)

You can inspect this in Tag Assistant (GTM preview mode): check the Consent tab, then open the relevant request under Hits Sent. The gcs values in this example describe analytics_storage and ad_storage; they are not a check of every Consent Mode setting.

Keep your existing consent setup and include it in the migration tests. Verify the default state and what happens after accepting or rejecting consent, using the behavior your implementation is supposed to have.

 

How to test the migration

After you complete the migration wizard, the next step is to test. Click Preview in GTM, enter your website URL, and connect Tag Assistant. Check the destination tags and the events that matter to your implementation before publishing.

If you need a refresher, my Google Tag Manager Preview mode guide explains how to use the debugger.

One visible change is the Hits Sent tab under the GTM container itself. Previously, you would switch to a Google Analytics or Google Ads ID to inspect those requests.

In my demo, Hits Sent shows a page view going to Google Analytics and another request going to Google Ads.

The Tags tab also shows the shared tag settings used by the optimized destinations. Open a setting to inspect its configuration while debugging.

For the migration, I would check:

  • The Google Analytics and Google Ads destination tags fire on the intended triggers.
  • Page views and your important events reach the correct destination IDs. For example, you can verify this with Google Analytics DebugView.
  • A test purchase or lead sends the expected parameters and doesn’t create duplicate events.
  • Your consent behavior still works when consent is denied, granted, or changed.
  • Any cross-domain setup and settings you carried over still behave as intended.

Check the data in the receiving product too, where its debugging tools allow it. For GA4, DebugView is useful for inspecting the events and parameters from your test session.

When the tests pass, click Submit in the GTM container and publish a container version with a description of the migration (Gemini will generate it for you). Then check the published setup as well.

 

Can you undo the optimization?

You can undo the tagging changes in the workspace before publishing. If you have already published them, you can roll back to a previous container version.

However, permissions need a separate check. Google’s optimization documentation explicitly says, “Permissions are not versioned.” Restoring an older container version won’t undo the access you granted during optimization.

To change that access, go to Admin > External account links in the container. Review the linked accounts and adjust their access there.

 

Should you migrate now?

I would plan the migration rather than leave the container on the old setup indefinitely. Fewer Google tag library loads and a single place for shared settings are useful improvements.

If you have a straightforward container and time to test it, the wizard makes this fairly simple. With multiple destinations and conflicting settings, allow more time to compare the configurations before publishing.

You don’t have to treat the optimization banner as a reason to rush an untested change onto your website.

 

Frequently asked questions

What changes should I make in my server-side GTM container after migration? No changes are required in your server-side GTM container for this migration. The Optimized Tagging Experience changes the web container. SGTM behavior does not change. Keep your existing server container configuration. After migrating the web container, test that requests still reach your tagging server and that the expected server tags fire.

The server_container_url configuration parameter stays in the migrated Google Analytics destination tag in the web container. Keep its existing value (or the variable containing your tagging server’s URL).

Should I remove the Conversion Linker from my server container? In the web container – yes (after the migration). However, the server-side GTM container (if you have configured Google Ads tracking there) will still ask you to add the Conversion Linker tag there (and that’s ok)

Do I need to recreate my GA4 event tags? No. The migration keeps your existing event tags and triggers. Test your important events after migrating to confirm that they still send the expected data.

 

Optimized Tagging Experience in Google Tag Manager: Final words

Google Tag Manager’s optimized setup removes the extra Google tag library loads for migrated destinations and brings their shared settings into the container. Your existing event tags remain part of the setup.

The work is in choosing the right settings, checking access, and testing the data after migration. I think this is a welcome update, even if it means getting used to another change in Google’s tag names.

If you want to get more comfortable with tags, triggers, and testing your tracking setup, take a look at my Google Tag Manager Masterclass for Beginners.

Subscribe and Get the Ebook - Server-side tagging
Julius Fedorovicius
In Google Tag Manager Tips
14 COMMENTS
Arturo Santiago-Rivera
  • Oct 20 2026
  • Reply

Hello! What if a client is using a regex or a lookup table for the Measurement-ID in a Legacy Google Tag?

    Julius
    • Oct 21 2026
    • Reply

    Hi, the article is updated to explain that

      Arturo Santiago-Rivera
      • Oct 21 2026
      • Reply

      Thank you for the article update on using a regex or lookup table in the Measurement ID for the legacy Google Tag. It has been extremely helpful in determining the approach.

Chris
  • Oct 21 2026
  • Reply

Currently if you enable optimization, but also have a gtag.js the tracking breaks - tag are stuck on still running status, and there are no relevant network hits. Both GA4 event and Ads conversion tracking is affected.

If you dont have a way to remove the gtag.js from code (maybe you dont have the access, or don't know how to), do NOT enable the google tag optimization in GTM.

As far as I know, you cant reverse it either. I guess we will have to way until it is possible to remove this 'optimization'

    Julius
    • Oct 21 2026
    • Reply

    1. That's why you should use the GTM preview to test the setup before you publish.

    2. You can revert. Delete the GA destination tag and create a Google Tag (legacy) instead

Sava
  • Oct 22 2026
  • Reply

I think (if I understood the article correctly) it would be be beneficial to leave a note that linking the external account is necessary only if you want others to have access to the settings from GA4 or G Ads.
In our case, GTM and all relevant are managed by a separate team and it does not make sense to link and give access for people who have access to G Ads (there's tens of people)
What do you think?

    Julius Fedorovicius
    • Oct 27 2026
    • Reply

    Good idea, I will add a note

DimChi
  • Oct 27 2026
  • Reply

What if you have a single google tag with many measurement-id's (say with a lookup table)? Is it possible to do this upgrade? It looks like it is not tbh, but I just want to be sure there is a way

Thank you

    Julius Fedorovicius
    • Oct 27 2026
    • Reply

    This is already mentioned in the blog post. And more details are in the 2nd video of this article

Marianne
  • Oct 31 2026
  • Reply

Thanks for your guide.

I would love future blog posts about what the optimized set up should look like and work together and its implications. In a client side set up what should it look like after optimizing and what issues are people coming across./

More on how we'll use these systems future state. For example, I'm now building events in GA4 vs. building most in GTM like I used to. How GA4 and Ads can talk or intermingle now. FYI when I go into GA4 in the Advertising then Conversion Management I get an error when I try to build an Ads conversion that way.

J
  • Nov 2 2026
  • Reply

A question on the settings. If you have the Gtag settings in place in GTM can you not then override these in the stream settings in GA allowing you to have different settings across multiple GA streams?

Which is ‘canonical’? I.e. which settings tab takes precedence over the other?

J
  • Nov 2 2026
  • Reply

Great article btw!

Julius
  • Nov 3 2026
  • Reply

You can overwrite whatever is possible in the Destination tag. But not everything is possible. For example, if you want to manage the list of internal traffic's IP addresses, that will have to be done in the shared settings (as far as I know, you cannot set the IPs directly in the destination tag). So the list of IP addresses will be shared across all destinations.

If it is important for you to have different IP addresses (for example) in different destinations, you will have to keep using Google Tag (instead of destinations) and then manage the IP addresses in the admin panel of Google Analytics for each individual data stream (in other words, you will have to NOT migrate to the new experience). At least, that's how it works right now

Helena
  • Nov 17 2026
  • Reply

I would have one further question about the settings. I currently use a regex table in my container that maps the data to different GA4 properties based on hostname:
test1.mywebsite.at - Property1
test2.mywebsite.at - Property1
test3.mywebsite.at - Property1
mywebsite.jobs - Property2
mywebsite-test.at - Property3

I already know that regex tables are not supported in the new setup, only lookup tables are. But regarding my actual question:
I want to enable cross-domain measurement for the first three as they all go into the same GA property, but not for the last two as each of them has their own property. Would I have to split this setup into 3 GTM-Containers now to account for that? Or can I add the first three hostnames to the cross-domain list in the settings without also impacting measurement for the other sites?

Leave a comment Cancel reply

Your email address will not be published. Required fields are marked *


 

Hi, I'm Julius Fedorovicius and I'm here to help you learn Google Tag Manager and Google Analytics. Join thousands of other digital marketers and digital analysts in this exciting journey. Read more
GTM & GA4 Essentials Bundle — five free e-books 5 free e-books GTM & GA4 Essentials Bundle Get your tracking right. Tags, the data layer, GA4 reports and server-side tagging, explained in a way I wish someone had explained them to me. Send me the e-books
Analytics Mania
  • Google Tag Manager Courses
  • Google Tag Manager Recipes
  • Google Tag Manager Resources
  • Google Tag Manager Community
  • Login to courses
Follow Analytics Mania
  • Subscribe to newsletter
Recent Posts
  • Major Google Tag Manager Update: Optimized Tagging Experience
  • “_Tagging Activity Tag” in Google Tag Manager Preview Mode
  • Where to Find Video Engagement Data in Google Analytics 4?
Analytics Mania - Google Tag Manager and Google Analytics Blog | Privacy Policy
Manage Cookie Settings