Agent skill · data analytics · coreyhaines31
analytics
When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For choosing attribution models, comparing multi-touch/MMM/incrementality, or reconciling conflicting numbers across tools, see attribution. For A/B test measurement, see ab-testing.
Why this skill is useful
Provides a structured framework for implementing analytics tracking that includes event naming conventions and essential events, which the AI wouldn't reliably generate on its own.
What it needs
About 5k tokens when loaded. Last updated 2026-07-29. 43,366 stars on the source repository.
What this skill does
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.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, 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 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 --- Event Naming Conventions Recommended Format: Object-Action Best Practices Lowercase with underscores Be specific: ctaheroclicked vs. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills coreyhaines31/analytics