I Connected Claude to My Tag Manager and Found 3 Containers Nobody Knew Existed

Published · Updated · 6 min read
MeasureU blog cover reading Look before you add, over an abstract diagram of a tag manager account with live and abandoned container connections
MeasureU

I Connected Claude to My Tag Manager and Found 3 Containers Nobody Knew Existed

Tired of wondering what's actually firing inside your tracking setup? You're not alone.

We pointed Claude at our own Google Tag Manager account, the one we've been managing for years, and in seconds it found containers we'd completely lost track of. And people who still had access that should have been shut off long ago.

If that's what's sitting inside a setup we run every single day, it's worth knowing what's inside yours.

I'm Jeff Sauer, and I've spent twenty years helping companies collect marketing data they can trust. I helped build and sell an eight-figure agency doing marketing and measurement work, landed on the Inc 5000 five times, and now I run MeasureU, where we teach you how to get clean data for your marketing and build the tools our members actually use in their accounts.

We built this GTM connection for our own community. And the first account it ran on was ours.

In this post, I'll show you how the MCP connection works, what we found hiding in our own account, and how you can run the same audit on your business or your clients.


Watch the Full Breakdown

The walkthrough above is the same account, the same connection, and the same handful of plain-English questions you can ask on your own setup within the hour.

What You'll Learn in This Post

  • An MCP connection lets Claude read your entire Google Tag Manager account: every container, every tag, and every user with access
  • We discovered 3 forgotten containers and consultants who still had permissions from 5+ years ago
  • Clean data starts with visibility, not with adding more tracking
  • The MCP gives you the map of where to focus. Deeper validation is separate work

Table of Contents

What Is Google Tag Manager?

Before we go further, let me ground this for anyone who hasn't lived inside a tag manager.

Google Tag Manager is the system that holds all of your site's tracking tags. Those little code snippets that fire when someone:

  • Visits a page
  • Clicks a button
  • Completes a purchase
  • Submits a form

Every analytics event, every ad pixel, every conversion signal usually runs through GTM.

Diagram showing a website feeding data through one Google Tag Manager tag out to analytics, ad pixels and conversion tracking
Every analytics event, ad pixel and conversion signal usually runs through GTM.

Which means if GTM is a mess, your data is a mess.

And here's the thing. Most tag manager accounts are a mess.

Why Your Google Tag Manager Becomes a Disaster Over Time

GTM accounts accumulate history. They get touched by a dozen different people over a span of years:

  • The marketing team adds Facebook pixels
  • An agency sets up Google Ads conversion tracking
  • A contractor implements custom event tracking for a campaign
  • Someone else installs a heat mapping tool
  • Another person adds a chat widget

And nobody ever looks at the whole picture at once.

That's the main problem we're trying to solve here. It's not that tags are bad themselves. It's the fact that nobody even knows what tags are firing at any given time.

The real consequences:

  • Fines for collecting data illegally (GDPR, CCPA violations you didn't know about)
  • Overage charges from platforms you didn't know you were still using
  • Conflicting conversion data that makes your reporting worthless
  • Security risks from outdated access permissions

You can't fix what you can't see. And most teams haven't actually looked at their full GTM setup in years.

What Is an MCP Connection?

That's where the MCP connection comes in.

MCP stands for Model Context Protocol. In plain terms, it's a direct connection that lets Claude read and work with a tool on your behalf.

We've already covered installing and connecting MCP servers elsewhere, so I'm not going to walk through the technical setup here. What we're going to focus on is the result that this connection produced.

When you connect Claude to Google Tag Manager through an MCP, it can read your entire account:

  • Every container
  • Every tag inside those containers
  • Every user with access permissions

And it can surface all of that in seconds.

Claude asking which of three MeasureU Google Tag Manager accounts to read after a single plain-English question
One question, and the first thing it surfaced was that we had three accounts, not one.

Notice what happened there. One plain-English question, and the very first thing it had to do was ask which MeasureU account I meant, because there were three of them.

What We Found: 3 Lost Containers and 5-Year-Old Access Permissions

So here's what happened when we ran this on our own account.

First, the MCP surfaced three containers we had completely lost track of.

A container is basically a separate file inside GTM. You might have one for your main site, one for a subdomain, one for a campaign you ran two years ago and never cleaned up.

Claude listing the three containers inside the MeasureU Google Tag Manager account, one of them named Clean Up Container To Be Deleted
Three containers, including one nobody had gotten around to deleting.

We had containers sitting in our account that nobody on the current team could explain. Old campaign containers. Test environments that got abandoned. Stuff that had been collecting dust for who knows how long. One of them is named “Clean Up Container ‐ To Be Deleted.”

Then it pulled the full access list.

Every person who had ever been granted permissions to our GTM account was right there. And some of those names weren't with the company anymore. Some were consultants who hadn't been involved with the company in over five years.

Diagram of a Google Tag Manager container with four current users on active connections and four stale permissions struck through
The access list is where the real risk sits: people who left, on connections nobody closed.

People who'd moved on. Contractors from old projects. Emails that had no business touching our tracking anymore.

If that's what's inside an account we manage daily, what's inside yours?

Why a GTM Audit Comes Before Adding More Tags

Here's why this matters for your measurement and how it enables you to do better marketing.

Everyone wants to talk about adding more tracking. More tags, more events, more granular data. I understand that instinct. More data feels like more control.

But the more you add, the worse your tracking usually gets. And the less you trust your data. The more conflicts you end up having.

You can't trust your conversion data if there are tags in containers you forgot existed.

Clean data doesn't start with adding more tags to try and collect your way out of a problem. It starts with seeing what's actually there.

And for most setups? Nobody has looked in a long time.

I've been doing this for twenty years. It's smart to start with an audit before you go further. Take a systematic look at what's inside a setup:

  • What's working
  • What's broken
  • What's out of place

Tag managers accumulate history, and history gets messy, and nobody ever sets aside time to look at the whole thing.

Using an MCP connection gives you that look in seconds.

What the MCP Connection Can and Cannot Do

I want to be clear about what the GTM MCP can do and what it can't. An honest take is more useful than a hyped one.

What Claude surfaces through this connection:

  • A full picture of what's in your account
  • The containers and their structure
  • The access list showing everyone with permissions
  • The overall map of what exists

That can get you pretty far.

But the MCP connection is not a tag validator.

It's not going to fire every tag and confirm the data is landing correctly in your analytics platforms. That's the deeper work, and it's a different layer that's best reserved for a consultant or dedicated QA process.

Think of it this way: the MCP connection gives you the map of where to focus. You need that map to do the deeper fixing. Everything else follows from that.

How to Run This GTM Audit Yourself

If you want to connect to the MCP server and run this on your own account, you can get the MCP running and connect to Claude in an hour or less.

Your next steps:

  1. Set up the MCP connection to your Google Tag Manager account
  2. Ask Claude to list all containers and access permissions
  3. Review what surfaces, especially anything you don't recognize
  4. Clean up outdated access immediately (this is a security issue)
  5. Document which containers are active vs. abandoned
The MeasureU Prompting GTM MCP Servers guide open to use case one, auditing key tracking tags
The setup guide inside the MeasureU Academy, with ready-made prompts for each audit pass.

Or you can use our setup guide that lives inside the MeasureU Academy. We build these tools for our members, test them on our own account, and then get feedback from the practitioners inside our community after we release them.

Want to see this skill in action for your own data?

This GTM audit resource is included inside the MeasureU Academy, alongside 50+ other tools and resources. You can get started with a monthly plan right away.


What's hiding in your Google Tag Manager? If you've had contractors, agencies, or team members come and go over the years, I'd bet there's more in there than you realize.

About the author

Founder, MeasureU

Jeff Sauer is a measurement marketing expert who has helped thousands of marketers make better decisions with data. He founded MeasureU to make analytics accessible to everyone.

Share:

Ready to fix your marketing data?

Our team helps marketing organizations build data infrastructure they can actually trust. Tell us about your situation.

Enjoyed this article?

Get weekly measurement marketing insights delivered to your inbox.

No spam. Unsubscribe anytime.