Google Tag Manager
Google Tag Manager: containers, tags, triggers and versions
- Connects by
- Signing in with Google
- Category
- Analytics and SEO
- Part of
- Tools
- 102
| Service | Key | Base URL |
|---|---|---|
| Google Tag Manager | google-tag-manager | https://tagmanager.googleapis.com/tagmanager/v2 |
Connecting
Your client presses Connect on their link and approves on Google's own screen. Operate As never sees their password.
curl https://api.operate.as/v1/me/clients \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"[ { "id": "6f1c2a7e-...", "name": "Miller Dental", "services": [ "google-tag-manager" ] }]Permissions
| What the client reads | Permission it asks for |
|---|---|
| See your Tag Manager accounts and containers | https://www.googleapis.com/auth/tagmanager.readonly |
| Add and change tags, triggers and variables in your containers | https://www.googleapis.com/auth/tagmanager.edit.containers |
| Publish changes to your containers | https://www.googleapis.com/auth/tagmanager.publish |
Tools
Install Google Tag Manager's typed package for your language:
pip install operate-as-google-tag-managergoogle-tag-manager.accounts_containers_createcurl -X POST https://api.operate.as/v1/actions/google-tag-manager.accounts_containers_create \ -H "Authorization: Bearer $OPERATE_AS_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "clientId": "6f1c2a7e-...", "input": { "parent": "<parent>" } }'Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/google-tag-manager.accounts_containers_create
{ "status": 200, "data": { "…": "the service's own response" }, "encoding": "json"}Pass-through
Paths continue from https://tagmanager.googleapis.com/tagmanager/v2. Your Operate As key goes in Authorization; the client's access is added for you.
See Pass-through requests for the full request and response format.
curl "https://api.operate.as/v1/clients/6f1c2a7e-.../google-tag-manager/..." \ -H "Authorization: Bearer $OPERATE_AS_API_KEY"{ "status": 200, "data": { "…": "the service's own response" }, "encoding": "json"}When access ends
Operate As renews the sign-in before it runs out and checks it daily. If Google refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.
See Keeping access alive and Removing access.
HTTP/1.1 409 ConflictContent-Type: application/json{ "detail": "Miller Dental's Google access ended. Send them their link to reconnect."}{ "id": "evt_3f9a1c…", "type": "connection.expired", "createdAt": "2026-10-16T08:00:00+00:00", "data": { "clientId": "6f1c2a7e-...", "clientName": "Miller Dental", "provider": "google", "services": [ "google-tag-manager" ], "reconnectUrl": "https://…" }}