Google tags become Tag Manager containers
Google’s 17 November Tag Manager release notes describe an upgrade that turns each Google tag into a Tag Manager container. Sites using the standalone Google tag gain access to Tag Manager’s…
Google’s 17 November Tag Manager release notes describe an upgrade that turns each Google tag into a Tag Manager container. Sites using the standalone Google tag gain access to Tag Manager’s interface, debugging and version control.
Google says the upgrade does not change existing tags’ in-page behaviour. Each Google destination retains its own tag and existing automation triggers are preserved. That is a reason to review the installation carefully, rather than replace working measurement code simply because the interface changes.
New snippets and initialisation
New deployment snippets will use a common format without the gtag config command. Google recommends using standard Tag Manager initialisation triggers. It also says the Initialization trigger can wait for the config command where a legacy setup needs to be preserved.
For agencies maintaining custom tagging, the practical task is to identify how each installation starts its tags and which events subsequent tags depend on. Test that sequence in the supported debugging tools before deploying a change. Do not assume that deleting a config command from an existing installation is the required migration.
Permissions and the January deadline
Tag Manager’s permission model now applies across the unified setup, including access to Tag Assistant data. Review who can inspect and modify each container, especially where several agencies or contractors have worked on the same store.
Google says unsupported installations will receive the upgrade in January 2027 and advises adjusting them beforehand. Its release notes link to guidance for those installations. Establish whether that guidance applies to your implementation; January is not a blanket instruction for every merchant to reinstall tracking.
What Shopify teams should check
List the integrations, theme code and custom pixels responsible for Google measurement, and identify an owner for each. Avoid adding a second tag simply to get the new interface. Before and after an authorised change, test the intended events and check for duplicate conversions.
A store using an app-managed integration should first follow that provider’s supported setup. A team maintaining custom code should test in a controlled environment, keep the previous configuration available and verify consent behaviour as well as purchase measurement. Schedule the work around the store’s change controls rather than making an untested edit during peak trading.
Google tag and Google Tag Manager unification todayhttps://t.co/IqRKCx1bly
— Barry Schwartz (@rustybrick) November 18, 2026
More from Marketing
See all →

