Google Analytics 4 Setup
ooiyeefei/ccc
Sets up GA4 on a website and wires one real conversion event end to end, verified in DebugView before any money goes into ads.
A skill your agent uses when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-sync --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tracking-sync .claude/skills/tracking-sync && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "tracking-sync" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-sync into .claude/skills/tracking-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-sync", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-syncType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-sync --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tracking-sync .agents/skills/tracking-sync && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "tracking-sync" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-sync into .agents/skills/tracking-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-sync", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-sync --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tracking-sync .cursor/skills/tracking-sync && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "tracking-sync" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-sync into .cursor/skills/tracking-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-sync", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jtrackingai/analytics-tracking-automation.git --path skills/tracking-sync--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-sync --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tracking-sync .gemini/skills/tracking-sync && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "tracking-sync" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-sync into .gemini/skills/tracking-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-sync", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-syncInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tracking-sync .github/skills/tracking-sync && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "tracking-sync" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-sync into .github/skills/tracking-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-sync", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jtrackingai/analytics-tracking-automation tracking-sync --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jtrackingai/analytics-tracking-automation.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tracking-sync .opencode/skills/tracking-sync && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "tracking-sync" agent skill from https://github.com/jtrackingai/analytics-tracking-automation/tree/main/skills/tracking-sync into .opencode/skills/tracking-sync/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "tracking-sync", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
tracking-syncA skill your agent uses when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Tracking Sync is an agent skill from jtrackingai/analytics-tracking-automation. Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Its SKILL.md is about 680 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Marketing & SEO, covering Go-to-market strategy. It works with Shopify and Google Analytics. The repository describes itself as: AI-powered GA4 + GTM event tracking — automates site analysis, event schema, GTM sync, preview verification, and publishing. Works with Cursor, Codex, and any AI agent. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 68378e0. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Tracking Sync loads about 677 tokens when it runs. Until then it costs about 34 tokens; SKILL.md has 236 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from jtrackingai/analytics-tracking-automation at commit 68378e0, republished under its Apache-2.0 licence (© jtrackingai). 236 words, ~677 tokens.
.claude/skills/tracking-sync/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Use this skill for Step 4 and Step 5 work.
One of:
<artifact-dir>/event-schema.json<artifact-dir>/gtm-config.jsonIf 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.jsonIf 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>--force.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.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.sync only when exact --account-id, --container-id, and --workspace-id values are already confirmed.Produce and share:
<artifact-dir>/gtm-config.json<artifact-dir>/gtm-context.json<artifact-dir>/workflow-state.jsonFor Shopify runs, also expect:
<artifact-dir>/shopify-custom-pixel.js<artifact-dir>/shopify-install.mdStop 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© jtrackingai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
SKILL.md and 1 other file in skills/tracking-sync of jtrackingai/analytics-tracking-automation.
Open the folder on GitHubat commit 68378e0
Tracking Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Tracking Sync this skilljtrackingai/analytics-tracking-automation | 142 | — | ~677 | Automated safety check: Pass | Apache-2.0 | |
| Google Analytics 4 Setupooiyeefei/ccc | 494 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Gtm Auditcognyai/claude-code-marketing-skills | 104 | — | ~1.6k | Automated safety check: Pass | None | |
| Gtm Setupcognyai/claude-code-marketing-skills | 104 | — | ~4.8k | Automated safety check: Notes | None | |
| Gtm Tracking Plancognyai/claude-code-marketing-skills | 104 | — | ~1.4k | Automated safety check: Notes | None | |
| Ad Conversion Tracking Setupminhnv0807/ai-business-skills | 608 | — | ~3.7k | Automated safety check: Pass | MIT |
ooiyeefei/ccc
Sets up GA4 on a website and wires one real conversion event end to end, verified in DebugView before any money goes into ads.
cognyai/claude-code-marketing-skills
Google Tag Manager container audit — tag health, orphaned and paused tags, duplicate GA4 config, trigger coverage, Consent Mode, naming, workspace hygiene
cognyai/claude-code-marketing-skills
GTM Event Tracking & Setup Reference — dataLayer fundamentals, trigger types, variable types, GA4 tag configuration, debug mode, and best practices
cognyai/claude-code-marketing-skills
Turn a measurement plan into a Google Tag Manager spec — tags, triggers, variables, and copy-paste dataLayer snippets for every event
minhnv0807/ai-business-skills
Sets up and verifies conversion tracking before ad spend: Meta Pixel and CAPI, Google Ads, GA4, TikTok, server-side GTM, consent mode, UTMs and a pre-launch checklist.
thatrebeccarae/claude-marketing
Google Tag Manager expertise. An agent skill from thatrebeccarae/claude-marketing.
jtrackingai/analytics-tracking-automation
A skill your agent uses when the user wants crawl coverage, platform detection, dataLayer discovery, or a fresh artifact directory before grouping and schema work.
jtrackingai/analytics-tracking-automation
A skill your agent uses 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-automation
A skill your agent uses when the work starts from site-analysis.json and the user wants page-group authoring, grouping adjustments, or page-group approval.
jtrackingai/analytics-tracking-automation
A skill your agent uses when the user wants to inspect the real live GTM runtime before schema generation or compare multiple live GTM containers.
jtrackingai/analytics-tracking-automation
A skill your agent uses when the user wants schema preparation, event design, selector validation, schema review, or event-spec generation.
jtrackingai/analytics-tracking-automation
A skill your agent uses when the user wants preview QA, failure interpretation, release readiness, or an explicit publish handoff.
Works with
Categories
A skill your agent uses when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema. Tracking Sync is an agent skill from jtrackingai/analytics-tracking-automation. Use when the user wants GTM-ready config generation, GTM workspace sync, or container selection from an approved schema.
Tracking Sync fits situations like: the user wants GTM-ready config generation; GTM workspace sync; container selection from an approved schema.
Run `npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a claude-code`. Or copy the skill folder (skills/tracking-sync in jtrackingai/analytics-tracking-automation) into .claude/skills/tracking-sync in your project. Claude Code loads it when a task matches its description.
Run `npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a codex`. Or copy the skill folder (skills/tracking-sync in jtrackingai/analytics-tracking-automation) into .agents/skills/tracking-sync in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jtrackingai/analytics-tracking-automation --skill tracking-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/tracking-sync, .gemini/skills/tracking-sync, .github/skills/tracking-sync and .opencode/skills/tracking-sync in your project.
SKILL.md names no scripts, command-line tools or credentials: Tracking Sync is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Tracking Sync is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 677 tokens (SKILL.md is roughly 2.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Tracking Sync: Google Analytics 4 Setup (ooiyeefei/ccc, 494 stars), Gtm Audit (cognyai/claude-code-marketing-skills, 104 stars), Gtm Setup (cognyai/claude-code-marketing-skills, 104 stars) and Gtm Tracking Plan (cognyai/claude-code-marketing-skills, 104 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
jtrackingai (a GitHub user) maintains it in jtrackingai/analytics-tracking-automation, which has 142 GitHub stars. The repository holds 8 skills in this directory. The repository was last updated on April 29, 2026.
Source: jtrackingai/analytics-tracking-automation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.