Google Tag Manager for ecommerce: a decision guide, not a manual
Where it sits among the other tools is on the ecommerce marketing technology stack page. Plenty of guides already teach the buttons. This page covers the business decisions around them.
What does Google Tag Manager do?
GTM holds your tags in one place, called a container. You decide when each tag fires, for example on a purchase. Then you publish the container to the site.
The benefit is control. Marketing can change tracking without waiting for a developer release. The cost is the same thing: anyone with access can break tracking, or send data somewhere they should not.
Two terms get mixed up:
- Google tag. A specific Google product, also known as gtag.js. It sends data to Google products.
- Google Tag Manager. The tool that manages tags, including the Google tag and tags from other vendors.
So "Google tag vs Google Tag Manager" is not a like-for-like choice. You can put the Google tag directly on the site, or run it through GTM. In our view, GTM adds control and more things to look after. Direct placement is simpler and less flexible.
A related piece is the Conversion Linker tag. Google's guide to Consent Mode with server-side Tag Manager says Google Ads conversion tags in a server container need the Conversion Linker tag installed there1. For the conversion side, see Google Ads conversion tracking.
Why do e-commerce brands use tag management?
Example (illustrative): a shop wants to add a new ad platform's tag before a sale starts. With GTM, a marketer adds it, tests it and publishes it. Without it, the change joins the developer queue.
Brands use it for four practical reasons:
- Tags such as a tracking pixel can be added and edited without a code release.
- Triggers can be tied to shop events, such as add to cart or purchase.
- Google features such as enhanced conversions can be configured in the tag. Google describes enhanced conversions as sending hashed first-party customer data, such as an email address, to Google to improve conversion matching2. See enhanced conversions.
- Campaign data such as UTM parameters can be read and passed on consistently.
GTM does not create data. It sends what it can read. Order values usually come from a data layer your shop provides.
How does it work with consent?
Consent Mode is how your consent banner tells Google tags what a visitor agreed to. Google's Tag Manager help describes two implementations3. In basic, Google tags do not load until the visitor interacts with the banner. In advanced, tags load and, while consent is denied, send cookieless pings that Google uses for modelling3.
Server containers can also work with Consent Mode. Google says they support both modes, and that consent is set in the web container1. So a server container does not replace getting consent right in the web container. Whether and how you may collect is a question for your counsel.
How do we implement it?
Write the plan
List the events you need and what each should send. Without a written plan, nobody can say what the container should do.
Own the container
The GTM account and container belong to you. Agencies and freelancers get access, not the account.
Clean up, then test
Explain or remove tags nobody can explain, and complete the data layer. Test every tag on key pages before publishing.
Limit publish rights
Fewer people publish. Review the container when platforms or your shop change.
What does it cost in effort?
We give no figures. The software is not where the effort goes.
- Planning. A written list of the events you need and what each should send.
- Setup. Tags, triggers, consent behaviour and a data layer.
- Testing. Every tag, on every key page, before publishing.
- Upkeep. Reviewing the container when platforms or your shop change.
- Ownership. The GTM account and container should belong to you. Agencies and freelancers should have access, not the account.
Pitfalls
Tags firing more than once
A purchase tag on the wrong trigger can count one order twice.
No consent order
Tags that fire before consent is read can send data you did not mean to send.
No documentation
Nobody remembers why a tag exists, so nobody dares remove it.
Too many people with publish rights
Fewer is safer.
Lost access
The person who built it left and owned the account.
Our take: Core
We rate GTM Core. This is our view, not a market fact.
Why Core? Google's own set-up paths run through it. Google's Consent Mode help is written for Google tag users and shows where to add consent checks in Tag Manager3. Its enhanced conversions page points to a guide for setting them up with Google Tag Manager2.
Our view: the tool is rarely the problem. A container with no documentation is.
FAQ
What is the difference between the Google tag and Google Tag Manager?
The Google tag (gtag.js) sends data to Google products. Google Tag Manager is the tool that manages that tag and others.
Do I need the Conversion Linker tag?
If you run a server container, Google says its Google Ads conversion tags need the Conversion Linker tag installed in that container1.
Who should own the GTM account?
You should. Give your agency access to the container, not ownership of the account.
Does GTM handle consent for me?
No. Google's help says Consent Mode does not provide a consent banner; it takes the choices from yours3. Your counsel decides what is allowed.
Do I need a server container as well?
Not automatically. It is a separate decision, covered on our server-side tracking page.
Should I install the Google tag directly instead?
It can work for a small, simple setup. GTM is more flexible and needs more discipline.
Sources
Let’s find what’s actually working.
Next step. Want a view on what your container should and should not contain? Talk to us about your tracking setup.