Google Tag Manager

Containers, tags, triggers and variables.

Category: Analytics
How you connect: Sign in, read only unless you allow writing. You sign in with your account. Homla never sees your password.
Time to set up: About 2 minutes
Actions: 11 read, 12 write

Connect it#

In Homla, open Connectors, then Google Tag Manager. The Setup guide button walks you through the same steps, with fields to paste into.

Who can do it. Each person connects their own Google account; Homla then sees exactly the GTM accounts and containers that account can open. Read on a container is enough for the read tools. Tag and variable edits need Edit, creating versions needs Approve, and version_publish needs Publish on the container.

Check your container permissionsIn Tag Manager, open Admin > User Management on the container. Read is enough to list tags, triggers, variables and versions. Edit lets Homla change tags and variables, Approve lets it create versions, Publish lets it push a version live. Ask an account Administrator if a permission is missing. Open it.
Connect Google in HomlaIn Homla, open Connectors > Google Tag Manager and click Connect Google account. Tick Also allow editing first only if you need the write tools: without it, Homla asks for read access only. This connection is separate from Google Analytics. Open it.
Pick the right account and acceptGoogle asks which account to use: pick the one that has access to the containers. The consent screen lists viewing your Tag Manager containers (read tools) and, with editing ticked, managing containers, managing container versions and publishing them (write tools). Homla never asks to delete containers. Accept every line.
Check it worksBack in Homla, the account shows as connected on the card. Ask your assistant "do we have access to GTM-XXXXXXX?" with a real container id: containers_list finds it across every account you can see.
If something failsgtm_scope_missing: you connected without editing; reconnect with Also allow editing ticked. 403 on a write or publish: your permission on that container is too low (Edit, Approve or Publish, see step 1). Container not found: you consented with a Google account that has no access to it; revoke it and connect the right one. Quota message: the Tag Manager API allows few calls per minute for all Homla users together; wait a minute and retry. google_auth_expired: Google no longer accepts the connection; click Connect again.
Publishing pushes the version to the live site at once. Homla asks you to confirm every write, publish included.

What your AI can do#

These are the actions Homla gives your AI. Your role decides which ones you get. Write actions are a dry run until confirmed, see Approvals and dry runs.

Read#

Looks things up, never changes anything.

Action	What it does
`google-tag-manager_accounts_list`	The Tag Manager accounts this user can access.
`google-tag-manager_account_get`	One GTM account (name, accountId, shareData, ...).
`google-tag-manager_containers_list`	The containers under a GTM account: containerId, publicId (GTM-XXXX), name, usageContext.
`google-tag-manager_container_get`	One GTM container (name, publicId, usageContext, taggingServerUrls, ...).
`google-tag-manager_workspaces_list`	The workspaces in a GTM container: workspaceId and name.
`google-tag-manager_tags_list`	The tags in a GTM workspace (name, type, firing/blocking triggers, ...).
`google-tag-manager_triggers_list`	The triggers in a GTM workspace (name, type, filters).
`google-tag-manager_variables_list`	The user-defined variables in a GTM workspace (name, type, parameters).
`google-tag-manager_version_live`	The currently LIVE (published) version of a container.
`google-tag-manager_version_get`	One container version by id (its tags/triggers/variables snapshot).
`google-tag-manager_versions_list`	A container's version history (id, name, live/deleted flags).

Write#

Creates or changes things, as the account owner.

Action	What it does
`google-tag-manager_container_create`	Create a container under a GTM account.
`google-tag-manager_container_update`	Update a GTM container.
`google-tag-manager_tag_create`	Create a tag in a GTM workspace.
`google-tag-manager_tag_update`	Update a tag in a GTM workspace.
`google-tag-manager_tag_delete` Deletes	Delete a tag from a GTM workspace.
`google-tag-manager_variable_create`	Create a user-defined variable in a GTM workspace.
`google-tag-manager_variable_update`	Update a user-defined variable.
`google-tag-manager_variable_delete` Deletes	Delete a user-defined variable from a workspace.
`google-tag-manager_workspace_create_version`	Snapshot a workspace as a container version, which you then publish live.
`google-tag-manager_version_publish`	Publish a container version live.
`google-tag-manager_version_delete` Deletes	Delete a GTM container version.
`google-tag-manager_request`	Any Tag Manager API v2 call, for what the typed tools don't cover (triggers, folders, environments).

Disconnect it#

In Homla, open the account menu on the tool's page and choose Disconnect. Anyone it was shared with loses access at once. To cut it off on the tool's side too:

To cut Homla off, open your Google account's Third-party apps & services page, pick Homla, then Delete all connections. To go back to read-only, revoke there and reconnect in Homla without ticking Also allow editing. Removing the person's access in the product itself also stops Homla at once.

Generated from the product code. Action names are what the CLI and the API use.

Something wrong or missing on this page? Tell us.