tracking-sync
/tracking-sync
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
- Author
- jtrackingai ↗
- Repository
- analytics-tracking-automation ↗
- Licence
- Apache-2.0
- Last repository change
- 29.04.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 29.04.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Original author description
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
How it works
- Inputs
- Workflow
- Hard Rules
- Required Output
- Closeout Style
- Stop Boundary
- References
SKILL.md preview
--- name: tracking-sync 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](../../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. ## Required Output Produce and share: - `<artifact-dir>/gtm-config.json` - `<artifact-dir>/gtm-context.json` - `<artifact-dir>/workflow-state.json` For Shopify runs, also expect: - `<artifact-dir>/shopify-custom-pixel.js` - `<artifact-dir>/shopify-install.md` ## Closeout Style - default to a short answer-first sync summary before listing files - summarize what was generated or synced, what still needs manual selection or approval, and any blocking checklist items first - keep file listings and follow-up commands after the summary ## Stop Boundary Stop after sync unless the user explicitly asks for verification. Default next phase: ```bash ./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json ``` ## References - [../../references/output-contract.md](../../references/output-contract.md) - [../../references/gtm-troubleshooting.md](../../references/gtm-troubleshooting.md)
Files in this package (2)
- SKILL.md 3 KB
- agents/openai.yaml 1 KB
Versions
The database has no other skills named tracking-sync.
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version 2a22efb80a1a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100tracking-live-gtm
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers. - 100gtm-container-auditor
Audits a Google Tag Manager container for dead tags, trigger logic, consent settings, naming, versions and workspace conflicts, and builds missing GA4 event tracking with dataLayer code. Use when asked to audit or clean up GTM, or how to track clicks, forms or scroll in GTM. - 90analytics-tracking-automation
Use when you need GA4 + GTM tracking delivery from site discovery through publish, or when the right phase entry point is still unclear. - 100gtm-build-konvert
Build or extend a Google Tag Manager (GTM) container from an approved event contract: variables, triggers, tags, folders, consent settings, naming, and an import-ready container JSON generated from a declarative spec and checked before import. Use when asked to create, scaffold,… - 90gtm-get-started
Triggers when someone new to GTM Skills asks where to begin, with phrasings like "how do I get started", "what do I do first", "where do I begin with gtm", or /gtm-get-started. Looks at what the workspace already has and takes the user through each missing step, handing it to… - 100server-side-tracking-planner
Decides if a site needs server-side tracking by weighing orders GA4 and ad platforms miss against hosting cost, then plans the server GTM container, Conversions API events, event ids, hashing and tests. Use for server-side tagging, server-side vs client-side tracking or sales lost to ad blockers.