Google Tag Manager
Manage website tracking tags, triggers and variables in GTM containers.
There is no Tag Manager integration in the product today: the application does not create or edit GTM tags, triggers or variables. Website tracking is done with the chat widget/form embed scripts and GA4 (read-only). This entry documents what an integration would require so it can be scoped.
AProvider definition
- Provider
- Google Tag Manager
- What it does
- Manage website tracking tags, triggers and variables in GTM containers.
- Why we need it
- Manage website tracking tags, triggers and variables in GTM containers.
- Used in
- Not used by any module yet
BAccount requirements
- Account type
- Google account with access to a GTM account/container
- Prerequisites
- Tag Manager API enabled in the Cloud project
CConnection method
- Authentication
- OAuth 2.0 (Google) — would reuse the Google OAuth client
- Where to enter it
- Not available in the application yet.
Setup steps
- 1Would require enabling the Tag Manager API, adding GTM scopes (tagmanager.readonly / tagmanager.edit.containers / tagmanager.publish) and building the connector.
DPermissions & API scopes
Scopes are granted on the provider's side when you authorise the app.
This list is generated from the scopes the application's code requests.
EFree vs paid
- Free account / free API access
- Yes — GTM and its API are free.
- Card or billing account required?
- No.
- Paid plan / costs
- None (Tag Manager 360 is part of Google Marketing Platform).
- Quota and usage limits
- API quota per project per day.
FSetup screenshots
Capture each step with real values masked. Save images as public/docs/integrations/google_tag_manager/1.png … 10.png and they appear here automatically.
- Screenshot to add1. Account login / creationThe provider's sign-in or sign-up page.
- Screenshot to add2. Developer consoleThe developer console or dashboard home.
- Screenshot to add3. Project / app creationCreating the app or project used for this integration.
- Screenshot to add4. API enablementThe API or product enabled for the project.
- Screenshot to add5. OAuth configurationConsent screen / OAuth settings with the redirect URIs.
- Screenshot to add6. API key / credentials creationCreating the key, secret or token (mask the value).
- Screenshot to add7. Permissions / scopesThe scopes or permissions requested or approved.
- Screenshot to add8. Billing / quota settingsBilling, credits or quota page.
- Screenshot to add9. Application connectionThe provider card in our application with fields filled (secrets masked).
- Screenshot to add10. Successful connectionThe green Test result or the connected account listed.
GApplication configuration
Never include real API keys, client secrets, access tokens or passwords in screenshots, tickets or documentation. Values below are field names and examples only.
No credentials to enter.
HTesting
- 1Not applicable until the integration is built.
ITroubleshooting
| Problem | What to do |
|---|---|
| Invalid credentials | Check the Client ID/App ID and secret were copied from the same app, without spaces. Regenerate the secret if unsure. |
| Missing permissions | Reconnect and accept every permission on the consent screen. If a permission is missing from the list, add it to the app (and get it approved). |
| OAuth failure | Sign-in was cancelled, the app is in development/testing mode, or the user isn't allowed to use it yet. Add the user as a tester or publish the app. |
| Redirect URI mismatch | Copy the redirect URI from section G exactly — same https scheme, host and path, no trailing slash — into the provider's app settings. |
| API not enabled | Enable the API/product for the project or app in the provider console and wait a few minutes. |
| Quota exceeded | Wait for the quota window to reset (see section E) or request a higher quota / add credits. |
| Account not eligible | Check the account requirements in section B (e.g. business/professional account, verified property, registered organisation). |
| App review required | Permissions beyond development access need the provider's review before other accounts can connect. See section E for restrictions. |
| Billing required | Add a payment method or prepaid credits on the provider account (see section E). |
JDisconnect & security
- Revoke access at the provider
- Not applicable.
- Disconnect in the application
- Not applicable.
- Rotate credentials
- Create the new key or secret first, paste it into the same card and Test, then delete the old one at the provider — no downtime.
- How credentials are stored
- Encrypted at rest with AES-256-GCM using the server's ENCRYPTION_KEY, shown masked after saving, never returned to the browser, and used only from the API server.
- What data the application can access
- None today.

