Unsupported Google tag setups get upgraded in January 2027

· By the Slate desk

On 17 November 2026 Google added a new entry to the Google Tag Manager release notes: the merger of its two site measurement tools is now being applied. Every Google tag, the snippet that connects a website to Google Ads and Google Analytics, becomes a full Tag Manager container. The same note sets one date. Sites with what Google calls an unsupported installation "will receive the upgrade in January 2027," and Google advises them to fix their setup before then.

Most small business owners have no idea how their tag was installed. A web designer pasted it in years ago, or a freelancer who set up the first campaign, or a WordPress plugin. That is where the problem installation tends to hide, and the first sign of it is usually a conversion count that suddenly behaves differently.

A copied snippet Google stops supporting

According to the Tag Manager help center, an unsupported installation is a site that loads a Google tag ID starting with G- (Analytics), AW- (Google Ads) or DC through the Tag Manager snippet, gtm.js, followed by a gtag config command. It happens when someone copies the Tag Manager code but puts an Analytics or Google Ads ID into it instead of an ID that starts with GTM-.

Until now that combination worked, because the Tag Manager snippet waited for the config command and ran it. Google says Tag Manager snippets will be updated to stop recognizing or waiting for that command, and that sites using this setup "may experience unexpected changes to their tag behavior." Owners of containers identified as affected were notified by email. If the account sits under an old address, or an agency opened it, that email may never have been seen.

Everyone else keeps their tracking

For correctly installed tags, Google says the in-page behavior does not change. The difference is on the management side. A site that uses only the Google tag gains Tag Manager's tools: setting up tags from the interface without touching code, a debug mode, and version history to roll back to. Each Google destination, such as a Google Ads account and an Analytics property, gets its own tag, and existing settings and automatic event triggers are kept.

New installations change too. All new snippets will be identical and will no longer include the config command. Google recommends handling start-up behavior with Tag Manager's standard Initialization trigger. Tag Manager permissions now apply across the board, so data in Tag Assistant is visible to whoever has access to the container.

Google first announced the merger on 20 August 2026. What started now is the rollout, and the only date Google has attached to it is January 2027 for unsupported installs. Nothing in the announcements limits the change to particular countries, so it applies to sites everywhere, Israel included.

A five-minute check

The simplest test is Google's Tag Assistant at tagassistant.google.com. Add your domain, click Connect, and check that the right ID appears under the tags found, with a green or blue icon.

To check by hand, open the site in Chrome, press F12, go to the Network tab and reload. A correct Google tag install sends requests to googletagmanager.com/gtag/js. If you see a request for gtm.js and you have no GTM- ID at all, that is most likely the setup Google means.

Two ways to fix it

Google spells out the fix in its help center. If you don't use Tag Manager for anything else, replace the code with the standard Google tag snippet. Find the ID in Google Ads under Tools, Data manager, Google tag, or in Analytics under Admin, Data streams, Configure tag settings. Delete the gtm.js snippet and the config commands tied to it, and paste the new code immediately after the opening head tag on every page.

If you do use Tag Manager for other tags, a Meta pixel for example, keep the Tag Manager snippet, swap in your container's GTM- ID, and set up the Google tag inside Tag Manager.

On Wix, Shopify or a WordPress plugin, the tag usually goes in through a settings field rather than by hand, so check which ID was entered and where. Check again after the fix. A change like this does not break the site, it breaks the measurement. If your campaigns suddenly look as if they bring in no leads after January, the tag install belongs near the top of the list, before you start working out why the website brings no leads.

The numbers that depend on the tag

This tag is what records conversions in Google Ads, and automated bidding uses those conversions to decide what to pay per click. A tag that stops sending them leaves the campaign learning from missing data. It also feeds Analytics, which is where you tell visits from Google Search apart from every other source. One check now saves a month of skewed data at the start of 2027.

For a business in Israel the picture is the same as anywhere else: the Google Ads and Analytics accounts are global, the help pages apply as written, and an agency-built site is worth checking first, since that is where copied snippets most often end up.

Ready to issue your first invoice?

Slate is free to use with no limits, Israel Invoice integration included. No credit card, no trial that runs out.

Open a Free Account