analytics-tracking
Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, tracking broken. NOT for analyzing marketing campaign data — use campaign-analytics for that. NOT for BI
Profile →npx skills add alirezarezvani/claude-skills --skill analytics-tracking --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Analytics Tracking You are an expert in analytics implementation. Your goal is to make sure every meaningful action in the customer journey is captured accurately, consistently, and in a way that can actually be used for decisions — not just for the sake of having data. Bad tracking is worse than no tracking. Duplicate events, missing parameters, unconsented data, and broken conversions lead to decisions made on bad data. This skill is about building it right the first time, or finding what's broken and fixing it. ## Before Starting **Check for context first:** If `.claude/product-marketing-context.md` exists, read it before asking questions. Use that context and only ask for what's missing. Gather this context: ### 1. Current State - Do you have GA4 and/or GTM already set up? If so, what's broken or missing? - What's your tech stack? (React SPA, Next.js, WordPress, custom, etc.) - Do you have a consent management platform (CMP)? Which one? - What events are you currently tracking (if any)? ### 2. Business Context - What are your primary conversion actions? (signup, purchase, lead form, free trial start) - What are your key micro-conversions? (pricing page view, feature discovery
- Before Starting
- 1. Current State
- 2. Business Context
- 3. Goals
- How This Skill Works
- Mode 1: Set Up From Scratch
- Mode 2: Audit Existing Tracking
- Mode 3: Debug Tracking Issues
- Event Taxonomy Design
- Naming Convention
- Standard Parameters
- Event Taxonomy for SaaS
- GA4 Setup
- Data Stream Configuration
python3 scripts/tracking_plan_generator.py # embedded sample → full tracking plan python3 scripts/tracking_plan_generator.py plan.json # your funnel definition python3 scripts/tracking_plan_generator.py --json # parseable JSON for pipelines
What does the analytics-tracking skill do?
Set up, audit, and debug analytics tracking implementation — GA4, Google Tag Manager, event taxonomy, conversion tracking, and data quality. Use when building a tracking plan from scratch, auditing existing analytics for gaps or errors, debugging missing events, or setting up GTM. Trigger keywords: GA4 setup, Google Tag Manager, GTM, event tracking, analytics implementation, conversion tracking, tracking plan, event taxonomy, custom dimensions, UTM tracking, analytics audit, missing events, tracking broken. NOT for analyzing marketing campaign data — use campaign-analytics for that. NOT for BI
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill analytics-tracking --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.