GTM command center
One connected tool: what gtm-docs-watcher detects on Google's help pages, how it maps to the plugin marketplace, the autoresearch loop that fixes containers, and the live 3D graph of the container itself.
GTM COMMAND CENTER — SYSTEM
┌────────────────────────────────────────────────────────────┐
│ gtm-docs-watcher (Apify Actor) detects doc changes │
└───────────────────────────┬────────────────────────────────┘
▼
┌────────────────────────────────────────────────────────────┐
│ IMPACT MAP — change → affected plugins │
└───────────────────────────┬────────────────────────────────┘
▼
┌────────────────────────────────────────────────────────────┐
│ GTM AUTORESEARCH — keep/revert loop, version history │
└───────────────────────────┬────────────────────────────────┘
▼
┌────────────────────────────────────────────────────────────┐
│ CONTAINER GRAPH (3D) — same node data, live and rotatable │
└────────────────────────────────────────────────────────────┘
Announcement changes → plugin impact
Each detected change mapped against the plugins it touches. Click a change to filter the grid.
Container version control
An autoresearch-style keep/revert loop: each round scores the container, applies fixes, keeps what improved the score, reverts what didn't.
How tracking connects
Three rings: variables innermost, triggers in the middle, tags outermost. Drag to rotate, scroll to zoom, click a node to isolate its connections. This reads directly from the same container data as the impact map above.
Unused or missing at a glance
Zero-connection components, or components referenced as needed but not yet created.
Dimensions and parameters
Dimensions, metrics, and parameters across GA4, Google Ads, and Meta tags.
| Tag | Platform | Parameter | Value / source |
|---|
Container growth over time
Component counts at each container version release.