Google Tag Manager Is Changing: Is Your Tracking Setup Ready?

The latest Google Tag Manager update is worth a bit of your attention if your GA4 and Google Ads tracking runs through it. Unlike the previous change to how Google tags work, Google won’t be automatically migrating every existing setup this time, which means somebody needs to review what’s in your container and decide how and when to make the move.

The good news is that it’s very manageable with some planning and testing. Here’s what’s changing, why it matters, and how we’d approach it.

What’s changing in the Google Tag Manager update?

Until now, plenty of setups have had separate Google tag configurations for GA4 and Google Ads. That has meant more to look after and a fair amount of duplicated setup, with the same settings sometimes needing to be maintained in more than one place.

The newer approach is a more unified Google tag, where you can manage the key settings in one place and have them apply consistently to the products your tag is sending data to. Google is also treating the older configuration as legacy, so it’s worth getting ahead of it rather than waiting.

Why it’s worth caring about

  • Potentially better site performance. Fewer separate tags loading for the same job can mean less tag-loading overhead on the page. How much difference you’ll see depends on everything else your site is loading, so we’d treat this as a nice bonus rather than the main reason to move.

  • Simpler tracking management. Cross-domain measurement is a good example. The linker settings that stop a session splitting when someone moves between your main site and a separate checkout domain are far easier to keep right when they’re defined once rather than copied across several tags.

  • Better consent management. Google tags have consent checks built in, and with Consent Mode they adjust what they send based on signals like ad_storage, analytics_storage, ad_user_data and ad_personalization. A single, well-configured Google tag firing on the Consent Initialization trigger means your defaults are in place before anything else runs.

  • A more future-proof setup. With the older configuration now treated as legacy, moving across on your own timeline is much more comfortable than being nudged into it later.

Why this isn’t a one-click migration

Your GTM container is more than a tag. It’s a set of triggers, settings variables, event tags and firing orders that all depend on how your configuration is built, and every container is a little different. That’s why Google isn’t migrating everything automatically this time, and why reviewing your current implementation is the sensible first step.

How we’d approach it

If you have a straightforward GA4 and Google Ads setup, this is usually a case of reviewing the configuration, building the new setup in a workspace and testing it before you publish. Things to check include:

  • the Google tag fires on the right trigger and still fires before your event tags

  • any custom settings (such as send_page_view or cross-domain linker domains) have carried across

  • your Conversion Linker, enhanced conversions user-provided data settings and Google Ads conversion IDs and labels are all still in place

If you have server-side tracking, multiple GA4 properties or a consent management tool, it’s worth planning more carefully and validating everything in GTM Preview before anything goes live. The things we’d look at closely:

  • Server-side tracking: the setting that points your Google tag at your server container (server_container_url or transport_url) needs to carry across. If it doesn’t, hits can start going straight to Google rather than through your server container, and it’s easy to miss because everything still appears to work. We’d also check the server container’s own Preview to confirm requests are being received, claimed by the GA4 client and passed on to your outgoing tags.

  • Multiple GA4 properties: check each measurement ID is sending the events you expect, and watch for overlapping configurations sending the same event twice to one property, which can inflate purchases and conversions without anyone spotting it.

  • Consent tools: confirm your consent defaults are set before the Google tag fires, and use the Consent tab in Preview to check states update when a visitor changes their choices. The consent parameters (gcs and gcd) in the network requests are a handy way to double check what’s actually being sent. e

The risk worth planning around

The biggest risk isn’t a visibly broken tag. It’s losing conversion data and not realising for days or even weeks. Google Ads bidding learns from your conversions, so a drop (or a sudden jump from duplicated events) can change how your campaigns optimise before anyone spots it, and budget decisions end up being made on incomplete information. If your Google Ads conversions are imported from GA4 key events, a break in GA4 will flow straight through to Ads too.

How to test before and after

  1. Take a baseline first. Note your current live GTM version (which also gives you an easy rollback) and record the last few weeks of purchases, revenue, key events and Google Ads conversions.
  2. Build and preview. Make the changes in a workspace and run them through Preview, checking each tag fires once, on the right trigger, with the right parameters.
  3. Check the data is arriving. Use GA4 DebugView, look at the /g/collect requests in your browser’s network tab for duplicates, and check the server container Preview if you use one.
  4. Publish with clear notes. Give the version a descriptive name and add an annotation in GA4, so anyone looking at the data later knows what changed and when.
  5. Compare afterwards. Look at like-for-like periods (same days of the week), check GA4 purchases are following the same trend as your actual order data, and confirm your Google Ads conversion status still shows as recording. Reports can lag by a day or two, so give it a little time. GA4 won’t match your order data exactly these days thanks to cookie consent, but the trends should move together.

A note on timing

If you run an ecommerce business, timing is worth thinking about too. With Black Friday and the Christmas rush on the way, the comfortable options are either making the change early enough to test and settle it before peak, or deliberately holding off until afterwards, rather than changing your tracking in the middle of your busiest weeks. Our Black Friday tracking post covers what else is worth sorting before peak season.

How we can help

This is the kind of thing we work on every day, whether that’s reviewing your current GTM container, planning the migration, building and testing the new setup, handling server-side tracking and consent configuration, or checking your GA4 events and Google Ads conversions before and after the change. A GA4 audit is usually where we start, as it gives a clear picture of what’s in place and what’s worth prioritising.

If you’d like a second pair of eyes on your setup, we’d be happy to help make the transition as smooth as possible.

Has your team started reviewing its Google Tag Manager setup, or is this still on the to-do list?

Get in touch at polkadotdata.com.

[Book a free consultation]