Tag management
Google Tag Manager for ecommerce stores
Google Tag Manager loads marketing and analytics tags from one container, fed by a data layer the store populates with product, cart and order details. Most containers we inherit have grown by accretion: tags from past agencies still firing, purchase events duplicated between the theme and a checkout pixel, no consent configuration and versions published without notes. We rebuild the container around a documented data layer and give each event one owner.
Google Tag Manager
Tag management · by Google. A text wordmark, not a logo: we are not affiliated with the vendor and make no claim to its trademarks.
What we do with it
The work inside Google Tag Manager
A data layer specification
Before tags come events. We write the data layer for the store: page type, product and variant details, cart contents, checkout steps and the purchase with transaction id, value, tax, shipping and items. The specification is what the theme, the pixel and every tag are built against.
Checkout tracking on hosted platforms
Shopify checkout does not load the theme's container, so checkout and purchase events come through a custom pixel that runs in a sandboxed environment with its own rules. We build the pixel to publish the same event shape as the theme, and on WooCommerce or BigCommerce use the plugin or template hooks that reach the order confirmation page.
Tags with one job each
GA4, Google Ads conversions with enhanced conversions, Meta, TikTok, Microsoft UET, Pinterest and affiliate tags each get a trigger tied to a data layer event and a variable set drawn from it. No tag scrapes the page, and no event is sent by two tags.
Consent mode wired correctly
Google's consent mode needs default states set before tags load and updates when the banner records a choice. We configure the consent settings per tag, connect the banner platform, and test what fires in each consent state in the markets the store sells to.
Container hygiene and version control
Workspaces for changes in progress, version notes that say what changed and why, folders by vendor, and a quarterly removal of tags nobody can account for. Preview mode is used before every publish, with a purchase test on a real order.
Server-side when the store needs it
A server container, hosted on Google Cloud or through a provider such as Stape, receives events from the web container and forwards them to vendors from the store's own subdomain. We add it when event loss, page weight or data control justify the cost, and keep the web container as the source.
When it fits
Google Tag Manager is the right tool when
Stores running more than two marketing platforms
Once GA4, Google Ads, Meta and an email tool all need events, a container with one data layer is easier to keep correct than tags pasted into the theme.
Teams that change tags often
Launches, affiliate programs and new ad channels each need a tag. A container lets that happen without a theme deployment, with a version history to roll back to.
Shopify, WooCommerce and BigCommerce stores
Each can host the container and populate a data layer, with platform-specific handling for checkout. Headless builds can do the same with the container loaded in the frontend.
Merchants who need consent handled centrally
Consent mode and banner integration are managed once in the container rather than separately in every vendor's script.
What to watch
Where accounts drift
Facts about defaults and costs, not criticism. These are the settings we check on every account.
Every tag adds weight
Each vendor script the container loads runs on the shopper's device. Tags that fire on every page should be reviewed against Core Web Vitals, and vendors nobody uses removed.
Checkout pixels run in a sandbox
On Shopify, custom pixels have restricted access to the page and their own event API. A tag that works in the theme may need a different approach in the pixel, and testing has to happen on a real checkout.
Personal data in the data layer
Emails, names and addresses pushed into the data layer can be read by any tag in the container. Hash what is needed for enhanced conversions and leave the rest out.
Versions without notes become unrecoverable
A container with a hundred unlabelled versions cannot be rolled back with confidence. Notes and a change log are the difference between a fix in minutes and a rebuild.
Does a Shopify store still need Google Tag Manager?
It depends on how many tools need events. Shopify's native integrations cover GA4 and the Google channel without a container. A store adding Meta, TikTok, affiliates and enhanced conversions usually benefits from one, with a custom pixel for checkout.
Can Google Tag Manager track Shopify checkout and purchases?
Yes, through a custom pixel built with Shopify's pixel API. The pixel subscribes to checkout events and can load a container or send events directly. It cannot read the page like a theme script, so the setup is different from the storefront.
How do you stop duplicate purchase events in a container?
By giving each event one source. If the platform's native integration sends purchase to GA4, the container does not. We audit which tags fire on the order confirmation, then compare transaction counts with orders for a month to prove the fix.
What is in a tag manager audit?
Every tag, trigger and variable listed with its owner and purpose, a data layer check on product, cart and checkout pages, consent behaviour in each state, a purchase test, page weight from tags, and a version history review. The output is a container plan and a list of removals.
Do we need server-side tagging as well as the web container?
Not always. Server-side helps when browser events are being lost, when page weight from vendor scripts is hurting speed, or when the store wants control over what each vendor receives. We recommend it from the audit findings rather than by default.
Works alongside
Find the leak.
A free Growth Analysis ranks what your store should fix first, by revenue at stake.