Tracking Live GTM

SkillDatabases & data

Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.

Available today. Use it from your connected AI after setup.

No other account needed.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use the Tracking Live GTM skill

What this skill tells your AI

The instructions your AI receives, as published by jtrackingai/analytics-tracking-automation in skills/tracking-live-gtm/SKILL.md and read by ahel’s review.

Use this skill to audit the site's real live GTM setup before event generation.

One of:

If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing.

Run the live baseline step before schema preparation whenever the site has a real GTM container installed:

./event-tracking analyze-live-gtm <artifact-dir>/site-analysis.json

If multiple live containers matter and the user already knows the primary comparison target:

./event-tracking analyze-live-gtm <artifact-dir>/site-analysis.json --primary-container-id GTM-XXXXXXX

If the user wants to test the quality of the already-published live GTM setup on the real site, run:

./event-tracking verify-live-gtm <artifact-dir>/site-analysis.json

During review:

show all detected live GTM containers
explain which container is the primary comparison baseline
summarize existing live events, measurement IDs, and obvious issues
when verify-live-gtm was run, separate parsed live definitions from browser-verified live firing evidence
if this review is part of tracking_health_audit, clearly separate runtime-detected live definitions from any formal preview-verified automation evidence
stop before schema authoring if the user wants to review the live baseline first

Produce and share:

default to a compact live-tracking summary before listing files
name the detected live events directly instead of only reporting event counts
in tracking_health_audit, explicitly separate runtime-detected live definitions from formal preview-verified automation evidence
list artifacts only after the decision-ready summary

Stop after the live GTM baseline is reviewed unless the user explicitly asks to continue into schema work.

Default next phase:

./event-tracking prepare-schema <artifact-dir>/site-analysis.json

Advanced