Google Tag Manager Setup and Container Management

Google Tag Manager is a free tool that lets you add, manage and update tracking and marketing tags on your website or app without editing the site’s code each time. You install the GTM container once, then configure tags inside GTM. It supports Google and many third-party tags, and provides testing, version control and user permissions.

GTM is built on three concepts.

The data layer is a structured JavaScript object on your website that holds information for tracking, such as page type, user status, products viewed, cart contents and completed transactions. Instead of GTM scraping information from page elements, which breaks when designs change, developers push reliable data into the data layer at the right moments. A clear data layer specification is the foundation of accurate ecommerce and conversion tracking.

Hard-coded tags are difficult to track, update and remove, and they often duplicate or conflict with each other. Moving them into GTM centralises control, allows testing before changes go live, provides version history, supports consent management and reduces dependence on developers for routine changes. Migration must be done carefully to avoid gaps or double counting during the switch.

Forms are submitted in many ways: page reloads, thank-you pages, AJAX submissions without reloads, embedded third-party forms in iframes and multi-step forms. Generic form triggers often miss submissions or count failed attempts. The most reliable approach is for the website to push a data layer event only after a successful submission, or to track a genuine thank-you page. For embedded forms, we use the provider’s own tracking features or messaging events.

Single-page applications change content without full page reloads, so standard page view triggers may fire only once. Tracking requires history change triggers or, better, data layer events pushed by the application on route changes and key actions. We work with developers to add these events in a consistent way. Our Next.js development team builds websites with tracking planned from the start.

GTM supports consent settings for tags, so tags can wait for or adapt to visitors’ consent choices. A consent management platform or cookie banner updates consent states, and Google tags use consent mode to adjust behaviour. Non-Google tags can be configured to fire only after the relevant consent is granted. Correct integration respects visitors and supports compliance with data protection expectations.

Common tags include GA4 configuration and events, Google Ads conversion tracking with enhanced conversions, Google Ads remarketing, Floodlight for enterprise advertisers, the Meta pixel, LinkedIn Insight Tag, Microsoft Advertising UET, Microsoft Clarity or Hotjar for heatmaps, chat widgets and affiliate or partner pixels. Each should be justified, documented and reviewed regularly.

A well-organised container uses consistent naming, such as platform, type and action in each tag name, folders by platform or purpose, notes explaining unusual configurations, shared variables instead of duplicates and a small number of well-defined triggers. This makes the container understandable to anyone who works on it later and reduces mistakes.

GTM’s preview mode and Tag Assistant show exactly which tags fire on each action and what data they send. We test each change across key pages and devices, confirm data arrives correctly in GA4 DebugView and ad platform tools, then publish with a descriptive version name. If something goes wrong, a previous version can be restored quickly. Workspaces allow several changes to be prepared without interfering with each other.

GTM can run code on your website, so access should be controlled. Most users need only view or edit rights; publishing should be limited to trusted people. The container should belong to your business account, with agencies and freelancers given access that can be removed. Regular reviews of users and permissions reduce risk.

GTM itself is lightweight, but the tags it loads can affect performance, especially heavy third-party scripts, many pixels firing on every page and custom scripts that run inefficiently. We review tags for necessity and impact, remove unused ones, fire tags only where needed and consider server-side tagging to move some processing off the browser.

Custom HTML tags can run any JavaScript on your site. Poorly written or malicious scripts could break pages, slow performance or leak data. We minimise custom HTML, prefer built-in templates from the community gallery, review any third-party code before adding it and restrict who can publish changes. For sensitive pages such as checkout or account areas, tags are kept to the essential minimum.

Different platforms handle tracking differently. Shopify restricts scripts on checkout and uses its own customer events system for tracking in a sandboxed environment, so standard GTM implementations may not capture checkout steps without adjustments. WordPress, WooCommerce, Magento and custom sites generally allow full GTM installation with plugins or code. We choose the right approach for each platform to capture complete, accurate data.

A GTM audit reviews container structure, tag inventory, duplicate or conflicting tags, trigger accuracy, variable usage, data layer quality, consent settings, custom code risks, performance impact, publishing history and permissions. The audit report lists issues by priority and includes a clean-up plan.

These issues are common in containers we audit.

Tracking changes over time as campaigns, pages and platforms change. Without documentation, teams forget why tags exist and fear removing anything. We document the data layer specification, tag list with purposes, key events, naming conventions and change process, so tracking remains understandable and maintainable.

Ecommerce tracking depends on the website pushing structured events to the data layer, such as viewing an item, adding to cart, beginning checkout and completing a purchase, with product details, prices, quantities and a unique transaction ID. GTM then sends these events to GA4, Google Ads, Meta and other platforms in the formats each expects. A single, well-structured data layer feeding all platforms keeps numbers consistent across tools.

Enhanced conversions improve Google Ads measurement by sending hashed customer information, such as an email address or phone number provided in a form or checkout, alongside conversions. Google matches this securely with signed-in accounts to attribute conversions that cookies would miss. In GTM, enhanced conversions are configured using data layer values or page elements, with consent and privacy considerations respected.

GTM has containers for Android and iOS apps working with Firebase, but most mobile tracking today is implemented directly with the Firebase SDK and the GA4 app data stream. We recommend the approach that best fits your app architecture and team.

Costs depend on the number of websites and domains, the number of platforms and tags, data layer complexity, ecommerce and form tracking needs, consent integration, migration of existing tags, testing depth and documentation. Audits are usually priced by container size and complexity.