Analytics
GTM built for clean data, not tag sprawl.
Google Tag Manager is supposed to make marketing measurement easier. In most implementations, it has made it worse. Tags firing on the wrong triggers. Tags firing twice. Conversion tags that nobody knows the purpose of. Variables that stopped working when the website changed. A GTM container that has been untouched for two years except to add new tags on top of broken ones. The container is not a problem until your ad platforms start optimising on the wrong data.
The GTM problems that corrupt your marketing data.
Most GTM containers are a record of every marketing request ever made, never cleaned, never audited. Here is what they contain.
Conversion tags are firing on every page, not just the thank-you page.
The Google Ads conversion tag trigger is set to "All Pages" because someone was not sure how to configure a specific trigger. Every pageview is being counted as a conversion. Google Ads has been optimising for session starts, not leads. The reported CPA is artificially low, the algorithm is reaching the wrong people, and nobody knows how many actual conversions happened.
The same event is tracked by three different tags.
GA4 via gtag.js hardcoded in the site, GA4 via GTM, and a HubSpot tracking code all firing the same purchase event. GA4 shows triple the revenue. The Google Ads conversion is duplicated in the tag and in the GA4 import. Every number in every platform is inflated by a factor nobody has calculated.
Tags from previous agency relationships are still live.
A Facebook Pixel from 2021 that belongs to an account the business no longer has access to. A Google Ads remarketing tag from a previous agency account. An old LinkedIn Insight Tag for a campaign that ended. Dead tags slowing the site, sending data to systems nobody controls, and creating GDPR and privacy compliance risk.
There is no consent mode implementation.
Google Consent Mode v2 became mandatory for ad personalisation and measurement in the EU in March 2024. Many Indian businesses with international traffic, or who sell to EU customers, are operating without Consent Mode. Without it, Google cannot model conversions for users who decline cookies, resulting in signal gaps that Smart Bidding cannot compensate for.
Custom HTML tags are running arbitrary JavaScript.
Custom HTML tags in GTM can execute any JavaScript on your site. Over time, these accumulate from various agency requests, one for a chat widget, one for a heatmap tool, one for a scroll tracker. They are not reviewed when agencies change. They are not removed when campaigns end. Some are injecting third-party scripts with no security review.
How we clean and build a GTM container.
Every GTM engagement starts with a full audit. We do not add new tags to a broken container.
Container audit
- Full tag inventory, every tag in the container listed with purpose, status, and firing trigger
- Duplicate detection, tags tracking the same event identified and marked for removal
- Dead tag identification, tags for inactive accounts, cancelled campaigns, or removed tools flagged
- Trigger audit, every trigger reviewed for correct specificity, overly broad triggers identified
- Variable audit, variables that reference broken DOM elements or unavailable data layer keys found
- Priority list, tags to remove, tags to fix, and tags to leave documented before any changes
Container cleanup
- Dead tag removal, inactive and orphaned tags deleted with change notes
- Duplicate deduplication, single canonical tag per tracking purpose retained
- Trigger correction, overly broad triggers replaced with specific event or page-based triggers
- Variable rebuild, broken variables corrected with current data layer structure or DOM selectors
- Naming convention, all remaining tags, triggers, and variables renamed to a clear standard
- Folder organisation, tags organised by tool and purpose for future maintainability
New implementation
- GA4 configuration tag, single canonical GA4 tag with correct measurement ID and shared settings
- Google Ads conversion tags, conversion-specific triggers, one tag per conversion action
- Meta Pixel and CAPI, browser Pixel with deduplication keys, server-side event matching
- Consent Mode v2, Google Consent Mode implementation integrated with CMP or cookie banner
- Server-side GTM (if in scope), first-party subdomain container for ad platform signal quality
- Additional platform tags, LinkedIn, HubSpot, Hotjar, or other required tools added cleanly
- Custom event tags, all business-specific events tagged with correct parameters
Validation & governance
- Preview mode verification, every tag trigger confirmed before production publish
- Network request inspection, actual tag payloads verified in browser developer tools
- Cross-system data reconciliation, GA4, Google Ads, and Meta data compared post-implementation
- Version documentation, every container version has a change note explaining what changed and why
- Governance policy, rules for future tag additions so the container stays clean
- Team training, how to use GTM Preview mode and when to involve a developer
What a GTM engagement includes.
Audit
- Full tag inventory
- Duplicate detection
- Dead tag identification
- Trigger audit
- Variable audit
- Priority remediation list
Cleanup
- Dead tag removal
- Duplicate deduplication
- Trigger correction
- Variable rebuild
- Naming convention
- Folder organisation
Implementation
- GA4 configuration tag
- Google Ads conversion tags
- Meta Pixel and CAPI
- Consent Mode v2
- LinkedIn / HubSpot / Hotjar tags
- Custom event tags
Quality & Governance
- Preview mode verification
- Network request audit
- Cross-system reconciliation
- Version documentation
- Governance policy
- Team training
This is right for you if:
- Businesses whose GTM container has been managed by multiple agencies and has never been audited
- Companies where ad platform conversion data does not match expected volume or CRM lead counts
- Marketing teams who cannot answer what every tag in their container does
- Businesses running Google or Meta ads who want to implement server-side tracking for signal quality
- E-commerce brands where GA4 purchase events and ad platform conversions are inflated or inconsistent
Not the right fit if:
- Businesses that have a clean, recently audited GTM container and validated conversion data
- Companies without a website or with a website that has no analytics tracking requirement
Frequently asked questions.
What is server-side GTM and do we need it?
Server-side GTM is a GTM container that runs on your own server rather than in the user's browser. Instead of sending data from the browser to Google, Meta, and other platforms, the data goes to your server first, then your server forwards it. This bypasses browser-based tracking prevention, improves data accuracy, and increases Meta signal quality from the typical 5-6 range to 8+ out of 10. For businesses spending significant budget on Meta or Google Ads, server-side GTM produces a measurable improvement in campaign performance.
How do we know how many conversions are duplicated in our current setup?
Compare your ad platform reported conversions to your CRM lead count or Shopify order count for the same period. If ad platforms are reporting 2-5x more conversions than your source of truth, you have duplication. We can also audit directly in GTM Preview mode and the GA4 DebugView to see how many conversion events fire per actual user action.
What is Consent Mode and is it required in India?
Google Consent Mode v2 is Google's system for adjusting tag behaviour based on user cookie consent choices. It is technically mandatory for EU users as of March 2024, but Google has indicated it will become a global standard. For Indian businesses, it is currently not legally required, but implementing it is best practice: it allows Google to model conversions for non-consenting users, reducing signal gaps in Smart Bidding. If your site has any EU traffic, it is not optional.
Can we give the new agency access to GTM without losing control?
Yes. GTM supports multiple user accounts with granular permission levels: Read, Edit, Approve, and Publish. We recommend giving agencies Edit access only, with Publish reserved for an internal admin or a designated trusted partner. This means no agency can publish changes without your review. Every publish should be accompanied by a version note explaining what changed and why.
Ready to know exactly what your GTM container is sending?
Book a 30-minute call. We will do a live walkthrough of your GTM container and show you the three biggest data quality risks before you commit to anything.
Book a call