Google Tag Manager: container configuration in operational investigations
Opsphere now queries a connected Google Tag Manager account during an operational investigation. Ten read-only tools cover accounts, containers, tags, triggers, variables, published versions, workspace status, and version diffs. The gtm module stays disabled until that tenant links Google with Connect Google and an operator enables the module. Google Tag Manager remains the source of that container configuration.
The Tag Manager API reflects container configuration, not live browser firing. End-to-end validation pairs that configuration with macro_tracking_integrity_audit and HTTP checks. Opsphere is read-only by default and does not change the container.
What changes
A connected Google Tag Manager account can now be queried during an investigation. The result is container configuration from the Tag Manager API: accounts, containers, tags, triggers, variables, published versions, workspace status, and the diff between versions.
How it works
A tenant links Google through Connect Google OAuth. An operator enables the Tag Manager API in Google Cloud, then enables the gtm module for that tenant. Admin can set gtm_default_account_id and gtm_default_container_id as defaults. Google Tag Manager supplies the container configuration. Opsphere queries it for the investigation.
- gtm_accounts_list lists accounts.
- gtm_containers_list and gtm_container_details list containers and open one.
- gtm_tags_list, gtm_triggers_list, and gtm_variables_list read tags, triggers, and variables.
- gtm_versions_list and gtm_live_version read published versions and the live version.
- gtm_workspaces_status reports workspace status.
- gtm_version_diff compares container versions.
Why it matters
During an investigation, a team can read the published container, workspace status, and version diffs Google Tag Manager already holds, next to other connected signals. Google Tag Manager remains the source of that configuration.
Limits and requirements
Opsphere is read-only by default. The Tag Manager API reflects container configuration, not live browser firing. Source systems remain authoritative for the underlying operational data.
- Requires Connect Google OAuth and the gtm module enabled for the tenant.
- Requires the Tag Manager API enabled in Google Cloud.
- Admin defaults are gtm_default_account_id and gtm_default_container_id.
- End-to-end checks pair this configuration with macro_tracking_integrity_audit and HTTP checks.