Google is rolling out a series of updates to the Google Tag and Google Tag Manager in August 2026 to create a more unified experience for users.
To understand the rolling out changes, it’s important to remind how Google’s tagging architecture has worked lately.
Google Tag and Google Tag Manager have provided different ways to manage website measurement:
When these tools are implemented separately, a website can end up with additional JavaScript and a more fragmented tagging setup, especially if Google products have been implemented independently over time.
The goal:
Google is unifying Google Tag and Google Tag Manager so that the same tagging infrastructure can provide centralized configuration, debugging, version control, and direct data transmission to Google destinations.
Google has introduced a redesigned Overview page in Google Tag Manager. The new interface moves container configuration into a Settings section. Less frequently used tagging features such as triggers, variables, templates, and folders are grouped under a collapsible Advanced section.
The redesign aims to make GTM easier to navigate without removing existing functionality.
One of the bigger changes is the closer integration between Google Tag and Google Tag Manager.
Websites using only Google Tag will get access to Tag Manager capabilities such as:
✅ Interface-based tagging;
✅ Debugging;
✅ Version control.
Google says the update doesn’t change the in-page behavior of existing Google tags. Each Google destination will still have its own tag, but the settings can be managed through the unified container experience.
Google is also encouraging advertisers to optimize their existing GTM containers. The optimization flow can move Google tag settings into the new Settings tab, connect the container with relevant Google destinations, and make changes available for review before they are published.
Google team says that the updated architecture can improve website performance since it allows Tag Manager containers to send data directly to Google destinations. Previously, GTM could load additional gtag.js JavaScript to send data to a Google destination, potentially adding latency to measurement transmission.
For teams managing several Google measurement products, the changes also provide a more centralized way to manage tagging settings and access.
Google is also introducing Visual tagging, which allows advertisers to configure certain events and conversions by selecting elements directly on their website.
Instead of manually defining selectors, triggers, and other technical settings, users can interact with a website through Tag Assistant.
Note:
The feature is currently in beta for purchase conversions in Google Ads, with additional use cases expected to roll out during the year.
You can find more details on the updates in Google’s documentation.
Google's new approach provides several potential improvements.
On the client side, businesses can benefit from fewer Google scripts loading and simplified, centralized Google tagging configuration.
For server-side tracking, these changes don’t really impact a lot. It can simplify the browser-side Google tagging setup, but they do not inherently reduce the number of requests sent to a server-side GTM container.
No, at least at this point. Google says no changes will be made automatically, and advertisers can choose whether to adopt the new configuration. You can review the proposed changes before publishing them.
Comments