All guides, by feature
Set up Google Tag Manager for Claude
Add Orbit’s GTM service account to each container in Tag Manager, list the accounts and containers Claude may use, then mark the setup verified.
Before you start
- You need
- Permission in Google Tag Manager to add users to your containers.
- Where in Orbit
- Sidebar › Data › Integrations
Steps
Tick a step’s number when it’s done. We’ll remember where you were.
Open Integrations, choose Google Tag Manager, then Connect with Claude.ai →.
Under 1. Grant the Orbit GTM service account, press Copy email. In Tag Manager, open each container’s User Management, add that email as a user and give it the Publish role, or Edit if Claude shouldn’t publish.
Press ← Back to GTM. Under , type each account as accounts/ and its ID, and press the plus button. To limit Claude to some containers, switch on Restrict to specific containers and add each one.
Leave Read-only on and Allow publish off unless Claude should change or publish tags, then press Save scope.
Press .
When it worked
Orbit confirms “GTM scope saved”, then “Marked verified”, and the status changes to Connected.
If something goes wrong
Orbit rejects an account or container path.
Write accounts as accounts/ and the ID, such as accounts/6034256781, and containers as accounts/6034256781/containers/12345678. Find the IDs in Tag Manager’s admin pane.
Orbit showsAt least one account path is required
Add at least one account under Allowed GTM accounts, then press Save scope.
Orbit showsno gtm integration configured for this agency
Save the container scope first, then press I added the SA — mark verified.
The status went back to Pending verify.
Changing the allowed accounts or containers resets it. Check the service account is a user on any new container, then mark it verified again.
How it works
Explainer: Google Tag Manager container scope
Orbit’s shared GTM service account can act only on the accounts and containers your agency lists under Container scope. Anything outside that scope is rejected.
| Setting | What it does |
|---|---|
| Allowed GTM accounts | The Tag Manager accounts Claude may reach, each written accounts/ and its ID. At least one is required. |
| Restrict to specific containers | Off: every container in those accounts. On: only the containers you list, written accounts/…/containers/…. |
| Read-only | On by default. Agents can read GTM data but can’t change tags, triggers, variables or workspaces. |
| Allow publish | Off by default. While it’s off, publishing a container always fails. |
- In Tag Manager, give the service account the Publish role on each container, or Edit if Claude should change tags but not publish.
- Find account and container IDs in Tag Manager’s admin pane.
- The approval screen in Claude.ai sums up the scope, for example “Read and modify GTM data · 1 account, all containers in scope”.
- Once authorized, the Claude.ai connector also works in Claude Code.
Explainer: Google Tag Manager statuses
Google Tag Manager shows Connected once your agency has saved which containers Claude may use and marked Orbit’s service account as added. The Integrations card and the GTM page word the earlier steps differently.
| Integrations card | GTM page | What it means |
|---|---|---|
| Not connected | Not configured | No container scope saved yet. |
| Pending verify | Scope saved · awaiting verification | Scope saved, but nobody has marked the service account as added since the scope last changed. |
| Connected | Connected | Scope saved and marked verified. |
- Marking it verified is your agency’s own confirmation. Orbit doesn’t check Tag Manager to see the service account was added.
- Changing the allowed accounts or containers sets it back to Pending verify. Changing Read-only or Allow publish doesn’t.
- There’s one Google Tag Manager setup per agency, shared by everyone.