Google merges Google tag and Tag Manager into one measurement system
Google announced a series of updates to its tagging products. Google tags are being upgraded into fully capable Google Tag Manager containers, and visual tagging that creates events and conversions without writing code is in beta. Existing tags keep behaving the same way on web pages.
Two separate tagging products become one system
Per an update published in the Google Tag Manager Help Center dated August 20, 2026, Google is turning Google tag and Google Tag Manager into a more unified measurement system. The stated aims are to streamline measurement setup, improve performance and management, and provide one consistent experience across the tagging products.
At the center of the change is this: Google tags are being upgraded into fully capable Google Tag Manager containers. A site that until now used only Google tag will gain access to interface driven tagging, debugging and version control.
Per Search Engine Land reporting dated August 24, 2026, the upgrade does not change how existing Google tags behave on web pages. Measurement that already runs on the page is not disturbed, a management layer is added on top of it.
No-code visual tagging, container optimization and a new interface
The first headline in the announcement is visual tagging. This beta feature makes it possible to create events and set up conversions for Google products without manual coding. The advertiser defines the event by selecting elements directly on the site while the system handles the technical configuration. Per Search Engine Land, a flow such as a purchase can be defined by walking through it the way a customer would.
The scope is narrow for now. Per the help page, visual tagging is available only for Google Ads purchase conversions and will roll out progressively through the year.
The second headline is container optimization. Advertisers with the right permissions can optimize their containers to run faster and be easier to manage. The described benefits include tag performance from transmitting data directly to Google destinations, and simpler team access through automatic account linking.
One detail matters here: this change is not applied on its own. Per Search Engine Land, existing Tag Manager users are prompted through a new in account optimization banner, and the decision stays with the user.
The third headline is the interface. The Overview page is being streamlined, with a Settings section for container wide settings and a collapsible Advanced tab that gathers Triggers, Variables, Templates and Folders.
There is also a change in deployment snippets. Per the help page all new deployment snippets will be the same and will not include the gtag config command, with configuration handled through the gtm init trigger.
Measurement setup moves from code knowledge to interface knowledge
The assessment in this section is ours. For years conversion measurement has been work stuck between marketing and engineering. Getting a purchase event set up correctly meant joining the developer queue, which in most small and mid sized businesses meant weeks.
Visual tagging aims to shorten that wait. But removing the code does not remove the responsibility. A wrongly defined event is no less harmful than a wrong definition written in code, it is just produced faster.
The second point is data quality. Tag Manager debugging and version control have so far belonged only to Tag Manager users. Sites running on Google tag alone had no way to look back and see what changed when measurement broke. Opening version control to that group can reduce silent data loss.
The third point is timing. The rollout is progressive across the year. What appears in an account today may differ from what appears tomorrow, so the change needs to be owned by a process rather than by one person.
The fourth point is context. Measurement changes do not arrive alone, and they should be read alongside adjustments such as the Google Analytics attribution window change. What a number in your report means depends on attribution rules as much as on measurement setup.
What it means for businesses in Türkiye
The assessment below does not appear in the sources, it is our reading. The announcement mentions no Türkiye specific timeline or exception.
In Türkiye a large share of small and mid sized advertisers run on half finished measurement. Having the tag on the page is not the same as counting the purchase correctly. The pattern we see most often in the field is a conversion showing in Google Ads while the basket value is never read, or the same purchase counted twice.
No-code visual tagging can improve that picture because it shortens the distance between setup and the sales team. One caution is needed though: on ecommerce sites a purchase event rarely works correctly by selecting one element on the page, since values such as order total, currency and order number have to be read from the right source.
The second practical point is consent management. Under KVKK, advertising and analytics tags must not run before cookie consent is given. As tagging gets easier, verifying that the tag stays silent for a visitor who declined becomes more important, not less. When moving to the new container structure, consent mode settings need to be checked.
The third is ownership. Because container optimization is not applied on its own, nothing happens if it is unclear who decides when the banner appears in the account. Writing down where that authority sits between agency and business prevents data gaps later.
The fourth is test discipline. The healthiest route is applying the change on a low traffic property first and comparing conversion counts with the previous week.
The UNALSOFT take
On the advertising management side, the first thing we do is not launching a campaign, it is proving the measurement is correct. Optimizing a badly measured account means moving fast in the wrong direction. For us this announcement lowers the setup threshold, not the responsibility. When no-code tagging becomes widely available we will run the same checklist: does the event fire once, are amount and currency read correctly, does the tag stay silent for a visitor who declined consent, is the data consistent between Analytics and Ads. The interface can get easier, the verification step does not.
Is your measurement actually correct?
Let us review your conversion setup together.