Analytics Tracking
Plan and implement GA4, GTM, conversion events, and UTM discipline so you can tell if marketing and product changes actually work.
Overview
Analytics Tracking is an agent skill most often used in Grow (also Launch) that helps solo builders set up, improve, and audit marketing and product measurement with GA4, GTM, events, and UTMs.
Install
npx skills add https://github.com/coreyhaines31/marketingskills --skill analytics-trackingWhat is this skill?
- Initial assessment: business decisions, current stack, tech stack, and privacy constraints before tagging
- Core principle: track for decisions, not data hoarding
- Covers GA4, Google Tag Manager, conversion and event tracking, UTM parameters, Mixpanel, Segment
- Reads product-marketing context first to avoid redundant questions
- Explicit handoff: A/B test measurement defers to ab-test-setup skill
- Metadata version 1.1.0 documented in skill frontmatter
- Explicit cross-skill note: A/B test measurement references ab-test-setup
Adoption & trust: 58.1k installs on skills.sh; 32.4k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You cannot confidently tell whether campaigns, pages, or features convert because events, tags, or UTMs are missing, wrong, or never mapped to decisions.
Who is it for?
Builders shipping web or SaaS who need GA4/GTM or product analytics wired to real conversion definitions and campaign attribution.
Skip if: Pure backend services with no user-facing measurement surface, or teams wanting A/B test design without tagging foundation—use ab-test-setup for experiment measurement focus.
When should I use this skill?
User mentions set up tracking, GA4, Google Analytics, conversion tracking, event tracking, UTM parameters, GTM, tracking plan, attribution, Mixpanel, Segment, or analytics isn't working.
What do I get? / Deliverables
You get a decision-oriented tracking plan and implementation guidance so conversions and key events fire correctly and inform marketing and product choices.
- Tracking plan aligned to business decisions
- Implementation and audit checklist for events, conversions, and UTMs
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Measurement pays off once you ship and promote; canonical shelf is Grow analytics because the skill optimizes ongoing insight for marketing and product decisions. Analytics subphase matches event tracking, attribution, tagging plans, and tooling audits rather than copywriting or lifecycle email flows.
Where it fits
Define primary conversion and UTM schema before you spend on ads to a waitlist or pricing page.
Implement campaign and channel events so launch traffic separates organic, paid, and referral performance.
Audit an existing GA4 and GTM setup when founders say analytics is not working or events look wrong.
Track content-led funnel steps so blog or newsletter traffic ties to signup and activation metrics.
How it compares
Skill package for tracking plans and tag implementation—not a hosted analytics product or MCP server that ingests telemetry for you.
Common Questions / FAQ
Who is analytics-tracking for?
Indie founders and marketers who own their site or app instrumentation and need GA4, GTM, or product analytics aligned to specific conversions.
When should I use analytics-tracking?
In Grow when auditing events or attribution; in Launch when turning on conversion tracking for a new site or campaign; whenever tracking is broken or you ask how to measure results.
Is analytics-tracking safe to install?
Recommendations may involve third-party scripts and tag containers—review the Security Audits panel on this page and your privacy policy before publishing GTM or analytics snippets to production.
SKILL.md
READMESKILL.md - Analytics Tracking
# Analytics Tracking You are an expert in analytics implementation and measurement. Your goal is to help set up tracking that provides actionable insights for marketing and product decisions. ## Initial Assessment **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Before implementing tracking, understand: 1. **Business Context** - What decisions will this data inform? What are key conversions? 2. **Current State** - What tracking exists? What tools are in use? 3. **Technical Context** - What's the tech stack? Any privacy/compliance requirements? --- ## Core Principles ### 1. Track for Decisions, Not Data - Every event should inform a decision - Avoid vanity metrics - Quality > quantity of events ### 2. Start with the Questions - What do you need to know? - What actions will you take based on this data? - Work backwards to what you need to track ### 3. Name Things Consistently - Naming conventions matter - Establish patterns before implementing - Document everything ### 4. Maintain Data Quality - Validate implementation - Monitor for issues - Clean data > more data --- ## Tracking Plan Framework ### Structure ``` Event Name | Category | Properties | Trigger | Notes ---------- | -------- | ---------- | ------- | ----- ``` ### Event Types | Type | Examples | |------|----------| | Pageviews | Automatic, enhanced with metadata | | User Actions | Button clicks, form submissions, feature usage | | System Events | Signup completed, purchase, subscription changed | | Custom Conversions | Goal completions, funnel stages | **For comprehensive event lists**: See [references/event-library.md](references/event-library.md) --- ## Event Naming Conventions ### Recommended Format: Object-Action ``` signup_completed button_clicked form_submitted article_read checkout_payment_completed ``` ### Best Practices - Lowercase with underscores - Be specific: `cta_hero_clicked` vs. `button_clicked` - Include context in properties, not event name - Avoid spaces and special characters - Document decisions --- ## Essential Events ### Marketing Site | Event | Properties | |-------|------------| | cta_clicked | button_text, location | | form_submitted | form_type | | signup_completed | method, source | | demo_requested | - | ### Product/App | Event | Properties | |-------|------------| | onboarding_step_completed | step_number, step_name | | feature_used | feature_name | | purchase_completed | plan, value | | subscription_cancelled | reason | **For full event library by business type**: See [references/event-library.md](references/event-library.md) --- ## Event Properties ### Standard Properties | Category | Properties | |----------|------------| | Page | page_title, page_location, page_referrer | | User | user_id, user_type, account_id, plan_type | | Campaign | source, medium, campaign, content, term | | Product | product_id, product_name, category, price | ### Best Practices - Use consistent property names - Include relevant context - Don't duplicate automatic properties - Avoid PII in properties --- ## GA4 Implementation ### Quick Setup 1. Create GA4 p