Google is rolling out updates to Google tag and Google Tag Manager that it says are designed to “improve performance and management, and provide a more unified experience across Google’s tagging products.” The changes are set out in Google Tag Manager Help on August 20: a redesigned interface, Google tags to be upgraded to full containers, and an opt-in path to send data straight to Google destinations. Ginny Marvin, Google Ads Liaison, framed it the same day: “Today, we’re rolling out updates across our tagging tools to make it easier for advertisers to effectively measure website performance.”
What changed in Google Tag Manager on August 20?
Google Tag Manager’s Overview page moved to a reorganized layout with new Settings and Advanced sections, and Google says Google tags will be upgraded to fully capable Tag Manager containers. Advertisers who use Google Tag Manager can opt into direct-to-Google delivery from an in-account optimization banner, which Google’s Ads Liaison says is coming soon, with a preview step before anything publishes. Google says the upgrade does not change the in-page behavior of the tags. Visual, no-code tagging remains in beta and is scoped to Google Ads purchase conversions only.
A Reorganized Overview, With Settings and Advanced Tabs
The container’s Overview page is being reorganized. Nothing already configured disappears: “This update won’t remove any functionality you already use,” the Help doc says. A new Settings tab is “a new, centralized location for managing container-wide settings,” and a collapsible Advanced tab now holds Triggers, Variables, Templates, and Folders. Accounts that only ever used the plain Google tag will gain access to that same interface, plus debugging and version control.
Google Tags Become Full Tag Manager Containers
“Your Google tags will be upgraded to fully capable Google Tag Manager containers,” the Help doc states. “Each Google destination will have its own tag, preserving your existing setup and triggers for automation events.” The upgrade “will not change the in-page behavior of the Google tags.” One detail applies to new deployments only: new deployment snippets will not carry the gtag config command, and Google recommends a gtm init trigger instead, which can still be set to wait for a config command for legacy setups. The Help doc frames the upgrade in future tense; Marvin describes the rollout as already under way.
Delivery Optimization Stays Opt-In
Sending data directly to Google destinations, instead of loading gtag.js to relay it, is the piece that asks for action. Google is direct: “no changes will be made automatically, and you can choose whether to adopt the new configuration.” Anyone with edit, approve, or publish permissions will be able to start the flow from the optimization banner and “preview all changes after completing the optimization flow before publishing them to your workspace.” Google’s stated reason: containers “will be able to send data directly to Google destinations, resulting in a faster website performance,” where previously Tag Manager “loaded extra JavaScript (gtag.js) to send data to a Google destination, which could cause latency in measurement transmission.” Worth checking first: account links to destinations are created automatically during optimization, and “‘Read’ access is granted by default.”
| Change | Status | What it means |
|---|---|---|
| Redesigned Overview, Settings, Advanced tabs | Automatic | No setup needed; interface reorganized |
| Google tag upgraded to full container | Google-initiated, no behavior change | In-page behavior unchanged; each destination keeps its tag |
| Direct-to-Google delivery | Opt-in | From the optimization banner; previewable first |
| Visual, no-code tagging | Beta | Google Ads purchase conversions only |
Visual Tagging Stays in Beta, and It Isn’t New
The no-code piece lets someone “select elements directly on your website to define events, while the system handles the technical configurations such as selectors and triggers in the background.” It is not new: this site covered the Visual Event Builder in the June 29 interface refresh, already in beta and scoped to Google Ads purchase conversions. The August 20 note adds direction: the feature “will be progressively rolled out for additional use cases throughout the year.” June’s visible part was the interface; August 20 is Google’s formal write-up of the unification behind it, and of the optimization flow that drops the extra gtag.js load. As the feature expands to more use cases, events defined by clicking through a page will still need GA4-conformant names; inimino’s GA4 Event Name Generator checks names against the 40-character limit and snake_case convention.
What to Check Before You Click Optimize
Barry Schwartz’s read for Search Engine Roundtable matches Google’s framing of the interface change: “The functionality is unchanged but it does make it easier to set up…” Unchanged functionality still leaves things to review. Before running the optimization flow, use the preview step to confirm each destination still fires its own tag and that triggers survived the move, then check who holds the Read access the optimization grants by default. The optimization is not forced: Google says no changes will be made automatically, and Google’s Ads Liaison describes the banner as coming soon.