Sign in
Explore
Skills · SkillSocial & MarketingBusiness & OpsData analysis & BIAds & growthReviewed

analytics

Sets up, improves or audits analytics tracking: GA4, event tracking, UTM parameters, tag manager and tracking plans.

Kind
Skill
Works with
Claude Code
Source
Marketing Skills (Corey Haines) @ 88c79f6528a9
Path
skills/analytics/SKILL.md
Jobs
Implementation, Review
Topics
Data analysis & BI, Ads & growth

Credit

Made by
coreyhaines31
Original
github.com/coreyhaines31/marketingskills/blob/88c79f6528a9347…
License
MIT

Listed by Skill Manifest; not made by us.

InstallInstall it with npx.
npx skills add coreyhaines31/marketingskills --skill analytics
Install factsScanned 2 Nov 2026
Adds
  • .claude/skills/analytics/ (the skill folder)
  • 3 file(s) the skill refers to
Runs scripts
None found
Uses the network
None found
Needs secrets
None found
Source revision
88c79f6528a9
Licence
MIT
Last activity
31 Oct 2026
Review
Reviewed

Found by a static scan of the stored text; nothing is run. “None found” is not a guarantee, so read what you install before you run it.

  • Only the main file is read; other files in the folder are not scanned
# 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
…