AI SummaryUse this skill to audit the site's real live GTM setup before event generation. 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
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "tracking-live-gtm" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/tracking-live-gtm && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/tracking-live-gtm/SKILL.md "https://raw.githubusercontent.com/jtrackingai/analytics-tracking-automation/main/skills/tracking-live-gtm/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
Tracking Live GTM
Use this skill to audit the site's real live GTM setup before event generation.
Inputs
One of: • confirmed <artifact-dir>/site-analysis.json • explicit live GTM public IDs when the crawl did not capture them
Workflow
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: `bash ./event-tracking analyze-live-gtm <artifact-dir>/site-analysis.json ` If multiple live containers matter and the user already knows the primary comparison target: `bash ./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: `bash ./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
Required Output
Produce and share: • <artifact-dir>/live-gtm-analysis.json • <artifact-dir>/live-gtm-review.md • optional <artifact-dir>/live-preview-result.json • optional <artifact-dir>/live-preview-report.md • optional <artifact-dir>/live-tracking-health.json • updated <artifact-dir>/workflow-state.json
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster