AI SummaryUse this skill for Step 4 and Step 5 work. If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing. If GTM config does not exist yet:
Install
Copy this and paste it into Claude Code, Cursor, or any AI assistant:
I want to install the "tracking-sync" skill in my project. Please run this command in my terminal: # Install skill into your project mkdir -p .claude/skills/tracking-sync && curl --retry 3 --retry-delay 2 --retry-all-errors -o .claude/skills/tracking-sync/SKILL.md "https://raw.githubusercontent.com/jtrackingai/analytics-tracking-automation/main/skills/tracking-sync/SKILL.md" Then restart Claude Code (or reload the window in Cursor) so the skill is picked up.
Description
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Tracking Sync
Use this skill for Step 4 and Step 5 work.
Inputs
One of: • approved <artifact-dir>/event-schema.json • existing <artifact-dir>/gtm-config.json
Workflow
If the telemetry consent prompt appears and no prior choice is recorded, stop and follow ../../references/telemetry-consent.md before continuing. If GTM config does not exist yet: `bash ./event-tracking generate-gtm <artifact-dir>/event-schema.json --measurement-id <G-XXXXXXXXXX> ` Then sync: `bash ./event-tracking sync <artifact-dir>/gtm-config.json ` If account/container/workspace IDs are already confirmed, skip interactive selection: `bash ./event-tracking sync <artifact-dir>/gtm-config.json --account-id <account-id> --container-id <container-id> --workspace-id <workspace-id> `
Hard Rules
• Do not bypass schema approval unless the user explicitly wants --force. • Treat custom dimensions as a blocking checklist before sync/publish. • Never auto-select GTM account, container, or workspace for the user. • sync calls Google's official GTM API via interactive OAuth. The consent flow needs outbound HTTP and a local loopback callback on 127.0.0.1; run sync in an environment that permits both. • Run sync with an interactive TTY from the start whenever it may prompt for OAuth consent, account, container, workspace, or new workspace name. Non-interactive invocation will fail at the first prompt. • Use non-interactive sync only when exact --account-id, --container-id, and --workspace-id values are already confirmed.
Discussion
Health Signals
My Fox Den
Community Rating
Sign in to rate this booster