Google Tag Manager — read containers, draft tags, and publish only with a human review
Google Tag Manager is now connected for every organization. The agent reads your containers, workspaces, tags, triggers and variables, and can draft changes — each pausing for your approval. Publishing is the one thing it will never do on its own, no matter how the autonomy settings are configured.
What the agent can do
- Read containers, workspaces, tags, triggers and variables — so "what is actually firing on this site, and on what trigger" is a question you can ask in plain language.
- Draft typed tags, triggers and variables, each pausing for your approval before it is written.
- Publishing a workspace is never unattended. Even with auto-approve on, a publish is refused with a named reason — a review has to happen, by a person.
- Custom HTML tags are fenced to the most restricted lane, because that payload is JavaScript that runs in every visitor's browser once published.
This is the second attempt, and the first one was withdrawn
An earlier Tag Manager integration was built and then pulled entirely — scopes removed from authorization, both connect routes closed — rather than left half-available behind a flag nobody could see. The Tag Manager scopes are classified sensitive by Google, and putting an unverified scope on a live consent screen shows every user of every organization an "unverified app" warning on a flow that was previously clean.
Getting it back required solving that properly: the integration ran for a single enrolled organization long enough to produce the demonstration Google asks for during verification, invisible to everyone else the whole time. With verification complete, it is offered to every organization and nothing about your consent screen is a surprise.
Frequently asked questions
- What can the agent do in Google Tag Manager?
- Read containers, workspaces, tags, triggers and variables, and draft typed tags, triggers and variables. Every draft pauses for your approval, and publishing a workspace always requires a human review.
- Can the agent publish a GTM container by itself?
- No. Publishing is never unattended — even with auto-approve enabled, a publish is refused with a named reason. A person has to review it.
- What about custom HTML tags?
- Custom HTML is fenced to the most restricted lane, separate from ordinary draft edits. That payload is JavaScript that will execute in every visitor's browser once published, so it is not treated like a tag configuration change.
- Will connecting Tag Manager show an 'unverified app' warning?
- No. The Tag Manager scopes completed Google's verification before the integration was offered generally, which is why the earlier version was withdrawn rather than shipped behind a flag.