gtm-tracking-plan — Claude Code skill: setup and overview
Generates Google Tag Manager container specs and copy-ready dataLayer.push() snippets directly from a website URL.
npx skills add cognyai/claude-code-marketing-skills --skill gtm-tracking-plan -a claude-codeWhat gtm-tracking-plan does
The skill transforms measurement requirements into a concrete Google Tag Manager build specification. Passing a website URL allows the agent to inspect pages via WebFetch, determine the conversion funnel, and produce structured tables for variables, triggers, and tags. It also natively consumes event structures generated previously by /ga4-measurement-plan.
Account access is optional. When run without connected platforms, the skill inserts clean placeholders such as G-XXXXXXX. Once connected via the Cogny MCP server, it inspects live workspaces to diff the plan against current setups, flagging tags to create, adjust, or retire.
Without connecting external ad accounts, marketing pixel identifiers must be entered manually.
What it helps with
- generate GTM tag, trigger, and variable build specifications
- produce structured
dataLayer.push()code for engineers - audit live GTM container setups against a tracking taxonomy
- organize conversion tags across supported ad platforms
Example prompts for the agent
- /gtm-tracking-plan example.com
- Build a GTM tracking spec for example.com
- Audit the live GTM container against our measurement plan for example.com
How to install gtm-tracking-plan
1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill gtm-tracking-plan -a claude-code2Manually: put the files in place
~/.claude/skills/gtm-tracking-plan/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gtm-tracking-plan/
1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill gtm-tracking-plan -a codex2Manually: put the files in place
.agents/skills/gtm-tracking-plan/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill gtm-tracking-plan -a cursor2Manually: put the files in place
.cursor/skills/gtm-tracking-plan/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install cognyai/claude-code-marketing-skills gtm-tracking-plan2Manually: put the files in place
.github/skills/gtm-tracking-plan/SKILL.md1Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill gtm-tracking-plan -a gemini-cli2Platform CLI
gemini skills install https://github.com/cognyai/claude-code-marketing-skills --path skills/gtm-tracking-planManually: put the files in place
.devin/skills/gtm-tracking-plan/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add cognyai/claude-code-marketing-skills --skill gtm-tracking-plan -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about gtm-tracking-plan
How to install gtm-tracking-plan in Claude Code?
Run npx skills add cognyai/claude-code-marketing-skills --skill gtm-tracking-plan -a claude-code. The skill file will be stored in ~/.claude/skills/gtm-tracking-plan/SKILL.md.
What does gtm-tracking-plan do?
It drafts an implementation spec for Google Tag Manager, including trigger logic, variable definitions, and ready-to-paste dataLayer code snippets.
Do I need connected accounts to generate a spec?
No. The skill runs without external connections using placeholder values. Connecting through Cogny MCP is only needed to compare against an existing container.
