Tag ManagerPlatform
Audited, staged, published by you
Audit a container and stage the fix in Tag Manager. You publish the version yourself, then verify.
- Live
- Your own Google sign-in
- You publish, not us
What it can do
What a Tag Manager MCP server can do here
18 tools, usable once Tag Manager is connected, as of v2.16.0: 9 read and 9 write. The writes — a container version, staged in a workspace for you to publish — run only with your approval in your AI client.
- Accounts, containers and workspaces
- What you can reach, which workspace a change would land in, and the version history behind it.4 tools, usable once Tag Manager is connected
- Tags
- Reading the tags a container fires, adding one, and correcting one that is firing wrongly.3 tools, usable once Tag Manager is connected
- Triggers
- The conditions a tag fires on, staged in a workspace rather than edited live.3 tools, usable once Tag Manager is connected
- Variables
- Your own variables and the built-in ones, read, created and switched on where a tag needs them.5 tools, usable once Tag Manager is connected
- Folders
- Keeping the workspace legible, so the change you asked for is the change you can find again.3 tools, usable once Tag Manager is connected
In practice
One turn, start to finish
A worked example rather than a recording of your account — the shape of it, not your numbers.
Tag Manager workspace: AdCopilot
stage a tag
Newsletter signupGA4 event
Stagedstage a trigger
Form submitForm ID equals signup
Stagedstage a variable
Form IDData layer
StagedYours to press.
Illustrative session
- audit
- stage the fix in Tag Manager
- you publish
- verify
Access
What you actually grant
Stated in the words you would use, because you are being asked to make a decision here.
- What you are granting
- Read access to your containers, and edit access to a workspace inside them. Publishing a version is not part of what you grant.
- What it can never widen
- It runs as you. If you cannot open an account or a property in Google's own interface, the connector cannot reach it either, and no setting on our side changes that.
- Where the grant lives
- In your own Google account, on its permissions page, where you can withdraw it at any moment without asking us first.
Connect it with the Google account that opens the container. The connector stages changes in a workspace; you publish the version in Tag Manager.
Google is still reviewing these permissions, so the consent screen may warn you that the app is not verified. You are granting access to your own account either way, and you can withdraw it from your Google account at any time.
Questions
Four short answers
The four things people ask before they connect this one, answered without hedging.
No. It stages the change in a workspace and stops there. Publishing is yours, in Tag Manager, and the verify step afterwards reads the container back to check that what you published is what was staged.
The tags a container fires, the triggers behind them, the variables they read, and the workspace a change would land in. What comes back is the fix, staged, with what it changed and why.
No. Each product is its own consent. Tag Manager is what turns a tracking finding into a staged fix rather than a line on your to-do list.
Yes — this one. AdCopilot's hosted connector covers Tag Manager with 18 tools usable once connected, 9 read and 9 write, as of v2.16.0. It audits a container and stages the fix — tags, triggers, variables, folders — and each staged change runs only with your approval in your AI client. Publishing the version stays yours, in Tag Manager.