Audit on demand
Full tag inventories, filtered lists, and setup reads across accounts, containers, and workspaces. The audit that consultants charge days for becomes a chat.
Google Tag Manager connector
Google Tag Manager MCP Connector – Audit and Publish Tags by Asking
Every marketing team has a Tag Manager container, and almost none can tell you what is in it. Tags accumulate like sediment: the old agency's pixels, the test nobody removed, the duplicate conversion tag quietly double-counting. The one person who understood the container left, and now everyone is afraid to touch it.
The Tag Manager connector ends the mystery. It links the AI you already use, like Claude, ChatGPT, or Copilot, to your GTM accounts through Mad Fish Elements. Your AI reads your containers, workspaces, tags, triggers, and versions. It answers "what is actually firing on our site" in plain language. And it can revert a workspace change that should not have happened, with your sign-off. The scariest admin surface in marketing becomes something you can question.
See it
What Your AI Can See
Connect your GTM accounts, and your AI reads the whole container picture. It lists every tag in a workspace, filtered by name or by type, so "show me all of it that mentions Facebook" or "list all custom HTML tags" is one question. It fetches any tag's full setup, by ID or by name. You see exactly what a tag does and when it fires. It reads full container versions: the complete snapshot of tags, triggers, and variables. So "what does the live version actually contain" has a factual answer. And "what changed between version 41 and now" becomes a check instead of an archaeology dig.
Custom HTML tags deserve their own mention: they are the riskiest thing in any container, arbitrary code firing on your site. Your AI can list them all in seconds, which is the first step of every container audit that has ever mattered.
Do it
What Your AI Can Do
Tag Manager writes can break tracking or the site itself, so the connector keeps write access narrow and safe on purpose:
Revert workspace changes
The undo button GTM buries: your AI can revert a tag's workspace-level changes, restoring it to its state from the base version, with your sign-off. The "someone edited the conversion tag and now the numbers look wrong" incident gets a clean rollback instead of a panicked rebuild.
Compare versions
Read any container version in full and hold it against the current workspace, so changes get reviewed before anyone hits publish.
Answer "what fires when." Any tag's triggers and setup, in plain language, so teams stop needing a developer to read the container to them.
Publishing itself stays in GTM, on purpose. The connector makes you certain about what you are publishing; the publish button stays human.
A working session
The Audit Nobody Scheduled
In practiceThe working session: a new analyst asks what is in the container, and for once that is a fair question. You ask: "List every tag in our main workspace, grouped by type." Forty-one tags, twelve custom HTML. You ask: "Show me the custom HTML tags with their triggers." Three fire on all pages; one is named 'test-DO-NOT-DELETE' from 2023. You ask: "What is in that tag?" A vendor pixel for a tool you cancelled last year. You remove it in GTM with trust, because now you know exactly what it is. Fifteen minutes, and the container has an list for the first time in years.
The return
What You Get Back
A container you can see into
The full list, on demand, in plain language. Institutional knowledge stops living in one former employee's head.
Confidence before publish
Version-against-workspace check means changes get reviewed on facts, and the revert path is one sign-off away if something slips through.
Faster incident response
When conversions look wrong, "what changed in the container recently" is the first question, and now it takes a minute to answer.
Cheaper audits
The tag hygiene pass that used to be a consulting engagement becomes a quarterly chat.
Fewer mystery pixels
Custom HTML tags, the highest-risk residents of any container, get listed and explained on request.
Use cases
One Conversation, Real Account Work
"List every tag in the main container's workspace, grouped by type."Google Tag Manager
The full list in one answer, the starting point of every audit.
"Show me all custom HTML tags and what triggers each one."Google Tag Manager
The high-risk shortlist, with firing conditions in plain language.
"What is in the live container version, and how does the current workspace differ from it?"Google Tag Manager
A pre-publish review grounded in the actual version snapshot.
"Someone changed the GA4 conversion tag this week. Revert it to the base version."Google Tag Manager
A clean workspace rollback, shown to you and shipped on your sign-off.
"Do we have any tags still pointing at the old analytics site?"Google Tag Manager + Google Analytics 4
A site move-leftover sweep across the container, checked against the site that should be there.
For in-house teams
Close the expectation gap
The container stops being the thing nobody dares open. Marketers get plain-language answers about what fires where. The revert path means an editing mistake is an sign-off away from fixed, not a week of forensic debugging. And when the analytics numbers look strange, the first question finally has a fast answer: what changed in here, and when?
For marketing teamsFor agencies
Run the whole book
Client containers are inherited crime scenes: years of other agencies' tags with no documentation. Inventory a new client's container on day one, flag the risks in the kickoff deck, and keep every client's container auditable from one connection with per-client access walls.
For agenciesReports worth sharing
From Live Account to Clear Story
Ask in chat and share the dashboard without building exports or taking screenshots.
Container Inventory Report
Every tag by type, with triggers, per workspace. Built for onboarding, audits, and the analyst who just asked.
Custom HTML Risk Board
The arbitrary-code tags, their firing conditions, and their age. Built for the security-minded review.
Change Review Summary
Current workspace against the live version: what would ship if someone shared today. Built for the pre-publish check.
The charts stay simple here: bar for tags by type, a table-first layout for inventories, and a change list for version check. And when your team wants the list anytime, the Data Visualization add-on turns your reports and analysis into always-current dashboards they open from a link. Ask in chat; share the dashboard. No exports; no screenshots.
Governance
Governed Access Your Whole Org Can Live With
Access is set per person, so Read seats see everything and change nothing, while Write seats create and edit with your approval flow in front of each change; Delete permissions go only to the people you trust to clean up. Many teams start read-only, check answers against the platform for two weeks, and then widen access as the audit trail earns trust.
You choose the level of human review and can change it at any time, while every action records what changed, when it changed, and who approved it. Per-user OAuth means Elements never stores your Google Tag Manager password, and your data is never harvested or resold.
Per-user OAuthRead / write / delete per seatFull audit trailApproval flow on every change
Clear limits
What This Connector Will Not Do
It will not publish your container; ever. That button stays human, in GTM, on purpose. It will not create or edit tags today. This page will say so until those actions are live. It will not run code or fire tags. Reading a tag is not executing it. And it will not revert anything silently. A rollback is shown to you and ships on your sign-off, into the workspace, where you can still review it before publish. Containers get scary when nobody can see inside them. This connector is the flashlight, not another hand on the wiring.
Setup
Setup Takes Minutes
- Start your trialCreate your Elements account and connect it to your AI.
- Link Google Tag ManagerSign in through the secure OAuth screen and choose what to connect. No code and no engineers.
- Set permissionsDecide who can Read, who can Write, and who can Delete. Start conservative and widen as trust builds.
- Ask your first question"How did we do last month?" is a complete instruction.
Plans, account limits, and the multi-client Agency plan are on the pricing page .
FAQ
Google Tag Manager Connector Questions
Can it publish container changes?
No, on purpose. The connector reads all of it and can revert workspace-level tag changes with your sign-off, but publishing stays a human action in GTM. It makes you certain about what you publish; it does not publish for you.
Can it edit or create tags?
Tag creation and editing are not offered on this page until those actions are live on the Gateway. Today the writes are the revert path: restoring a tag's workspace changes to the base version, with your sign-off.
We have multiple accounts and containers. Does it handle that?
Yes. Your AI works across the accounts, containers, and workspaces you connect, limited per person, with per-client walls for agencies.
Will my AI change things without asking me?
No. Your AI acts only with the access rules you set, changes go through the sign-off level you choose, and Read-only seats cannot change anything at all because the sign-off flow is the product working as designed.
Which AI assistants can our team use?
Your team can use Claude, ChatGPT, and Microsoft Copilot, while other AI tools can likely connect to Elements when they support MCP, the open standard for linking AI assistants to outside tools.
Is my data used to train anything?
No. Your data stays yours, so nothing is gathered and nothing is resold.
Focus on the Strategy, Delegate the Launch
The teams winning with AI in marketing are not handing their accounts to a black box; they keep the strategy and delegate the hands-on-keyboard work, while approvals and an audit trail make it safe to move fast. Connect the account you already have through the Gateway and ask the question you would normally build a report to answer.
Your first 14 days are free. Add your card to start, and cancel before the trial ends to pay nothing.