Home › Guides › Google tag and Tag Manager
Google tag and Google Tag Manager: what the unification changes
Google is merging the two: every Google tag becomes a Tag Manager container, with version control and debugging. What your tags do on the page does not change. The one hard deadline: sites loading a G-, AW- or DC- ID through the GTM snippet get the upgrade in January 2027 and should fix it before then.
For years the question was simple: hard-code the Google tag for Google Ads and GA4, or install Google Tag Manager and manage everything from one interface. Google tag and Google Tag Manager were two products with two snippets, and most comparison articles still treat them that way.
That answer has changed, because Google is folding the Google tag into Tag Manager. This guide covers what changes, which set-ups need fixing, and which one I would run on a UAE lead-gen site. Platform details come from Google's help pages, re-read on the day of writing.
How Google tag and Google Tag Manager differed until now
The Google tag (gtag.js) sends data to Google products only, while Tag Manager can also run third-party and custom tags. Google's own comparison, Google Tag Manager vs. gtag.js, sets out the split, and the last row is what changes now:
| Google tag (gtag.js) | Google Tag Manager | |
|---|---|---|
| Snippets | One on every page | Two on every page |
| Sends data to | Google services only | Google, third-party and custom tags |
| Managed in | Google Ads or GA4, which generate the tag for you | The Tag Manager interface, without code changes |
| Best fit | Marketers without a web developer on hand, or on a CMS (Google's words) | Sites that also run non-Google tags |
| After the unification | Becomes a Tag Manager container with debugging and version control | Optional container optimisation; nothing changes automatically |
In practice that meant small sites ran the Google tag, and anyone who also needed the Meta Pixel, a call tracking script or a WhatsApp click event moved to Tag Manager. Many sites ended up with both, which is where most of the problems I find start.
What the unification changes
Google's page on updates to Google tag and Google Tag Manager says your Google tags "will be upgraded to fully capable Google Tag Manager containers". The Tag Manager release note of 17 November 2026 confirms it.
- New features for Google-tag-only sites. Interface-driven tagging, debugging and version control, the parts of Tag Manager that used to need the second product.
- No change on the page. Google says the upgrade will not change the in-page behaviour of the Google tags. Each Google destination (your GA4 property, your Google Ads account) gets its own tag, so existing settings and automatic event triggers are kept.
- One snippet for everyone. New deployment snippets will all be the same and will not contain the gtag config command. Google recommends controlling when tags start with Tag Manager's Initialization trigger, which can also wait for a config command to keep a legacy set-up working.
- Access follows Tag Manager. Access to data in Tag Assistant will be managed through the container permissions you use in Tag Manager.
Google gives no date for supported installations. Its only published date, January 2027, is for unsupported installs.
The container ID now decides what can run
The ID on your snippet now sets the limits: a GTM- ID can run any tag type, while a G- or AW- ID can run Google tags only. Google's page on managing tagging behaviour using the container ID spells it out:
- GTM- prefix. Any tag type, including third-party scripts and custom HTML or JavaScript tags.
- G- or AW- prefix. Google tags only, sending data to Google services and blocking everything else.
Since a July 2026 change, this holds whatever path loads the container. So a Meta Pixel or custom HTML tag can sit in the interface and still never run, because the page loads its container with a G- ID. To lift the limit, Google says to replace the ID on your site with the container's GTM- ID, which you find in Tag Manager under Admin, then Install Google Tag Manager.
Unsupported installs: fix them before January 2027
An unsupported installation is the Tag Manager snippet (gtm.js) loading a G-, AW- or DC- ID with gtag('config') commands, and Google upgrades these in January 2027. Google's page on how to set up your Google tag installation correctly for gtag.js calls this "an unsupported implementation" and says such sites may see unexpected changes in tag behaviour. Users on these containers were sent an email, so check the inbox of whoever set up your tracking. If this section reads like code to you, forward it to the person who built your site.
A related change came first. Google's release note of 8 October 2026 says every gtm.js snippet starts on container load, regardless of any gtag('config') commands. Config commands now appear in the data layer as gtag.config events, and Google warns that tags on wildcard custom event triggers may start firing on them.
Google's fix depends on what else the site runs:
- Google tags only. Copy your Google tag ID (in GA4: Admin, Data streams, your stream, Configure tag settings; in Google Ads: Tools, Data manager, Google tag, Manage). Remove the gtm.js snippet and its gtag('config') lines, then paste the standard gtag.js snippet right after the opening head tag on every page.
- Third-party tags too. Keep the Tag Manager snippet but load it with your GTM- ID instead of the G-, AW- or DC- ID, and set up the Google tag inside Tag Manager.
- Check it. In Tag Assistant (tagassistant.google.com), add your domain and confirm your tag ID shows under Google tags found. Or open Chrome DevTools, Network tab, and confirm requests go to googletagmanager.com/gtag/js rather than /gtm.js.
Google's pages do not say what happens to an unsupported install that is still unchanged in January 2027. I would not wait to find out on a site whose leads you pay for.
Already on Tag Manager? The optimisation banner
Existing Tag Manager users get an optional "Optimize your Tag Manager container" banner, and Google says no changes are made automatically. Its guide to optimising your Tag Manager container lists what the flow does:
- Settings move to one place. Google tag settings go into a new Settings tab. Event tags and triggers stay as they are.
- Less JavaScript. The container sends data straight to Google destinations instead of loading gtag.js as an extra library.
- Account links. Your GA4 and Google Ads accounts are linked to the container, with Read access by default.
You need edit, approve or publish permission to start it. If your Google tags share the same settings you click Review details; if they conflict you choose which settings to keep. Either way, the changes land in a workspace. You can preview them, test in Preview mode and roll back a version if something breaks. Permissions are not versioned, though, so a rollback does not undo access changes; edit those under External Account Links in the container's admin.
Which should you use now? A rule for lead-gen sites
After the unification, the real question is how many places your tags live. This is the rule I use:
- Google tag on its own if the site only sends data to GA4 and Google Ads, with no other platforms planned and no one to maintain a container. You still get version control and debugging once the upgrade reaches your tag.
- One Tag Manager container with a GTM- ID if you also run the Meta Pixel, TikTok, call tracking, WhatsApp click events or form tracking that feeds a CRM. That is most UAE lead-gen sites I see.
- Never both for the same ID. A G- tag hard-coded by a theme or plugin plus the same tag inside Tag Manager means page views and conversions can be counted twice. Pick one route per ID.
Running Google Ads and GA4 together still needs only one Google tag: Google's set-up guide says to add the second product as a destination.
What I see in UAE accounts: tracking set up by several people over the years. A developer added the G- tag in the theme, an agency added Tag Manager, and someone else installed the Meta Pixel through a plugin. The container often sits in a former agency's account. With Tag Assistant access now following container permissions, find out who owns the container before you touch anything else.
The check order
- List what loads. Run Tag Assistant or the Network tab on your homepage and your thank-you page. Note every googletagmanager.com request and its ID (GTM-, G-, AW-, DC-).
- Fix any unsupported install: gtm.js carrying a G-, AW- or DC- ID. Move it to gtag.js or to your GTM- ID before January 2027.
- Remove duplicates, so each ID loads through one route only.
- Check wildcard custom event triggers in Tag Manager, since gtag.config events can now fire them.
- Check who has access. In Tag Manager admin, review users on the account and container, and remove people who no longer work on the site.
- Run the optimisation in a workspace, preview it, and test every conversion: the Google Ads lead conversion, GA4 key events and any Meta events that run through the container.
- Recheck the next day in Google Ads and GA4 that conversion counts look normal before making further changes.
If the list in step 1 surprises you, fix your ad tracking first, before more ad spend. For the Google Ads side, my guide to Google Ads conversion tracking covers the conversion actions themselves, and Google tag gateway covers serving tags from your own domain.
Frequently asked questions
What is the difference between Google tag and Google Tag Manager?+
Do I need to do anything about the Google tag upgrade?+
Can I use the Google tag and Google Tag Manager together?+
Is the Tag Manager container optimisation automatic?+
Related
Not sure what your site is loading?
Message me on WhatsApp or request a free campaign audit. I'll check which Google tags and containers your site loads, whether any install is on Google's unsupported list, and whether your conversions are counted once.