Google has announced a significant change to its measurement infrastructure: Google Tag and Google Tag Manager are being unified into a single platform, with no-code event tracking and faster data transmission. As Search Engine Land reported on 24 August, the change positions itself as a simplification: streamlined management, easier event setup, less reliance on developers.
For eCommerce merchants, this is both an opportunity and a trap. Done well, the unification removes one of the most persistent friction points in eCommerce measurement: the gap between what marketing teams want to track and what development teams have bandwidth to implement. Done poorly, or worse, ignored, it creates duplicated tags, conflicting configurations, and corrupted conversion data at exactly the moment when your measurement needs to be airtight: the final setup window before peak trading season.
What is actually changing
Before this update, eCommerce merchants typically managed two overlapping systems. The Google Tag (formerly the Global Site Tag or gtag.js) handled the direct connection between your website and Google services. Google Tag Manager (GTM) sat on top of that as a container system, letting you manage multiple tracking tags from different platforms through a single interface.
In practice, these two systems often stepped on each other. You might have a Google Tag firing GA4 events directly while also having a GTM container triggering duplicate events through its own configuration. For eCommerce specifically, this created double-counted transactions that inflated revenue data and fed incorrect signals to automated bidding systems.
The unification brings both under one roof. More importantly, it introduces no-code event tracking, the ability for marketers to configure and deploy conversion events without writing JavaScript or modifying the data layer.
Why this matters for eCommerce specifically
Ecommerce tracking is among the most complex measurement implementations on the web. A typical store needs to track product impressions, product clicks, add-to-cart events, checkout steps, purchases, refunds, and promotion interactions, each with product-level data including SKU, price, quantity, and category. When this tracking breaks, the consequences cascade.
-
The most immediate impact is on automated bidding. Google Ads Smart Bidding, Performance Max, and AI Max all depend on accurate conversion data to optimise campaigns. If your purchase events are double-counted, your Target ROAS campaigns think they are performing better than they are. With Google increasing automation across its advertising products, the quality of your conversion data has never been more consequential.
-
The second impact is on measurement velocity. Ecommerce teams routinely need to set up tracking for new promotions or product launches. Currently, this often requires a developer to modify the data layer, a GTM specialist to create the tag and triggers, and a QA process to validate the events. No-code event tracking potentially compresses this from days to hours.
The trap: migration without audit
The risk is not the unification itself. It is the transition. Merchants who have been running Google Tag and GTM in parallel need to answer uncomfortable questions.
-
Are you firing the same events from both systems? Many eCommerce stores have a Google Tag sending purchase events directly to GA4 while also having a GTM tag firing a duplicate GA4 purchase event. Under the old system, this created double-counted transactions. Under the unified system, reconciliation is needed.
-
Who owns your tracking configuration? No-code event tracking shifts power from development teams to marketing teams. That is efficient, but it also means marketers can create tracking configurations that conflict with developer-maintained implementations without either team realising it. Governance matters. You need a clear owner for your measurement configuration.
What to do right now
-
Step one: document your current setup - Before anything changes, create a complete map of every Google-related tag on your site, where it fires, what events it sends, and which Google product receives the data.
-
Step two: identify duplicates and conflicts - Look specifically for cases where the same event, especially purchase, add_to_cart, and begin_checkout, is being sent from multiple sources.
-
Step three: test the unified system in a controlled environment - Verify that conversion data flows correctly to both GA4 and Google Ads before applying changes to your production site.
-
Step four: establish a baseline - Record your current conversion rates, ROAS, and event counts for the two weeks before you make any changes. After the transition, compare against this baseline to catch discrepancies quickly.
-
Step five: define governance - Decide who is authorised to create and modify tracking events using the no-code tools. Without this, you will end up with conflicting configurations that are harder to debug because no developer was involved in creating them.
The bigger picture
Google's unification of its tagging infrastructure is, in principle, a good thing. But the transition window, happening now, weeks before peak season, requires active management. The merchants who audit, test, and validate their tracking configurations now will enter Q4 with clean data and reliable bidding signals. Those who assume the unification will "just work" may not discover the problems until their peak season data is already compromised.
About On Tap
On Tap is a growth-focused eCommerce consultancy helping mid-market and enterprise merchants build and maintain measurement infrastructure that drives confident decision-making. From GA4 implementation audits and GTM configuration reviews to conversion tracking validation and peak season readiness, On Tap helps merchants ensure their data is telling the truth.
If you want help auditing your tracking configuration before peak season, get in touch.
