Update
Tag Manager: versions, environments and Community Template Gallery imports
TL;DR
Seven new Tag Manager tools: the container's versions and environments, a Community Template Gallery template's permissions read before import, the import itself (always a person's decision), a compile check of the draft, syncing a draft to the latest version and undoing one draft change. And a fix: a workspace path from another container is now refused before any call.
What's new
- Versions and environments: which version is live, every earlier version with its counts, and which version each environment (Live, Latest, staging, QA) serves.
- Community Template Gallery: the agent reads a template's permissions — sending pixels, injecting scripts, cookies — before anything is imported. The import goes into the workspace draft, pinned to the version you saw, and always waits for a person.
- Compile check: whether the draft compiles, without creating a version or publishing. It needs Tag Manager's container-versions permission, which Google is still verifying; until then the answer says what is missing.
- Sync and undo: bring a draft up to the latest version (conflicts are reported, never resolved for you) or undo one pending draft change.
Fixed: writes stay in your container
One Google sign-in usually reaches several containers. A tool given a workspace or item path from another container used to accept it; it is now refused before Tag Manager is called, publishing included. Client writes are refused on a web container, where clients do not exist.
Publishing still always waits for a person. Every tool: Tag Manager guide · Tag Manager platform page.
Frequently asked questions
- Can the agent import a Tag Manager template from the Community Template Gallery?
- Yes, into the workspace draft. It shows the template's permissions first, and the import always waits for a person.
- Can the agent change a Tag Manager container I did not connect?
- No. A path from another container is refused before any call.