Google Tag Manager setup, or a clean-up of the one you have.

Google Tag Manager setup starts with an audit of what already runs. We export the container, list every tag, trigger and variable, and compare it with what loads on the live store: tags in the theme, tags added by apps and tags in GTM. Tag Assistant and the browser’s network panel show which fire on each page, so duplicate tags show up straight away.

The data layer comes next. Google’s data layer guide describes it as the object that passes information from the site to Tag Manager. We push e-commerce events into it with the item data that GA4’s e-commerce measurement expects: view_item, add_to_cart, begin_checkout and purchase with transaction_id, value, currency and items. Tags then read clean data instead of scraping the page.

Every purchase gets a transaction_id, and every tag reads the same one. That lets GA4 drop duplicate purchase events, and lets ad platforms deduplicate the browser event against the server event if you also use a Conversions API. When a purchase is counted twice, the cause is almost always two tags without a shared ID, or the same tag installed in two places.

On Shopify, the checkout works differently. Shopify retired the old checkout code, and tracking on checkout and thank-you pages now runs through custom pixels in a sandbox, using customer events. We load GTM inside a custom pixel where that suits, map Shopify’s events to the data layer, and test the purchase on a real order. Our checkout tracking page covers that repair in detail.

The container gets a structure. Tags are named by platform, type and event (“GA4 · Event · add_to_cart”), triggers and variables follow the same pattern, and folders group them by platform. Each tag has a note saying what it does and who asked for it. Old tags are paused for a few weeks, then removed once nothing is missing.

Variables get the same care. Built-in variables are switched on only when a tag uses them, data layer variables use the exact key names from the agreed plan, and lookup tables replace long chains of near-identical triggers, so the container stays small enough for your team to read.

Consent is part of the build. Each tag gets the consent checks it needs, and the default consent state is set on the Consent Initialization trigger before any tag runs. If you sell to the EU or UK, our consent mode setup service covers the banner side in full.

Publishing follows a routine. Changes are made in a workspace, checked in Preview mode against the live store, and published with a version name and notes. Google’s user permissions let you limit who can publish, so we keep publish rights to one or two people and give the rest edit or read access.

Kashif builds the tracking for this site and for the stores on our tracking and analytics pages, including GA4 audits, server-side setups and Shopify checkout repairs. After the Google Tag Manager setup is done, we compare purchases in GA4 and each ad platform with real store orders for two weeks, and hand over the container document.