Paid ads
Google tags are becoming Tag Manager containers. Check your conversion tracking before January 2027
Google says each Google tag now becomes a Tag Manager container. Setups it calls unsupported get the upgrade in January 2027, so check yours now.
By Umair Suleman · Published
Google is folding the Google tag (gtag.js) into Google Tag Manager. In a Tag Manager release note dated Tuesday, November 17, Google said "each Google tag becomes a Tag Manager container." Search Engine Roundtable and PPC Land both reported the note later that day.
In plain terms: a website that only uses the Google tag, the snippet many small businesses paste in to run Google Ads conversion tracking or Google Analytics 4, gets Tag Manager's interface-driven tagging features, debugging and version control without installing Tag Manager separately.
What Google says changes, and what doesn't
- In-page behavior stays the same. "This upgrade won't change the in-page behavior of the Google tags," the release note says. Each Google destination, such as a Google Ads account or a GA4 property, keeps its own tag, "preserving your existing setup and triggers for automation events."
- New snippets drop the config command. All new deployment snippets will be identical and "won't have the gtag config command." Google recommends controlling start-up behavior with the standard Tag Manager Initialization triggers, which can also be set to wait for the config command if you want to keep a legacy setup.
- Permissions move to Tag Manager. Access to data in Tag Assistant will be managed through the same container permissions used in Tag Manager today.
- Unsupported installations get a deadline. If your setup is one Google considers unsupported, "you'll receive the upgrade in January 2027, and are advised to adjust your setup before then."
The release note links to a separate help page that defines unsupported setups. PPC Land reports that the page describes loading Google Ads (AW-), Analytics (G-) or Floodlight (DC-) IDs through a Tag Manager container script while also firing gtag('config') calls as unsupported. An earlier release note, from October 8, already said Tag Manager containers start on load regardless of gtag('config') commands, and that those commands now show up in the data layer as gtag.config events.
Google has not said when the conversion of supported tags will finish, which Tag Manager account will hold the new containers, or what happens to an unsupported setup that isn't fixed by January.
What this means for your business
For a small business that pasted one Google snippet on its site and never touched it again, Google says nothing visible should change. The risk sits in the middle: sites where a web developer, a website plugin and an agency each added tracking over the years. Those are the sites most likely to mix a Tag Manager container with hard-coded gtag config calls, the pattern PPC Land says Google calls unsupported.
Why it matters: conversion tracking feeds Smart Bidding, Performance Max and the AI-driven campaign types Google keeps pushing. If a January change makes a purchase, call or form tag fire twice, or stop firing, bidding learns from bad data right when many businesses reset budgets after the holidays. Double-counted conversions look like good news until the bank statement disagrees.
The permissions change is the quiet one. If a former freelancer or agency still has access to your Tag Manager account, that access now matters more, because it covers the tags that decide how your ad money is spent. This is a good moment to know exactly who can edit them.
There is an upside. Small sites get version history and a preview mode, so a broken change can be rolled back instead of guessed at. That is the kind of tracking hygiene we build into our conversion optimization work.
What to do this week
- Find out what's on your site. Run Tag Assistant on your homepage, a service or product page and your thank-you page, and write down every ID that loads (GTM-, G-, AW-, DC-).
- Look for doubled setups. If you see a GTM- container and a separate hard-coded Google tag sending the same IDs, ask your developer whether your site matches the pattern Google calls unsupported, and fix it before January.
- Record a baseline. Note last week's conversions by action in Google Ads and key events in GA4, so a sudden jump or drop after the upgrade stands out.
- Audit access. Review the users on your Tag Manager account and remove anyone who no longer works with you.
- Put a January test on the calendar. Submit a real form or a test purchase in the first week of January and confirm it records once. If you'd rather hand this off, our paid media team checks tracking before it touches bids.
Sources
Languages: Español · 日本語 · Português · Bahasa Indonesia · Français · Deutsch · Nederlands