Google Tag Manager Update Brings Google Tag and GTM Together

According to the 2025 Web Almanac from HTTP Archive, 55% of webpages load essential tracking domains such as Google Tag Manager.

Any change to how GTM loads and sends data therefore reaches a large share of business websites, including many in Australia.

In a Tag Manager Help Centre announcement dated 20 August 2026, Google set out a Google Tag Manager update that merges Google Tag and GTM into one tagging infrastructure. 

Every GTM container becomes a Google Tag. Websites that run only the Google Tag also gain the full feature set of a GTM container.

For businesses that rely on Google Ads and GA4, the update affects both page speed and the reliability of the conversion data behind bidding and reporting.

Google is rolling the changes out progressively, so the optimisation prompt and visual tagging reach individual accounts at different times.

This guide explains what the Google Tag Manager update changes in your tracking setup and how to optimise an existing container before you accept the upgrade.

5 Key Changes in the Google Tag Manager Update

The Google Tag Manager update changes five areas of a standard tagging setup, and the largest shift happens in the infrastructure underneath the interface.

Most earlier Google Tag Manager updates adjusted features inside the interface itself.

Google outlined the full scope of its 2026 Google Tag Manager update in a Tag Manager Help Centre announcement.

• Simplified Interface. The redesigned Overview page adds a centralised Settings section for container-wide configuration. Triggers, variables, templates and folders move into a collapsible Advanced tab. Google confirms that the redesign removes no existing functionality. 
• Google Tag and GTM Unification. Google Tags become fully capable GTM containers. Websites that rely on the Google Tag alone gain access to the GTM interface along with its debugging and version control tools. The upgrade leaves the in-page behaviour of existing Google Tags unchanged. 
• Google Destination Tags. Google services such as Google Analytics 4 and Google Ads connect to the container as destinations. Each destination keeps its own tag, so existing triggers for automated events continue to fire. 
• Visual Tagging. A no-code tool in Tag Assistant lets advertisers click elements on their website to create events and conversions. The beta currently covers purchase conversions in Google Ads. 
• Linked Account Access. Optimisation links the container to each Google destination account automatically, with Read access granted by default. Administrators can change these permissions at any time in the Tag Manager user management settings.

How Google Destination Tags Reduce JavaScript Loading

Google destination tags deliver the largest performance change in the Google Tag Manager update by removing the extra gtag.js library GTM previously loaded for each Google Tag.

That saving matters because third-party code already weighs heavily on most websites.

The Web Almanac third-party chapter found that 90% or more of pages load at least one third party, with googletagmanager.com among the ten most common third-party domains.

Direct Data Transmission

With direct data transmission, the GTM container sends measurement data straight to each Google destination without loading gtag.js first.

In the previous model, a GTM container acted as a manager that loaded another manager.

A container holding Google Tags for GA4 and Google Ads requested a separate copy of gtag.js for each tag ID before any measurement data reached Google.

After optimisation, the container itself becomes the Google Tag, and Google Analytics 4 and Google Ads attach to it as destinations.

New deployment snippets are now identical across Google products and no longer include the gtag config command.

Google recommends controlling initialisation through the init trigger in GTM, which can also wait for a config command when a legacy setup depends on it.

Performance Gains for Your Website

Optimised containers send measurement data sooner, because Google confirms the extra gtag.js loads caused latency in measurement transmission.

Removing those loads also gives the browser less JavaScript to download and execute on every page view.

In a Deloitte study published on web.dev, a 0.1-second improvement in mobile site speed increased conversion rates by 8.4% for retail sites and 10.1% for travel sites.

Duplicate library cleanup will not produce a gain of that size on its own.

For a small or medium-sized business with several Google Tags in GTM, the update still offers a low-effort way to reduce the browser’s processing load.

A lighter load also supports a healthier Interaction to Next Paint (INP) score, the Core Web Vitals metric for how quickly a page responds to clicks.

Smaller script loads leave more room in the performance budget for the third-party tags that GTM still manages, such as Meta and LinkedIn pixels.

Centralised Settings in the Google Tag Manager Update

The new Settings tab gives teams one place to manage the configuration that applies to every Google destination in a container.

Before the Google Tag Manager update, these settings lived inside individual Google Tags.

Teams had to repeat any change to domain configuration, internal traffic definitions, unwanted referrals or user-provided data collection in each tag.

Mismatched settings between tags can produce inconsistent numbers across GA4 and Google Ads.

Consistent configuration also protects your marketing attribution, because both platforms start from one shared set of rules unless a tag overrides them. 

After optimisation, GTM moves the existing Google Tag settings into the Settings tab and leaves event tags unchanged.

The tab also displays a data flow map that lists every Google destination receiving those settings.

For agencies that manage containers for several clients, the map offers a fast visual check of where data goes before anyone publishes a change.

The automatic account links also help with troubleshooting, as Google Ads and Google Analytics users can view the linked container from inside those products when a conversion stops recording.

Visual Tagging for Google Ads Conversion Tracking

Visual tagging lets advertisers set up Google Ads purchase conversions by clicking elements on their own site, with no manual coding required.

GTM creates the selectors and triggers in the background, which makes this the most accessible part of the Google Tag Manager update for smaller websites.

The feature is in beta, and Google plans to extend it to more use cases progressively.

For small businesses that track no conversions at all, this tool offers a quick route to a working baseline.

Smart Bidding needs conversion data to optimise campaigns, and a basic purchase signal is far more useful than none.

How the Guided Setup Works

The guided flow runs through Tag Assistant and starts with a test order on your live site.

On the order confirmation page, you select the elements that display values such as the transaction ID, order subtotal, currency and customer email, then publish the changes in GTM. 

Google requires these main things before you start:

• A Google Ads account with at least one conversion action
• An order confirmation page
• A sitewide Google Tag
• Edit access to the container
• An authorised payment card for the test purchase

Limits of Selector-Based Tagging

Selector-based tags read specific elements on a page, and those elements change whenever the website does.

For that reason, visual tagging suits simple websites best.

An online store with a custom checkout or a multi-step funnel still needs a developer-managed data layer to keep tracking stable through site changes.

A broken selector is the first risk, and a small theme change is enough to cause one.

If a theme update renames the class on the order total from total-price to order-total, the visual tag keeps looking for the old class and stops sending purchase values.

GTM shows no error, so Smart Bidding works from incomplete data until someone notices conversions falling in Google Ads.

The second risk, double counting, affects stores that already send purchase events through a plugin or an older GTM tag, a common setup on Shopify and WooCommerce sites.

A visual tag added on top sends every sale to Google Ads twice, which inflates revenue and pushes bad data into every report built on those figures.

Tag Assistant warns you when it finds an existing purchase conversion, so check that message before you publish.

How to Roll Out the Google Tag Manager Update

You roll out the Google Tag Manager update by completing GTM container optimisation, the opt-in step that activates its performance and management gains.

Google recommends it for every advertiser but applies no change automatically.

Users with at least edit-level permission can start the flow from the optimisation banner in Tag Manager and preview every change before publishing it to the workspace.

A structured review protects live tracking during the switch, and the steps below follow the same tracking audit process data teams use for any major container change.

5 Steps for GTM Container Optimisation

1. Clean Up the Current Container

Review every Google Tag and event tag in the workspace, including those created by former staff or agencies. Delete any paused tags and any triggers that have stopped firing. 

The optimisation flow moves everything across as it is, so old clutter will follow you into the new setup if you leave it there. The Export Container option in the Admin section saves a JSON copy of your current setup. 

If a trigger stops working after optimisation, you can import that file and return to the old version.

1. Set a Baseline

Before you switch anything over, write down how many GA4 events and Google Ads conversions your site records each day across a fortnight. These numbers become the benchmark for post-upgrade validation.

2. Run the Optimisation Flow

The optimisation banner in Tag Manager starts the process. Once it finishes, the data flow map in the Settings tab should show every Google destination you expect, with the right ID beside each one.

3. Test in Preview Mode

Tag Assistant preview shows exactly what fires as you click through the site. A form submission and a test purchase cover the journeys most small businesses care about. 

Each event should land in the right destination with its parameters intact. Consent mode defaults need to load before any data leaves the page.

A legacy tag that relied on the gtag config command also needs the init trigger set to wait for it.

4. Compare Results After Publishing

Give the published version a name you can find later, plus one line on what changed. 

For the next week, compare each day’s GA4 events and Google Ads conversions with the same weekday in your baseline sheet. Daily figures will move a little. If purchases drop to zero, republish the backup version straight away.

Prepare Your Container for the Google Tag Manager Update

Google Tag and GTM unification ends the double-loading model that GTM users have worked around for years.

Optimised containers now send data straight to Google destinations from one centralised configuration, and smaller websites gain a no-code path to purchase tracking.

These gains depend on the state of the container you upgrade.

A workspace full of outdated tags carries old errors into the new structure. A clean, well-documented container gives you a faster and more reliable measurement setup.

Accurate tracking starts with a clean container.

Tell No Lies provides the tagging audits and data engineering expertise that businesses need to optimise their containers and protect the accuracy of their reporting.

Contact us today to review your GTM setup before you opt in.