Data Foundations · Tag Management
We audit, rebuild and maintain your Google Tag Manager container so every tag has one job, one trigger and the right consent check, and every release is tested before it reaches your customers.
Why it matters
Google Tag Manager (GTM) decides which marketing and analytics tags load, when they fire and what data they send. It's also where most stores accumulate years of tags from past agencies, abandoned tests and apps nobody uses. Each extra tag can slow pages, duplicate conversions or fire before the visitor has made a consent choice.
We treat the container like a codebase: inventoried, named, versioned and reviewed. The result is a container your team can read and a tag setup your ad platforms can trust.
Before and after
How we work
Every tag, trigger and variable in GTM, plus every pixel loaded outside it by the theme or apps. We mark what's used, duplicated or dead.
For each event we pick one source: an app, the container or a server-side tag. That decision is written down so it doesn't drift.
Tags rebuilt on clean data layer events with consistent naming, folders and notes. Old tags are paused first, then removed.
The CMP loads on the Consent Initialization trigger, Google tags use built-in consent checks and non-Google tags wait for the right category.
GTM preview, Tag Assistant and test orders under accept, reject and Global Privacy Control states, before anything is published.
Published as a named version with notes, plus a short guide to the container for your team.
What we manage in GTM
One Google tag, ecommerce events from the data layer and shared event settings.
Purchase conversion with enhanced conversions, plus remarketing, with clear primary and secondary actions.
Pixel events matched to the same data layer, with event IDs ready for server-side deduplication.
CookieYes, OneTrust or Cookiebot templates feeding Consent Mode and controlling every other tag.
Platform notes
On Shopify, GTM usually runs in two places: the theme for storefront pages, and a custom pixel for checkout events through Shopify's customer events. The custom pixel runs in a sandbox, so it can't read the storefront's data layer and works from Shopify's own event payloads instead. The common mistake is letting the theme container and the pixel both send purchases. We split responsibilities so each event has one sender. See our Shopify work.
WooCommerce stores often load GTM through a plugin that also builds the ecommerce data layer. That works well, as long as caching plugins don't serve stale data and no other plugin injects its own GA4 tag. More on WooCommerce.
On Magento, GTM is added through an extension or theme. Customer-specific values must load outside the full-page cache, or the data layer serves one shopper's cart to another.
Related services
GTM can only send what the data layer gives it, so we usually fix both together. For conversions lost to blockers and browser limits, we add a server-side container next to your web container. Consent behavior is covered by Consent Mode v2. Once conversions are right, check your targets against margin with the break-even ROAS calculator. All part of Data Foundations.
FAQ
Not always. Shopify's apps and customer events can cover basic GA4, Google Ads and Meta tracking. GTM earns its place when you run several ad platforms, need custom events, want consistent consent handling across tags, or plan to add server-side tagging. Whatever you choose, avoid running app pixels and GTM tags for the same event.
The container itself is light. What slows pages is the number and weight of tags it loads. A cleanup often removes tags nobody uses and replaces click-based triggers with data layer events. We check page speed before and after, against Core Web Vitals targets such as INP at or below 200 milliseconds.
Your company should. The container should sit in your own Google account, with agencies added as users. We work in our own workspace, publish named versions and remove our access when an engagement ends, so you keep full control and history.
Your consent management platform sets default consent states before any tag fires, then updates them when the visitor chooses. Google tags read those states through built-in consent checks. Non-Google tags get additional consent checks so they only fire when the matching category is granted. We test each state before publishing.
Start with the free audit to see which tags and pixels load on your store today, or book a call and we'll review your container with you.