Direct answer: Most sites will be fine, but unsupported installs will not be left alone. On Nov 17 Google said every Google tag becomes a Tag Manager container, and unsupported installs get a forced upgrade in January 2027. SMBs should spend 30 minutes checking how tags are installed and who owns the accounts.
On November 17, Google published "Google tag and Google Tag Manager unification" in the official Tag Manager release notes. Every Google tag (the G- GA4 tag and the AW- Google Ads tag on your site) becomes a Tag Manager container. The key line: sites with unsupported installations will be upgraded automatically in January 2027, and Google advises adjusting before then.
Why does this matter? The reach is huge. According to W3Techs data from November 18, Google Tag Manager runs on 44.3% of all websites and holds 99.6% of the tag manager market. For years the two coexisted, and many sites ran gtag.js and Tag Manager side by side. Google published the merger plan in May 2026, and since November 16 GA4's "Configure tag settings" links already open auto-created containers. This note makes it final.
The wider category is splitting. Tealium and Adobe's tag management hold large enterprises. Providers such as Stape sell server-side tagging as a monthly plan to mid-size ecommerce firms focused on privacy and ad conversions. Segment takes the customer data platform route. With this merger, Google pulls the free entry point fully into its own container, leaving one path for GA4, Google Ads and tag management.
Will Taiwan SMBs be affected? Yes, especially companies whose sites were installed by a vendor and nobody remembers how. Below: what changed, what three kinds of readers should do, a tool comparison, the risks Google has not spelled out, and a free check you can run.
The details: tag behavior stays, permissions and install methods change
The merger barely changes on-page tracking but significantly changes account permissions and legacy installs. The release note's main points:
- Every Google tag becomes a container: sites using only the Google tag gain Tag Manager's interface, debugging and version control.
- On-page behavior unchanged: each destination keeps its own tag and automatic event triggers.
- One deployment snippet: new snippets are identical for everyone and no longer include the gtag config command; Google recommends the standard Initialization triggers.
- Unified permissions: Tag Assistant data access now follows container permissions.
- January 2027: unsupported installs are upgraded automatically. Per Google's gtag.js installation guide, loading G-, AW- or DC- IDs through gtm.js while relying on gtag config commands is unsupported and may cause unexpected tag behavior.
What three readers should do now: check the install, then check who owns the account
All three readers should first confirm how tags are installed and who has access, not rush to change code.
- Brand owners and SMB owners: make sure your own company account is an administrator on GA4, Google Ads and Tag Manager. If only a vendor or a former employee has access, fix that now.
- Marketing and SEO operators: list how every site and subdomain is installed, flag pages mixing gtag.js and gtm.js.
- Developers and agencies: audit client sites you have touched, replace gtm.js-loaded G- IDs with the official standard install, and verify events and conversions with Tag Assistant.
Tool comparison: most SMBs only need the free version
Tag managers differ in cost, server-side capability and scale; companies below roughly NT$100M in revenue rarely need a paid plan.
| Tool | Positioning | Cost | Best for |
|---|---|---|---|
| Google Tag Manager (web container) | Free standard option | Free | Most SMB websites and online stores |
| Google Tag Manager server-side | Runs tags on your own server | Tool free, cloud hosting extra | Ecommerce with large ad budgets and conversion focus |
| Stape | Hosted server-side tagging | Monthly, by request volume | Teams wanting server-side without engineers |
| Tealium iQ | Enterprise tag management | Quote-based | Large multi-brand, multi-domain companies |
| Segment | Customer data platform | Priced by tracked users | Product teams unifying app, web and CRM data |
What they won't tell you: the real risk is accounts, not code
Google's note focuses on features and skips three problems that matter more to SMBs.
- Unclear container ownership: Google has not said where auto-created containers will live. If your GA4 property sits in a vendor's account, the new container likely will too.
- Tighter permissions lock you in further: Tag Assistant data now follows container permissions, so people without container access cannot even see debugging data.
- "Same behavior" is not "same numbers": on mixed installs with duplicate events, the merge may fix double counting. A drop in conversions would not mean business got worse.
The no-subscription alternative: a 30-minute tracking check
You can finish the check with Google's free tools and buy nothing.
- Read the source: open your site in Chrome, view the page source, search for googletagmanager.com and note whether it loads gtag/js?id=G- or gtm.js?id=GTM-.
- Verify with Tag Assistant: connect your site at tagassistant.google.com and confirm page views, form submissions and purchases each fire once.
- List the accounts: put the administrators of GA4, Google Ads and Tag Manager in one table and make sure at least 2 company accounts are admins.
FAQ
Do sites need to reinstall tags after the merge?
Mostly no. Google says in-page tag behavior is unchanged; only unsupported installs get upgraded in January 2027.
What counts as an unsupported install?
Loading a G- or AW- ID through Tag Manager's gtm.js snippet while relying on gtag config commands.
How do I check which install my site uses?
Check whether the page source loads gtag/js or gtm.js. Then connect Tag Assistant to confirm events fire correctly.
What if my vendor owns the GA4 account?
Ask them to add your company Google account as an administrator now; after the merge, tag access follows container permissions.
My take: this merger makes tracking-account transfer a required maintenance task
Most commentary treats the merger as a technical update for engineers. We think its real meaning for SMBs is data ownership, and many companies will discover for the first time that their GA4 is not theirs.
Before, a badly installed tag just meant inaccurate numbers. After the merger, the container becomes the single entry point for all Google measurement, and permissions concentrate with it. Whoever holds the container holds ad conversions, traffic data and debugging data. Many Taiwan SMBs had GA4 set up by their web vendor years ago; vendors changed, staff left, and the accounts became orphans. The January 2027 upgrade will move those orphans into new containers, and reclaiming them will only get harder.
For ScriptWalker (a Taiwan Laravel/Flutter custom development studio), a "tracking check plus account transfer" package is worth offering on its own: review the install, switch to the standard install, transfer ownership of GA4, Google Ads and Tag Manager back to the client's company account, and hand over a permissions list. That is an easier sale than a GEO monitoring tool, because it protects the company's own data.
Sources
- Google Tag Manager Help: Release notes (2026/11/17 unification entry)
- Google Tag Manager Help: Updates to Google tag and Google Tag Manager
- Google Tag Manager Help: Set up your Google tag installation correctly for gtag.js
- W3Techs: Usage statistics of tag managers (2026/11/18)
- Search Engine Roundtable: Google Tag and Google Tag Manager Unification (2026/11/17)
- PPC Land: Unsupported Google tag installs get the Tag Manager upgrade in January 2027 (2026/11/17)