Analytics Tracking
Implement or fix GA4 and GTM so conversions and key journey events are trustworthy before you optimize growth.
Overview
Analytics Tracking is an agent skill most often used in Grow (also Validate and Ship) that sets up, audits, and debugs GA4 and GTM event and conversion instrumentation for trustworthy journey data.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill analytics-trackingWhat is this skill?
- Build tracking plans with consistent event taxonomy, custom dimensions, UTM rules, and conversion definitions for GA4
- Configure and debug Google Tag Manager tags, triggers, and consent-aware firing
- Audit existing implementations for duplicate events, missing parameters, and broken conversions
- Separate scope from campaign-analytics and product-analytics so you instrument the right layer
- Emphasizes fixing bad data before trusting dashboards or growth decisions
Adoption & trust: 537 installs on skills.sh; 17.5k GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You cannot trust growth or launch decisions because GA4 events, GTM tags, or conversion definitions are missing, duplicated, or inconsistent.
Who is it for?
Solo builders shipping web or app experiences who need GA4/GTM implemented or repaired before scaling traffic or lifecycle experiments.
Skip if: Teams that only need campaign ROAS reports or in-product cohort analysis without fixing site-wide tag implementation—those need different analytics skills.
When should I use this skill?
Building a tracking plan from scratch, auditing GA4/GTM for gaps, debugging missing or broken events, or setting up conversion and UTM tracking.
What do I get? / Deliverables
You leave with a coherent tracking plan, corrected GTM/GA4 implementation, and validated events so funnel and conversion metrics match real user actions.
- Tracking plan with event names, parameters, and conversion mapping
- GTM/GA4 implementation or audit findings with fix list
- Documented UTM and custom-dimension conventions
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Canonical shelf is Grow because the skill’s payoff is decision-grade funnel and conversion data after the product exists. Analytics subphase matches tracking plans, event taxonomy, GA4/GTM implementation, and data-quality audits—not campaign reporting or in-app product analytics.
Where it fits
Define which signup and pricing-page events must exist before you call validation complete.
Verify GTM containers and consent mode before flipping launch traffic to production.
Audit event parameters and conversion labels after a redesign so retention reports stay comparable.
Align UTM and campaign landing-page events so acquisition channels reconcile in GA4.
How it compares
Implementation and audit skill for tags and event taxonomy—not a BI dashboard builder or paid-media campaign analyzer.
Common Questions / FAQ
Who is analytics-tracking for?
Indie and solo builders who own marketing site or app instrumentation and need GA4, GTM, and conversion tracking that leadership can actually act on.
When should I use analytics-tracking?
Use it when defining a tracking plan before launch, auditing tags before a release, debugging missing events after deploy, or standardizing UTMs and custom dimensions during Validate and Grow.
Is analytics-tracking safe to install?
Review the Security Audits panel on this catalog page and inspect the skill package in your repo before granting network or browser access during implementation work.
SKILL.md
READMESKILL.md - Analytics Tracking
# 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 `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, demo request) - Do you run paid campaigns? (Google Ads, Meta, LinkedIn — affects conversion tracking needs) ### 3. Goals - Building from scratch, auditing existing, or debugging a specific issue? - Do you need cross-domain tracking? Multiple properties or subdomains? - Server-side tagging requirement? (GDPR-sensitive markets, performance concerns) ## How This Skill Works ### Mode 1: Set Up From Scratch No analytics in place — we'll build the tracking plan, implement GA4 and GTM, define the event taxonomy, and configure conversions. ### Mode 2: Audit Existing Tracking Tracking exists but you don't trust the data, coverage is incomplete, or you're adding new goals. We'll audit what's there, gap-fill, and clean up. ### Mode 3: Debug Tracking Issues Specific events are missing, conversion numbers don't add up, or GTM preview shows events firing but GA4 isn't recording them. Structured debugging workflow. --- ## Event Taxonomy Design Get this right before touching GA4 or GTM. Retrofitting taxonomy is painful. ### Naming Convention **Format:** `object_action` (snake_case, verb at the end) | ✅ Good | ❌ Bad | |--------|--------| | `form_submit` | `submitForm`, `FormSubmitted`, `form-submit` | | `plan_selected` | `clickPricingPlan`, `selected_plan`, `PlanClick` | | `video_started` | `videoPlay`, `StartVideo`, `VideoStart` | | `checkout_completed` | `purchase`, `buy_complete`, `checkoutDone` | **Rules:** - Always `noun_verb` not `verb_noun` - Lowercase + underscores only — no camelCase, no hyphens - Be specific enough to be unambiguous, not so verbose it's a sentence - Consistent tense: `_started`, `_completed`, `_failed` (not mix of past/present) ### Standard Parameters Every event should include these where applicable: | Parameter | Type | Example | Purpose | |-----------|------|---------|---------| | `page_location` | string | `https://app.co/pricing` | Auto-captured by GA4 | | `page_title` | string | `Pricing - Acme` | Auto-captured by