Major Google Tag Manager Update: Optimized Tagging Experience - Analytics Mania
Learn about the new optimized tagging experience in Google Tag Manager and how this update changes tag configuration, migration, and testing.
Learn about the new optimized tagging experience in Google Tag Manager and how this update changes tag configuration, migration, and testing.

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.
Here’s what you will learn in this article
If you prefer video content, watch this tutorial from my YouTube channel.
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.
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.
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.
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.
#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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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:
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.
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.
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.
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.
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.
Texto de Analytics Mania tal como lo publicó, leído de su página y mostrado aquí con el formato de El Autómata. El original, en analyticsmania.com · Volver a la noticia de El Autómata