Skip to content
Theme
OnDevice Tools

Internet & SocialSearch & Google

Google Tag Manager features arrive in every Google tag

A Google release note dated 17 November 2026 confirms that each Google tag now becomes a Tag Manager container. Sites on unsupported installations will be upgraded in January 2027.

Illustration of a Google tag code snippet turning into a Google Tag Manager container

Key takeaways

  • Google's release note of 17 November 2026 says each Google tag now becomes a Google Tag Manager container.
  • Sites that only use the Google tag gain Tag Manager's interface-driven tagging, debugging and version control.
  • New deployment snippets are identical and drop the gtag config command, with initialisation triggers used instead.
  • Unsupported installations are due to be upgraded in January 2027, and Google advises preparing before then.
In this article
  1. What changed on 17 November
  2. From two tools to one
  3. Snippets and the gtag config command
  4. Permissions and Tag Assistant
  5. Who is affected and what to do next

What changed on 17 November

Google has published a release note dated 17 November 2026 that sets out how the Google tag and Google Tag Manager now work as one system, according to Search Engine Roundtable. The note is titled Google tag and Google Tag Manager unification.

Under the change, every Google tag becomes a Tag Manager container. A container is the unit that holds tags, triggers and settings for a website. Google says it is moving the full set of Tag Manager capabilities into the Google tag. The company first announced the plan in August.

From two tools to one

Google Tag Manager is the fuller of the two products. It offers interface-driven tagging, where tags are set up through screens rather than by editing page code, plus debugging to check whether tags fire correctly and version control that keeps a history of changes. The Google tag is the shorter snippet that sends page data to Google destinations.

The release note says websites that only use the Google tag will now be able to use those Tag Manager features. Advertisers gain the option to use them rather than being moved onto them. Google also says the way tags behave on the page itself will stay the same, and that every Google destination gets its own tag, which preserves existing setups and the triggers used for automation events.

Snippets and the gtag config command

Every new deployment snippet will now be identical, and none of them will include the gtag config command. Google recommends setting initialisation behaviour through the standard Tag Manager initialisation triggers instead.

There is a route for older configurations. The initialisation trigger can be set to hold the tag until the config command arrives, which Google offers as a way to keep a legacy setup working. Anyone with commands written into their page code should review them before switching.

Permissions and Tag Assistant

Illustration: AI, Google logo, settings, update and the labels Google, Google Tag, Google Tag Manager

Permission settings from Google Tag Manager will now apply everywhere. That includes Tag Assistant, Google's tool for inspecting the tags on a page, where data access will follow the container permissions already set in Tag Manager.

The effect is that tag access is governed in one place rather than separately for each tool. Agencies and site owners who manage access for several colleagues should check that the correct accounts hold the correct container permissions.

Who is affected and what to do next

Site owners, marketers and agencies that manage tags on their pages are the groups affected by the unification. Google says anyone on an unsupported installation will be upgraded in January 2027, and advises making changes before that date.

Because on-page behaviour is unchanged, visitors to a site should notice no difference. The work sits in configuration and access: checking triggers, confirming container permissions and testing that data still reaches each destination. Google's own release note and its Tag Manager help pages carry the full technical detail.

Sources

  1. Google Tag & Google Tag Manager UnificationSearch Engine Roundtable

Tags

Spotted a mistake? See our corrections policy. Read how News by OnDevice works in our editorial policy.