Back to blog
    Google Ads

    Google Tag Manager Unification: Every Google Tag Is Now a Container

    Thomas Walker 20 November 20267 min read
    Google Tag Manager Unification: Every Google Tag Is Now a Container

    Google has confirmed that every Google tag is becoming a Google Tag Manager container. If you installed Google Ads or Google Analytics by pasting the standard snippet into your site and have never opened Tag Manager, this still reaches you. The Google Tag Manager unification moved from plan to fact on 17 November, when Google added it to the Tag Manager release notes, and it comes with a January 2027 date for sites Google considers set up incorrectly.

    Most advertisers will not notice anything on their website. A smaller group will, and the timing, a week before Black Friday, is awkward. Here is what has changed and what you should check.

    What Google actually announced

    The release note is short. Each Google tag now becomes a Tag Manager container. Sites that only ever used the Google tag gain Tag Manager's interface, its debugging tools and version control. Google says the upgrade does not change how the tags behave on the page, and that each Google destination, such as a Google Ads account or an Analytics property, keeps its own tag along with its existing triggers.

    Three other points matter more than the headline.

    New snippets are standardised. Every new deployment snippet will be identical, and none will include the gtag config command. Google recommends handling initialisation through Tag Manager's initialisation triggers instead, with an option to wait for the config command if you need to keep an older setup working.

    Permissions move into Tag Manager. Access to Tag Assistant data will now be governed by the container permissions you already use in Tag Manager. Whoever controls users on the container controls who can see and debug your tags.

    Unsupported installations get a date. If your setup is one Google classes as unsupported, you receive the upgrade in January 2027, and Google advises fixing it before then.

    This is the end of a run of changes through the second half of 2026. PPC Land's write-up of the release note sets out the sequence: in July the container ID started to decide what a container may run, and in October Tag Manager snippets stopped waiting for gtag config commands while containers gained the option to send data straight to Google without loading extra gtag.js. The same report notes that the "Configure tag settings" link in Google Analytics data streams has started opening a Tag Manager container, so this is already showing up in accounts.

    What counts as an unsupported installation

    Google defines it on a separate help page, Set up your Google tag installation correctly for gtag.js. The problem case is a site that loads a product ID beginning G-, AW- or DC- through the Tag Manager (gtm.js) snippet and then relies on gtag config commands to set things up. Google calls that unsupported and warns that tag behaviour may change unexpectedly.

    The supported options are simple. Either use the standard Google tag snippet that loads gtag.js with your tag ID, or, if you use Tag Manager for other tags, load the container with your GTM- ID and deploy the Google tag inside it.

    We find the broken version more often than you would expect. It usually comes from a developer copying a Tag Manager snippet and swapping in an Analytics ID because it seemed to work, or from a theme or plugin that bolted its own tracking onto the site. Nobody notices, because data keeps arriving. That is exactly the kind of setup that fails quietly when Google changes the rules underneath it.

    Who should care

    If you only use the Google tag, the immediate risk is low. Your tag keeps working. What changes is where you manage it and who has access. Learn where your container lives now rather than when something breaks.

    If you already use Tag Manager, check whether your site also carries hard-coded gtag snippets alongside the container. Double installations were already a common cause of inflated conversion counts, and since October, config commands appear in the dataLayer as events, which can fire any tag sitting on a wildcard trigger.

    If an agency or freelancer manages your tracking, the permissions change is the one to think about. Plenty of businesses have a web developer running Tag Manager and an agency handling Google Ads conversions through the Google tag. Those two lines of control now meet in one container. Decide who owns it and who can publish, and make sure the business, not a supplier, holds admin access.

    What to do this week

    1. Find out how your tags are actually installed. View the source of your homepage and your thank-you or order confirmation page. Look for gtm.js and gtag/js. If gtm.js is loading an ID that starts with G- or AW-, you have the unsupported pattern.
    2. Run Tag Assistant on your key pages. Confirm the tag IDs you expect are present and that each conversion fires once, not twice.
    3. Audit access. List everyone with permissions on any Tag Manager container tied to your site. Remove former staff and old suppliers. Make sure at least one person inside the business is an administrator.
    4. Write down what you find. A one-page record of which IDs live where will save you hours later. If your conversion setup has never been properly mapped, our guide to making Google Ads and GA4 agree on what a lead is is a sensible next read.

    Our view: audit now, change things after Black Friday

    There is a temptation to tidy everything up the moment Google publishes a change. If you run an ecommerce business, resist it this week. Black Friday is seven days away, and changing how your conversion tags load just before your busiest trading period is a bad trade. If Smart Bidding loses conversions or double counts them during peak week, it will make poor decisions with the biggest budgets of your year.

    So audit now and make changes in early December. Google has given you until January. Use that time, rather than discovering in February that your conversion numbers stopped matching your sales and nobody knows why.

    Lead generation businesses with steady demand have less reason to wait. If you find the unsupported pattern, fix it this month, then check that the conversions in Google Ads still line up with your actual enquiry records.

    The wider point is that Google keeps pulling tagging closer to its ad products, and tracking that was set up once and forgotten is turning into a liability. If your Google Ads account depends on conversion data nobody has audited, that is where we would start. If the snippet problem sits in your site's template, it is a web development fix rather than an ads fix, and usually a quick one.

    Not sure how your tags are set up?

    If you cannot say how your tracking is installed or who has access to it, get in touch. We will check it and tell you plainly whether anything needs changing before January.

    #google-tag-manager
    #google-tag
    #conversion-tracking
    #google-ads
    #platform-news

    Want this handled for you? Our Google Ads team runs accounts built for leads and revenue, not clicks.

    See our Google Ads management
    TW

    Written by

    Thomas Walker

    Founder & CEO

    Founder of Atlas MKT. Performance marketer and business builder helping ambitious UK brands scale profitably.

    The Atlas Brief

    Weekly performance marketing plays from the Atlas team - Google Ads, Paid Social, CRO and SEO. No fluff.

    Related reading

    Let's Build Something That Scales

    Book a free 30-minute strategy call. We'll tell you exactly what's holding your growth back - no fluff, no sales pitch.

    Book a Strategy Call