It’s genuinely brilliant — right up until you inherit a container that nobody has properly maintained and realise the data you’ve been making decisions from for the past eighteen months is completely unreliable.
Messy GTM setups are everywhere. And the frustrating thing is that the mess usually builds gradually, added to by different people at different times, each making reasonable decisions in isolation that collectively create a tracking nightmare.
This guide covers the most common GTM problems that corrupt your data — and what to do about them.
Why GTM Setups Go Wrong In The First Place
The accessibility of GTM is part of the problem. Because you don’t need to write code to fire tags, it’s very easy for multiple people across a business — marketers, agencies, developers, analysts — to all have access and all be making changes independently.
Without governance, that becomes a problem fast. Tags get added without documentation. Old tags never get removed. Triggers get duplicated because nobody was sure whether the original was still active. Variables get named inconsistently because three different people used three different naming conventions.
According to research from Econsultancy, poor data quality costs UK businesses billions in wasted marketing spend each year — and a significant chunk of that traces back to tracking setup issues that nobody noticed until the damage was done.
If you’re working with an organic marketing agency London that uses your analytics data to inform content strategy, keyword priorities, and campaign decisions, the quality of your GTM setup is directly connected to the quality of those decisions.
The Most Common GTM Problems That Corrupt Your Data
Duplicate tags firing on the same event
This is probably the single most common issue in inherited GTM containers. A tag — typically a GA4 event, a conversion pixel, or a form submission tracker — fires more than once for the same user action. The result is inflated data: conversion counts that don’t reflect reality, event totals that look suspiciously round, and reports that don’t match what you can verify manually.
Duplicates happen when someone adds a new tag without checking whether one already existed, when triggers are set up at both the tag level and the trigger level in overlapping ways, or when a tag has been migrated from Universal Analytics to GA4 but the old one was never deactivated.
The fix starts with a full tag audit. Our guide to GTM housekeeping walks through how to systematically review your container and identify tags that are firing when they shouldn’t be.
Triggers that are too broad
An “All Pages” trigger on a tag that should only fire on specific page types is a classic setup error. It’s quick to implement, it works in the short term, and it causes quiet havoc over time.
The most common example is a purchase confirmation or thank-you page event that fires on all pages because someone used a page view trigger without a page path condition. You end up counting every page view as a conversion, which sounds great until someone asks why your conversion rate is 40%.
Triggers should be as specific as possible. Use page path conditions, element visibility conditions, or click element conditions rather than broad catch-alls, and always test in preview mode before publishing.
No naming convention
Open a poorly maintained GTM container and you’ll often find tags named things like “New tag – 14/03”, “COPY – GA4 form test”, “Facebook pixel – OLD do not delete”, and “Rick’s tag.” Nobody can tell at a glance what any of these do, which version is live, or whether any of them are still needed.
Without a consistent naming convention, routine maintenance becomes an archaeological dig. You can’t confidently pause or delete tags because you’re not sure what they’re connected to. You can’t efficiently onboard new team members. And mistakes become much more likely.
A good naming convention typically includes the tag type, the platform or tool, the event name, and the date — something like GA4 | Form Submit | Contact Page | 2025-03. It takes five minutes to set up a standard and saves hours of confusion down the line.
Variables that aren’t being validated
GTM’s built-in variables and custom JavaScript variables are powerful, but they’re also easy to break. A variable that worked when your site was on one platform might fail silently after a redesign. A dataLayer push that fired correctly on the old checkout flow might not trigger on the new one.
The problem is that broken variables often don’t throw an obvious error — the tag still fires, but the data it sends is undefined, null, or simply wrong. You get events in GA4 with no associated parameters, conversion data that looks off, or audience segments that aren’t capturing the right users.
Regular validation using GTM preview mode and your GA4 event strategy framework will catch these before they corrupt months of reporting.
Unmanaged third-party tags
Every third-party tag in your GTM container is a potential performance, privacy, and data quality risk. Remarketing pixels, chat widgets, heatmap tools, A/B testing scripts — they all need to be there for a reason, and that reason should be documented.
The problem is that third-party tags often get added for a specific campaign or project and then never removed. They slow your site down, they can interfere with other tracking, and in a post-GDPR environment, firing third-party tags before consent is obtained puts you in legally uncomfortable territory.
Your consent mode and measurement setup needs to be watertight, particularly given the ICO’s increasingly active enforcement stance. Tags that fire before a user has given consent — even inadvertently, because the trigger didn’t account for consent state — are a compliance liability.
The Naming And Documentation Problem Nobody Talks About
One of the least glamorous but most impactful things you can do for your GTM setup is create a simple spreadsheet that documents every live tag. What it does, who added it, when it was added, what it depends on, and whether it’s still needed.
This sounds tedious. It is. But it’s significantly less tedious than trying to reverse-engineer a container with 200 undocumented tags when something breaks.
Our Google Tag Manager governance guide covers how to build a sustainable process around this — one that doesn’t require heroic effort every time someone needs to make a change.
How Messy Data Affects Your Marketing Decisions
The downstream impact of poor GTM hygiene is significant. When your conversion data is inflated, you optimise your campaigns towards events that aren’t real conversions. When your form submission tracking is broken, you can’t accurately assess which landing pages or organic content pieces are actually generating leads.
When event names are inconsistent — sometimes form_submit, sometimes FormSubmit, sometimes contact_form_complete — your GA4 reporting for directors becomes unreliable and hard to trust. Decision-makers lose confidence in the data, and rightly so.
If you’re relying on your analytics to inform your content strategy, your paid media spend, and your organic marketing prioritisation, messy GTM data means you’re flying partially blind. You might be doubling down on channels or pages that look like they’re performing because of inflated tracking, while deprioritising things that are actually working.
For any business that takes its analytics seriously, a clean GTM setup isn’t optional — it’s foundational. It directly affects how well your data and analytics function can do its job.
What A Clean GTM Setup Looks Like
A well-maintained GTM container has a few obvious characteristics:
- Every tag has a clear, consistent name that tells you what it does without having to open it
- Triggers are specific, with conditions that prevent tags from firing in unintended contexts
- Variables are validated against your live site regularly, not just at the point of setup
- Third-party tags are audited at least quarterly, with anything no longer in use removed
- Consent mode is implemented correctly, so tags only fire when appropriate consent has been given
- Preview mode is used before every publish, without exception
It’s also worth considering server-side tracking as your setup matures — it moves tag execution away from the browser, which improves performance, reduces ad blocker impact, and gives you more control over what data is being sent and when.
A good technical SEO agency will flag GTM issues that affect site performance — particularly third-party scripts that add render-blocking load — as part of a broader site health review.
FAQs
How do I know if my GTM setup has problems? Start by opening GTM in preview mode and walking through your key user journeys. Watch which tags fire on each step. If you see tags firing multiple times for the same action, firing on pages they shouldn’t, or not firing when they should, you’ve found issues. Comparing your GA4 event counts to what you’d expect from manual testing is another quick sense check.
How often should a GTM container be audited? At minimum, once a quarter. If your site changes frequently or multiple people have access to the container, more often. Before and after any major site redesign or platform migration is also essential — these are the moments when tracking most commonly breaks.
Is it safe to delete old tags in GTM? Yes, as long as you’ve verified they’re not currently firing and nothing depends on them. Archive rather than delete if you’re uncertain — GTM’s version history means you can always restore something if it turns out it was needed.
What’s the difference between GTM and GA4 — aren’t they the same thing? They’re different tools that work together. GA4 is your analytics platform — it stores, processes, and reports on your data. GTM is a tag management system — it controls when and how tracking code fires on your site. GTM is often used to deploy the GA4 tracking code, but the two are separate, and issues in GTM will affect the quality of data in GA4.
Should my marketing agency have access to our GTM container? Yes, but with appropriate governance. Agencies should be working in a clearly defined role, documenting any changes they make, and ideally operating in a separate workspace so their changes can be reviewed before publishing. Full admin access for an external party without oversight is how containers get messy.
Does GTM affect website speed? It can, particularly if there are many third-party scripts loading through it. Tags that load synchronously or add significant JavaScript execution time will affect page speed scores and Core Web Vitals. Regular audits help keep this under control.
Sort Your GTM Before It Costs You More Than You Think
The cost of a messy GTM setup isn’t always obvious — it shows up in wasted ad spend, misguided content decisions, and strategy calls made on data nobody should have trusted. Getting it right doesn’t require a full rebuild in most cases; it requires a structured audit, a clear governance process, and a team that understands how tracking quality connects to commercial outcomes.
As an organic marketing company that takes measurement seriously, Totally Digital works with businesses to make sure their analytics are reliable enough to actually inform what happens next.