GTM destination tags: what the Tag Manager update changes

With GTM destination tags, Google is rebuilding Tag Manager from the ground up: your container takes over the job of the Google tag, and GA4, Google Ads and Floodlight hang off it as “destinations” with shared settings. For you that means less code on the page, but also new places where consent, conversions and access rights can quietly break. Here’s what changed, what it means for a Google Ads account in Germany, and how to switch over safely.

Watch on YouTube

1. GTM destination tags: what Google changed in Tag Manager

Google announced the change in the Tag Manager release notes on 12 October 2026. The most thorough analysis comes from Simo Ahava: Optimized Tagging Experience For Google Tag Manager (13 October 2026). He calls it the biggest change in Google Tag Manager in over a decade. This article is about what it means for your ad account, and the facts rest on Google’s own help pages.

Before: every Google tag with its own code and its own rules

Until now, Google measurement in a container worked like this: you created a tag of the type “Google Tag”, and it loaded the gtag.js library on top. Only through that library did the data reach GA4 or Google Ads. According to Google, this could delay transmission. On top of that, each of these Google tags had its own settings and permissions, maintained in Google Ads or GA4 rather than in the container. What separates GTM from GA4 in the first place is covered in GTM vs GA4.

After: the container sends the data itself

Now the container sends data directly to the Google products, without loading gtag.js. Google calls the receivers “destinations” and lists four types:

• a GA4 web data stream,
• a Google Ads account,
• a Floodlight configuration (Campaign Manager 360, Display & Video 360),
• a Merchant Center conversion source.

Each destination is connected through a destination tag. For Google Ads you enter the Conversion ID there, and the trigger defaults to initialization on all pages. As soon as you add a destination tag, it automatically sends a page view to that destination. Your existing event tags and triggers, such as the conversion tag on your thank-you page, are kept when you upgrade.

Two more changes show up in day-to-day work:

• A new “Settings” tab: it lists all Google destinations in the container plus the shared settings: automatic event detection, domains for cross-domain measurement, user-provided data, internal traffic, cookie settings and consent defaults. A destination tag can override individual values for its destination.
• Versions for the settings: the upgrade lands in your workspace like any other change. You test it in Preview, publish it as a version and can go back to an earlier one. Only permissions, according to Google, are not versioned.

What happens to the Google tag and the Conversion Linker

According to Google, a container doesn’t need a Conversion Linker if a Google tag or a destination tag for your destination loads on every page. Simo Ahava classes the “Google Tag” tag type and the Conversion Linker as legacy in the new setup: the destination tags take over their jobs.

Still, nothing switches over by itself. Google shows you a banner in the container, and you decide when to start the optimization. Simo’s explanation: unchecked shared settings could cause data quality and compliance problems.

A note about my own templates: the templates with Google Ads tracking in the GTM configurator still use the classic setup with a Google tag and a Conversion Linker, which Google continues to support. After importing one, upgrade it as described in section 3.

2. What the update means for your Google Ads account in Germany

For German accounts, three things matter: consent, user data for enhanced conversions, and access.

Consent: three settings that are easy to mix up

Under “Settings” you’ll find the consent options that used to live in the Google tag settings in Google Ads or GA4. They now apply to every directly connected destination:

• “Set consent mode override” sets the default consent to “denied” for the regions you choose, whatever your website code says. Once the visitor decides in the banner, their choice applies. It only works if the next setting is set to “No”.
• “Manage default consent settings” is meant for websites without Consent Mode whose tags only load after consent. Choosing “Yes” confirms to Google that all data sent was collected after consent. If you use Consent Mode, leave it at “No”.
• “Manage data transmission” limits what the Google destinations send while there’s no consent. For advertising data there are two levels: only limited data, without identifiers that could track people across sites or sessions (conversion modeling is preserved), or no advertising data at all until ad_storage is granted. Analytics and diagnostics data can be blocked as well. According to Google, this requires Consent Mode to be active.

Important: these settings only apply to Google destinations connected directly to the container. For Meta, LinkedIn or Microsoft Ads, your cookie banner and its release of the individual tags remain in charge. How to set up Consent Mode properly is in Consent Mode v2 setup. Whether the container may load before consent is a question the update doesn’t answer. More on that in my Google Tag Manager guide.

Enhanced conversions: one setting for every destination

“Allow user-provided data capabilities” is now a container setting. It lets the Google destinations pick up, for example, the email address from a form, hash it and send it to Google Ads for enhanced conversions. Two rules are worth knowing:

• If you turn the feature off in the container, none of the directly connected destinations receives this data, according to Google.
• A destination tag can only make the container settings stricter, never looser. That’s how Simo Ahava describes it: if the feature is off in the container, the Google Ads destination tag can’t turn it on. The reverse works.

This is the biggest risk. If your existing Google tags have different settings, say the GA4 tag without user data and the Google Ads tag with it, you decide in the wizard which settings the container takes over. Pick the wrong ones and your enhanced conversions stop receiving user data without a single tag failing.

If your container still loads a Google tag as an intermediary for a destination, the container settings don’t apply to that destination. You keep maintaining those values in that Google tag’s own settings.

Access: who gets to see your container

During the optimization you decide, for each destination, what access its users get to the container (you need admin rights on both sides). According to Google, the default is Read access. So anyone with access to your Google Ads account can read your container afterwards. The reverse doesn’t happen: according to Simo Ahava, container users don’t get access to the linked products.

So check the user lists in Google Ads and GA4 first: old agencies, former freelancers, people who left the company. You can change access later in the container’s admin settings under “External Account Links”. And because permissions aren’t versioned, a rollback doesn’t take back access you’ve already granted.

3. Checklist: how to upgrade your container safely

I worked for Google on measurement implementations, and my advice here is unspectacular: treat the upgrade as a migration. Simo Ahava recommends the same for complex containers: add destinations step by step, test, roll back if needed.

Before you start

1. Note the number of the currently published container version. That’s your way back.
2. Write down which Google tags run in the container (IDs like G-… and AW-…) and how they’re configured: user data, consent, domains.
3. Check the user lists of the accounts you want to connect.

In the wizard

4. In GTM, open the “Overview” page. In the “Optimize your Tag Manager container” banner, click “Review details” if all Google tags share the same settings, otherwise “Get started”.
5. Choose the Google tags you want to consolidate. In a large container, start with one destination, such as GA4, and add Google Ads later.
6. Set the container settings, checking user data and consent as you go.
7. Decide on access for each destination.
8. Click “Preview changes” and read the list before you choose “Add to workspace”. Nothing is live yet.

Testing: what matters for conversions

9. Start Preview. Tag Assistant opens in a new tab. Then check:

• The Google Ads destination tag fires on every page, including the landing page. Only then is the Conversion Linker redundant. I’d remove it in a separate step after the first test.
• Your Google Ads conversion tag fires on the thank-you page, with the same Conversion ID and label as before. How that tag is built is covered in Google Tag Manager for Google Ads.
• Open a landing page with ?gclid=test appended and accept in the banner. Your domain’s cookies should then include _gcl_aw. Repeat with a refusal: then it should be missing.
• For enhanced conversions, submit a test enquiry and, in the developer tools under “Network”, find the request to googleadservices.com/pagead/conversion/. The em parameter must show a long string after tv.1~em. If it only shows tv.1~em, no user data is arriving.

Publish and monitor

10. Click “Submit”, choose “Publish and Create Version” and give the version a clear name, such as “Optimization GA4 and Google Ads”.
11. Over the next few days, compare conversions in Google Ads with the weeks before and check the status of your conversion actions under Goals → Summary. According to Google, the enhanced conversions diagnostics report shows whether user data is arriving about 72 hours after setup.
12. If something goes wrong, revert the workspace to the version you noted and publish it. Access rights you take back by hand under “External Account Links”.

The bottom line

• The container takes over the role of the Google tag. GA4, Google Ads, Floodlight and Merchant Center hang off it as destinations with shared settings.
• No extra gtag.js loads for these destinations, and the Conversion Linker isn’t needed once the destination tag loads on every page.
• One wrong value for user data or consent now affects every destination at once.
• Users of your Google Ads account can get Read access to the container, and a rollback doesn’t change that.
• Upgrade like a migration: note the version, test step by step, then publish.

Want to upgrade your container without losing conversions? If you’re facing a specific decision, such as which container settings to keep or whether to switch in several steps, the Clarity Session is the right step: from €390, a 60-minute video call. If you’d rather have your measurement checked in full, the conversion tracking audit covers that. Whether the session fits is something you can check first in a free intro call. Book a free intro call.

FAQ

Do I have to upgrade my GTM container now?

No. Google calls the optimization a recommendation, doesn’t switch anything by itself and so far names no end date for the old setup in its help pages (as of 28 October 2026). Ideally, upgrade in a quiet week, not right before a high-budget promotion.

Do I still need the Conversion Linker?

According to Google, not if a destination tag or a Google tag for your Google Ads account loads on every page. Only remove it once you’ve seen in Preview that the destination tag fires on all pages and the click cookie is set after consent.

Will the upgrade change my conversion numbers?

According to Google, event tags and triggers are kept. Numbers change when settings change, for example if the container no longer allows user data or stricter consent rules apply. Those are exactly the values to check before “Add to workspace”.

Will my agency get access to my container?

Yes, if it has access to your Google Ads or GA4 account and you accept the default Read access. It can’t edit the container then. You can change that at any time under “External Account Links”.