Change your tracking, publish only after approval.
The agent knows every tag, trigger and variable in the container, creates new ones and prepares versions. A version only goes live once you explicitly enable publishing.
- Coverage: complete
- 24 tools · 11 of them make changes
Read and change.
Your agent works with exactly the permissions of the connected account. Read tools are quick to enable. Tools that change data stay off until you explicitly turn them on.
What your agent can read
- Accounts, containers and workspaces with all tags, triggers, variables, folders and templates.
- Pending changes and conflicts in a workspace.
- The live version and older versions for comparison.
- Environments such as staging, and the install snippet.
- If you mention a container ID like GTM-ABC123, the agent finds the matching container.
What your agent can change
- Create, edit and delete tags, triggers and variables, with protection against conflicting edits.
- Import templates from the Community Template Gallery, such as the LinkedIn Insight Tag.
- Create workspaces, compile a preview (shows errors without going live) and create a version from it.
- Publish versions. This changes the live website immediately.
Only once you enable it, per agent and per tool. If you want, a person also approves each action before it runs.
How teams use Google Tag Manager.
Marketing, sales and RevOps run these as recurring routines or on request.
- 01
Tracking audit
When you take over the tracking setup- List all tags, triggers and variables
- Find duplicate tags, tags without triggers and unused variables
- Document the setup in plain language
ResultAn inventory that would otherwise take half a day.
- 02
New form, new event
A new landing page goes live- Create a form submission trigger
- Set up the matching GA4 event tag
- Compile a preview and create a version
ResultA version is ready for review and only goes live after your approval.
- 03
Add the LinkedIn Insight Tag
Before your first LinkedIn campaign- Import the template from the Community Template Gallery
- Configure it with your partner ID
- Prepare it as a version
ResultLinkedIn conversion tracking, without anyone filing a ticket with the web team.
- 04
What changed?
When tracking suddenly drops- Compare the live version with the previous one
- Explain the changed tags and triggers in plain language
ResultYou know which change broke the tracking.
Built-in safeguards
- Publishing is a separate tool. Without your explicit approval, an agent only prepares versions and doesn't put anything live.
- Everything else depends on the role the connected Google account has in the GTM account.
- If you want, changes only run after a person approves them, for example the team lead: in the Data Hub, in Slack or via a link. On top of that, each agent has daily and hourly limits.
- Guardrails for every agent: deletes and changes to more than 10 records need approval by default, an emergency brake kicks in on a run of deletes, and you can set your own rules per tool.
- Each connection has an access level: Read, Write or Admin. Where the vendor allows it, the Data Hub only requests the permissions for that level.
- Credentials are stored encrypted in the Data Hub, and the agent never sees them. Every call is logged.
What it can't do
- The agent can't use preview and debug mode in the browser (Tag Assistant). It compiles the preview but doesn't click through your website.
What's possible here depends on what Google Tag Manager offers through its API. We make available what the API allows, as ready-made tools or through the generic API request to Google Tag Manager, and we check new API versions regularly.
Connect Google Tag Manager to your agents.
In 30 minutes, we'll show you the Data Hub with your own tools.