Use when you need GA4 + GTM tracking delivery from site discovery through publish, or when the right phase entry point is still unclear.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新
免费在 GitHub 公开
tracking-sync
Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
中文简介正在准备中。当前显示原文说明。
集成工具Shopify
查看安装方法包含的文件（2）
- SKILL.md2.6 KB
- agents/openai.yaml257 B
SKILL.md（原文）
安装前可以查看交给 AI 代理的指令内容。
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:
./event-tracking generate-gtm <artifact-dir>/event-schema.json --measurement-id <G-XXXXXXXXXX>
Then sync:
./event-tracking sync <artifact-dir>/gtm-config.json
If account/container/workspace IDs are already confirmed, skip interactive selection:
./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.
synccalls Google's official GTM API via interactive OAuth. The consent flow needs outbound HTTP and a local loopback callback on127.0.0.1; runsyncin an environment that permits both.- Run
syncwith 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
synconly when exact--account-id,--container-id, and--workspace-idvalues 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:
./event-tracking preview <artifact-dir>/event-schema.json --context-file <artifact-dir>/gtm-context.json
References
评价
还没有评价。欢迎分享你的使用感受。
评论
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
同一仓库的技能
Use when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新
Use when the work starts from `site-analysis.json` and the user wants page-group authoring, grouping adjustments, or page-group approval.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新
Use when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新
Use when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新
Use when the platform is Shopify or the run needs the Shopify-specific schema, sync, install, or verification branch.
中文简介正在准备中。当前显示原文说明。
jtrackingai/analytics-tracking-automation1442026年4月29日 更新