Skip to main content

gtm-telemetry-wizard

Declarative GTM Container IaC Compiler, Playwright E2E Live Verifier, and GA4 Telemetry Ingestion Setup Wizard.

gtm-telemetry-wizard is a standalone CLI tool and Python library for automating Google Tag Manager (GTM) container setups, compiling declarative IaC specs, verifying live webpage telemetry with Playwright, and warming up GA4 measurement streams to achieve Container Quality: Excellent.


Features

  • 5-Phase Setup Wizard: Diagnostic check, container spec compilation, live Playwright verification, GA4 ingest warm-up, and container quality reporting.
  • GA4 Ingest Warm-Up: Delivers initial telemetry pings directly to GA4 (/g/collect), automatically clearing 48-hour missing traffic quality alerts.
  • Playwright E2E Verification: Headless/Headful browser verification inspecting gtm.js snippet loading, dataLayer events, and UTM parameters.
  • Dual Deployment Options: Automated browser import (via Playwright CDP persistent Chrome profile) or GTM REST API v2 deployment.
  • Borderless Terminal UI: Clean Rich-powered terminal interface.

Installation

uv tool install gtm-telemetry-wizard

Or install from source:

git clone https://github.com/bizkite-co/gtm-telemetry-wizard.git
cd gtm-telemetry-wizard
uv sync

uv sync installs this checkout as an editable development package. The repository's mise.toml adds .venv/bin to PATH only while working in this directory, so gtw uses the local checkout here and the PyPI installation everywhere else.

Use mise run check to verify the CLI, mise run build to build distributions, and mise run release to create and push the next patch release with verkit.


Campaign Configuration and Provisioning

Every campaign command requires an explicit domain, GTM container ID, and GA4 measurement ID. gtw never substitutes IDs from another campaign. Store those values in the consuming repository's telemetry.toml and pass its location with --config:

gtw wizard --config path/to/telemetry.toml

To create a new GA4 property/web stream and GTM web container, provide the parent account IDs and the configuration path. This writes the returned G-... and GTM-... IDs to that file atomically, ready to review and commit:

gtw provision \
  --domain example.com \
  --analytics-account-id ANALYTICS_ACCOUNT_ID \
  --gtm-account-id GTM_ACCOUNT_ID \
  --config path/to/telemetry.toml

Provisioning uses Application Default Credentials. Before running it, enable the Google Analytics Admin API and Google Tag Manager API, then authenticate with analytics.edit and tagmanager.edit.containers scopes.

Deploy a generated container through the Tag Manager API:

gtw deploy --config path/to/telemetry.toml

Use --no-publish to create a reviewable GTM container version without publishing it.


Quick Start

1. Guided Setup Wizard

Run the 5-phase setup wizard for any website and container ID:

gtw wizard --domain example.com --container-id GTM-XXXXXXX --ga4-id G-YYYYYYYY

2. Using telemetry.toml Configuration File

Create a telemetry.toml in your project directory:

[site]
domain = "example.com"
container_id = "GTM-XXXXXXX"
gtm_container_api_id = "123456789"
ga4_measurement_id = "G-YYYYYYYY"

[deployment]
mode = "browser"
headful = true

Then run:

gtw wizard --config telemetry.toml

Python API Usage

from gtm_telemetry_wizard import TelemetryConfig, TelemetryProvider

# Initialize provider
config = TelemetryConfig(domain="example.com", container_id="GTM-XXXXXXX")
provider = TelemetryProvider(config)

# Run live telemetry verification
results = provider.verify_live_telemetry()
print("GTM Loaded:", results["gtm_script_loaded"])

# Send initial GA4 warm-up ping
ping_res = provider.ping_ga4_measurement_id("G-YYYYYYYY")
print("Ping Status:", ping_res["status"])

CLI Reference

  • gtw wizard - Guided 5-phase telemetry setup wizard.
  • gtw sync - Compile GTM container IaC spec.
  • gtw verify - Run Playwright E2E live URL verification.
  • gtw ping - Deliver initial GA4 warm-up measurement hit.
  • gtw provision - Provision GA4 web stream and GTM container via Google APIs.
  • gtw deploy - Import and publish compiled container manifest via GTM API.
  • gtw query - Query real-time and historical traffic via GA4 Data API.

License

MIT License © 2026 Bizkite Co.

Metadata

Release files for gtm-telemetry-wizard 0.1.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for gtm-telemetry-wizard 0.1.3
File Size Uploaded
gtm_telemetry_wizard-0.1.3.tar.gz 17.8 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for gtm-telemetry-wizard 0.1.3
File Interpreter ABI Platform
gtm_telemetry_wizard-0.1.3-py3-none-any.whl Python 3 none any Details

Total release size: 34.0 kB

Release files / gtm_telemetry_wizard-0.1.3.tar.gz

Download URL gtm_telemetry_wizard-0.1.3.tar.gz
Size 17.8 kB
Tags Source
SHA-256 checksum
How to use checksums
47940be827b9a3cceade2a9272ba87fe5f8563f5aae68f87eda55e1fdf2b0715
BLAKE2b-256 checksum
How to use checksums
5924d030786bd7b44e797c2ba36051910c445ac102fe01b32b9c4212b107217f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.

Transparency log

Release files / gtm_telemetry_wizard-0.1.3-py3-none-any.whl

Download URL gtm_telemetry_wizard-0.1.3-py3-none-any.whl
Size 16.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
333aee3aabd0c3fabe49d35269640798a0b04f245b1f4f069b9783469c4b2aa4
BLAKE2b-256 checksum
How to use checksums
d73124d5b3676c9229ecb124e6f2dc90ca8a5b57d7bf93e09d8d303d2bc4e633
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Sep 27, 2026.

Transparency log

Release history Release notifications | RSS feed

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

This release

0.1.3 This release

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page