analytics-tracking-automation

Use this skill as the end-to-end coordinator for GA4 + GTM tracking delivery. Use it when: • the user needs a full GA4 + GTM implementation flow, from analysis to go-live readiness • the request spans multiple workflow phases (discovery, schema, sync, verification, publish) • the correct entry point is still unclear and you need this skill to route to the right phase Do not assume the user wants the full workflow. <!-- analytics-tracking-automation auto-update bootstrap:start -->

This installed root skill can self-check for newer GitHub versions before you continue. Before doing any task in this bundle: • Resolve the directory that contains this installed SKILL.md. Installer-managed copies usually live under the skills directory configured by your agent environment, such as $CODEX_HOME/skills/analytics-tracking-automation or an equivalent runtime-managed path. • Run node "<bundle-dir>/runtime/skill-runtime/update-check.mjs" --json. • If the result status is update_available, immediately run node "<bundle-dir>/runtime/skill-runtime/self-update.mjs" --apply. • If the update succeeds, read <bundle-dir>/SKILL.md again before continuing so you are using the refreshed instructions. • If the result status is disabled, treat this bundle as a local development link or repo checkout and continue without updating. <!-- analytics-tracking-automation auto-update bootstrap:end -->

The skill family is split into one umbrella skill plus seven phase skills: • tracking-discover for crawl coverage, platform detection, and fresh artifact bootstrap • tracking-group for page-group authoring and approval • tracking-live-gtm for auditing the real live GTM runtime before schema generation • tracking-schema for schema preparation, review, validation, and approval • tracking-sync for GTM config generation and sync • tracking-verify for preview QA and optional publish handoff • tracking-shopify for Shopify-specific schema, sync, install, and verification rules If the request is already bounded to one phase and that phase skill is available, route there instead of inlining the full runbook here. Once site-analysis.json indicates Shopify, keep discovery and grouping shared, then let tracking-shopify own the Shopify-specific branch.

• Use the repo-local wrapper ./event-tracking in this repository. If dist/cli.js is missing, run npm run build first. • For public/ClawHub installs, you must run this first before any event-tracking command: npx skills add jtrackingai/analytics-tracking-automation. • Keep one artifact directory per site at <output-root>/<url-slug>. • If the user already provides an artifact directory or one of its files, resume from the earliest unmet prerequisite instead of restarting from analyze. • Use ./event-tracking status <artifact-dir-or-file> whenever the current checkpoint or next step is unclear. • Use ./event-tracking runs <output-root> when the artifact directory is unknown but the output root is known. • Prefer high-level entry commands for user-facing flows: run-new-setup, run-tracking-update, run-upkeep, run-health-audit. • Telemetry consent is a required user-choice checkpoint for richer diagnostics. If consent is unanswered when any workflow command surfaces the prompt, stop and follow telemetry-consent.md as the single-source interaction contract. Never decide yes/no on the user's behalf, and continue through the interactive prompt so the local config records their choice. • Explain the purpose, what yes does, what no does, and the remaining privacy tradeoff before asking the user to reply yes or no. Do not ask a bare yes/no question with no context. • Treat workflow mode metadata as an internal workflow-state layer, not a user-facing command surface. • analyze, validate-schema --check-selectors, preview, and sync each need outbound HTTP and a real Chromium; sync additionally needs a local loopback callback on 127.0.0.1 for Google's OAuth consent redirect. Run them in an environment that permits those capabilities so Playwright and the OAuth callback can complete. • Run prompt-driven GTM sync with an interactive TTY from the start unless exact --account-id, --container-id, and --workspace-id values are already confirmed. • Never auto-select a GTM account, container, or workspace on the user's behalf. • Do not continue past the phase boundary the user asked for.