On November 17, 2026, Google said every Google tag is becoming a Tag Manager container, and that sites with an "unsupported installation" will be upgraded in January 2027. The unsupported install is specific: a Google Analytics (G-), Google Ads (AW-) or Floodlight (DC) ID loaded through the Tag Manager snippet, gtm.js, instead of the Google tag snippet, gtag.js. It is an easy mistake when you add tracking to your own Next.js or AI-built app, because the Tag Manager component and the Google Ads ID look like they belong together. This guide is for a founder who set up Google Ads conversion tracking themselves. It shows how to tell in two minutes which install you have, how to switch, and how to confirm Google Ads still records conversions. It is useful without a Soloop account.
The short answer
Open your site with your browser's developer tools on the Network tab and look for requests to googletagmanager.com. If you see gtag/js?id=AW-… or gtm.js?id=GTM-…, your install is one Google supports. If you see gtm.js?id=AW-… (or G-… or DC-…), it is the unsupported one: replace it with the Google tag snippet, or with a Tag Manager container that has its own GTM- ID.
Then place a test conversion and check three things: Tag Assistant finds your tag, the browser sends a request to googleadservices.com when the conversion fires, and the conversion action's status in Google Ads looks healthy within 48 hours. Do it before January. Google has not said which day the upgrade arrives, and ad spend with broken conversion data teaches your bidding the wrong lesson.
What Google changed, and when
The change has arrived in steps across Google's Tag Manager release notes. For a correctly installed tag, Google says the in-page behavior does not change: you gain Tag Manager features such as version control and debugging if you want them. The risk sits with installs that mix the two snippets.
| Dimension | What Google said | What it means for you |
|---|---|---|
| July 9, 2026 | The ID in the snippet decides what a container may run: a GTM- ID is unrestricted, a G- or AW- ID permits only tags and variables provided by Google. Administrators of heavily affected containers were emailed. | A container loaded with an AW- ID cannot run your other scripts. |
| October 8, 2026 | gtm.js containers start when they load, regardless of any gtag('config') commands, which now appear in the data layer as gtag.config events. | Tags that waited for a config command no longer do; wildcard custom event triggers may fire on those events. |
| October 12, 2026 | Tag Manager containers can send data straight to Google products instead of loading gtag.js to do it. | Fewer scripts for GTM users; nothing to do for a correct install. |
| November 17, 2026 | Each Google tag becomes a Tag Manager container; new deployment snippets are identical and omit the config command; Tag Assistant access follows container permissions. | New snippets you copy from Google will look different from your old one. |
| January 2027 | Unsupported installations receive the upgrade and are "advised to adjust your setup before then". No exact date is given. | Fix a gtm.js snippet that carries a G-, AW- or DC ID before January. |
Find out which install you have
- Open your site in Chrome in a private window, so extensions and earlier sessions do not interfere.
- Open developer tools, choose the Network tab, reload the page and type googletagmanager in the filter box.
- Read each request's path and ID: gtag/js?id=… or gtm.js?id=….
- In your code, search for gtm.js, gtag/js, GoogleTagManager and gtmId to find where each one is added. Also check any "tracking" or "custom code" field in your site builder or plugin.
- Optionally, open tagassistant.google.com, add your domain and look at the "Google tags found" header for your tag ID with a green or blue status icon.
| Dimension | What it means | What to do |
|---|---|---|
| gtag/js?id=AW-… (or G-…) with gtag('config', …) on the page | The standard Google tag snippet. Supported. | Nothing for January. Make sure it loads once, not twice. |
| gtm.js?id=GTM-… with the Google Ads tag set up inside the container | A normal Tag Manager install. Supported. | Expect an optional "optimize container" prompt; Google says no changes are made automatically. |
| gtm.js?id=AW-…, gtm.js?id=G-… or a DC ID | The unsupported installation Google describes. | Switch to the gtag.js snippet, or to a container with a GTM- ID. |
| gtm.js?id=GTM-… plus a separate gtag('config', 'AW-…') in your page code | Not the unsupported pattern, but the October 8 change means Tag Manager no longer waits for that config command. | Load AW- with its own gtag.js snippet, or move it into the container as a Google tag. Then test. |
Next.js and AI-built apps
In Next.js, the GoogleTagManager component from @next/third-parties loads gtm.js. The Next.js documentation describes its gtmId as "Your GTM container ID. Usually starts with GTM-", and calls the library experimental. Passing a Google Ads ID, as in gtmId="AW-123456789", therefore loads gtm.js with an AW- ID: the pattern Google calls unsupported. Neither Google nor Vercel says this in so many words, so confirm it in the Network tab. A 2024 Vercel community thread describes this exact setup failing to record page-load conversions until the poster switched to the gtag.js snippet.
If an AI app builder or coding agent added tracking for you, it may have made the same choice. Search the code it generated for the strings above, ask it to switch to the snippet below, and read the diff before you publish. Keep one method: Google's Ads help recommends consolidating to a single tracking method if you use more than one.
Verify that Google Ads still records conversions
- Deploy the change, then open the site in a private window with the Network tab open.
- Confirm the page requests googletagmanager.com/gtag/js (or gtm.js with your GTM- ID) and no longer gtm.js with an AW- ID.
- Complete the action you count as a conversion, such as a test signup, using your own email address.
- Filter the Network tab for googleadservices and check that a request appears at that moment. Google names requests to googleadservices.com as the check for Google Ads.
- In Tag Assistant, confirm your tag shows a green or blue status.
- In Google Ads, open Goals > Conversions and check the action's status over the next 48 hours. Google lists Active, Needs attention, Misconfigured and Awaiting conversions; it says statuses can take up to 48 hours to update and some status details are still rolling out.
- Delete or exclude your test signup from your own product records so it does not inflate real numbers.
Worked example
Illustrative, not real data. A founder runs a $20-a-day Google Ads search test, about $600 over 30 days, for a Next.js app. Their layout contains <GoogleTagManager gtmId="AW-123456789" />, and the Network tab shows gtm.js?id=AW-123456789: the unsupported install.
They replace it with the gtag.js snippet, keep the conversion event on the post-signup page, deploy, and sign up with a test address. The Network tab shows gtag/js?id=AW-123456789 on load and a googleadservices.com request on signup. Tag Assistant shows the tag in green. Two days later the conversion action is Active. The fix took under an hour, against a month of spend that would otherwise be judged on conversion data the founder could not trust.
Checklist before January 2027
- The Network tab shows no gtm.js request carrying a G-, AW- or DC ID.
- Each Google tag ID loads once, through one method.
- If you use Tag Manager, the snippet carries your GTM- container ID.
- Tags in your container do not depend on waiting for a gtag('config') command, and wildcard custom event triggers were tested.
- A test conversion sends a googleadservices.com request, and Tag Assistant shows green or blue.
- The conversion action in Google Ads is Active, or Awaiting conversions only because no real conversion has happened yet.
- The conversion event sends a unique transaction ID so reloads are not double-counted.
Where Soloop fits
Soloop does not install, audit or fix website tags or conversion tracking. Check and fix your tag with the steps above whether or not you use Soloop.
According to the Soloop manual, Soloop can research buyers and keywords with sources, draft and send outreach through a connected Gmail account, publish X posts and prepare Google Ads search campaigns after setup and payment, with actions waiting for your approval by default. Working conversion tracking is what lets you judge any such campaign.
Sources, limitations and refresh
Google's Tag Manager release notes (July 9, October 8, October 12 and November 17, 2026 entries), the Tag Manager help pages on the Google tag update, container ID behavior and correct gtag.js installation, the Google Ads help pages on conversion tracking with the Google tag and on conversion statuses, and the Next.js third-party libraries guide were read on November 21, 2026. Google gives no exact January 2027 date and no date for when gtm.js stops recognizing gtag('config') commands; its pages call the recommended trigger both "Initialization" and "gtm init". The code is illustrative and was not run against a Google Ads account. This guide is editorial guidance, not a statement from Google or Vercel.
This guide will be reviewed by February 21, 2027, or sooner if Google publishes the January date or changes which installs it supports.
"Each Google tag becomes a Tag Manager container"; the upgrade "won't change the in-page behavior of the Google tags"; new snippets omit the gtag config command; unsupported installations "receive the upgrade in January 2027".
Tag Manager release notes, November 17, 2026A G-, AW- or DC ID deployed through the gtm.js snippet is unsupported; gtm.js "will soon" stop recognizing gtag('config'); owners were emailed. Verify with Tag Assistant and with requests to googletagmanager.com/gtag/js and googleadservices.com.
Tag Manager Help: Set up your Google tag installation correctly for gtag.jsA GTM- ID allows all tag types; a G- or AW- ID is limited to Google tags, "regardless of the installation path you use."
Tag Manager Help: container ID behaviorTag Manager users are prompted to optimize containers; "no changes will be made automatically".
Tag Manager Help: Updates to Google tag and Google Tag ManagerThe event snippet sends send_to 'AW-CONVERSION_ID/CONVERSION_LABEL' with value, currency and transaction_id; consolidate multiple tracking methods; statuses may take up to 48 hours to update.
Google Ads Help: Use the Google tag for Google Ads conversion trackingActive, Needs attention, Misconfigured, Awaiting conversions and Removed; some status details are gradually rolling out.
Google Ads Help: conversion status troubleshooter@next/third-parties is experimental; GoogleTagManager's gtmId is "Your GTM container ID. Usually starts with GTM-"; its script URL defaults to gtm.js.
Next.js docs: Third Party LibrariesThe Soloop manual describes research with sources, Gmail outreach through a connected account, X posting and Google Ads search campaigns after setup and payment; approval comes first by default. It does not install or audit website tags.
Soloop product manual