Skip to main content
skill CX Codex

data-and-funnel-analytics — Claude Code skill: setup and guide

Sets up GA4 and GTM event tracking, diagnoses funnel drop-offs, and calculates product retention metrics.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add manojbajaj95/claude-gtm-plugin --skill data-and-funnel-analytics -a claude-code
Open on GitHub

What data-and-funnel-analytics does

The skill establishes tracking standards and analytics evaluation rules for digital products. It enforces an object_action format in lowercase snake_case, provides property schemas for marketing and in-app actions, and outputs code snippets for gtag.js and dataLayer. For traffic evaluation, it compares bounce rates and scroll depth against built-in benchmark tables.

Product analytics include North Star definition, user retention tracking across D1 and D30 intervals, and unit economics such as LTV to CAC. When tagging traffic, the rules strictly prohibit UTM parameters on internal site links because they overwrite session attribution inside GA4.

The agent references local project context in strategy/brand.md and routes output drafts to content/<platform>/drafts/. Experiment workflows are deliberately excluded and handed off to ab-test-setup. PII hygiene is mandatory: raw email addresses or phone numbers cannot enter event properties, requiring hashed user IDs instead.

What it helps with

  • Create an event tracking plan for GA4 and Google Tag Manager
  • Identify where users drop off across conversion funnels
  • Evaluate D1, D7, and D30 user retention cohorts
  • Configure UTM parameters without corrupting session attribution

Example prompts for the agent

  • Generate a GA4 tracking plan for our checkout flow
  • Analyze why our onboarding funnel conversion is dropping
  • Check our D1 and D7 retention numbers against industry benchmarks

How to install data-and-funnel-analytics

1Skills CLI (Vercel)

npx skills add manojbajaj95/claude-gtm-plugin --skill data-and-funnel-analytics -a claude-code

2Manually: put the files in place

~/.claude/skills/data-and-funnel-analytics/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/data-and-funnel-analytics/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about data-and-funnel-analytics

How to install data-and-funnel-analytics in Claude Code?

Run npx skills add manojbajaj95/claude-gtm-plugin --skill data-and-funnel-analytics -a claude-code in your terminal. The configuration is stored at ~/.claude/skills/data-and-funnel-analytics/SKILL.md.

What does data-and-funnel-analytics do?

It guides GA4 and GTM tracking implementations, audits conversion funnels, and evaluates retention metrics. It ensures teams measure actionable product events rather than arbitrary data.

Can data-and-funnel-analytics configure A/B tests?

No, test design and experimentation workflows are deferred to ab-test-setup. This skill focuses on event tracking, funnel diagnostics, and cohort analytics.

Source text

SKILL.md · MIT
---
name: data-and-funnel-analytics
description: Analytics tracking, interpretation, funnel analysis, product metrics, and ROI measurement. Use when setting up GA4/GTM tracking, interpreting analytics data, analyzing conversion funnels, calculating ROI, or measuring product engagement. Triggers on "analytics," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "funnel analysis," "conversion rates," "user flow," "cohort analysis," "retention," "product metrics," "North Star metric," "ROI," "break-even," "payback period," "investment analysis," "validate my funnel," "why isn't my funnel converting," or "executive financial report." For A/B test setup, see ab-test-setup.
---

# Data & Funnel Analytics

## Workspace Context

Read bootstrap context before asking questions: `strategy/brand.md` for brand, audience, offer, channels, tools, constraints, and metrics; `about/me.md` for personal voice; `content/ideas.md` and `content/calendar.md` for content planning. Use legacy product-marketing context files only as fallback. Save generated drafts to `content/<platform>/drafts/YYYY-MM-DD_short-topic-slug.md`, and route durable learnings back to `strategy/brand.md`, `about/me.md`, or `content/ideas.md`.

## Operating Contract

This skill is self-contained for its frontmatter scope: use its local instructions, references, scripts, and assets as the playbook; ask only for missing task-specific inputs; hand off to adjacent skills instead of expanding scope; and return an actionable artifact, decision, plan, draft, or diagnostic.



End-to-end analytics: set up tracking, interpret data, analyze funnels, measure product engagement, validate conversion paths, and calculate ROI.

**Principle:** Track for decisions, not data — every event should inform an action.

---

## Analytics Tracking

### Event Naming Convention

Format: `object_action` in lowercase snake_case.

```
signup_completed | cta_hero_clicked | checkout_started | onboarding_step_completed
```

Rules: Specific over vague (`cta_hero_clicked` not `button_clicked`), past tense for completed actions, context in properties not event name.

### Tracking Plan

| Category | Event | Key Properties |
|----------|-------|---------------|
| **Marketing** | `page_view` | page_title, page_location, referrer |
| | `cta_clicked` | button_text, location, page |
| | `form_submitted` | form_type, page |
| | `signup_completed` | method, plan |
| **Product** | `onboarding_step_completed` | step_number, step_name |
| | `feature_used` | feature_name, context |
| | `trial_started` | plan, source |
| | `purchase_completed` | plan, value, currency |
| **E-commerce** | `product_viewed` | product_id, category, price |
| | `product_added_to_cart` | product_id, price, quantity |
| | `checkout_started` | cart_value, items_count |

### Standard Properties

- **User context:** user_id, user_type (free/paid/admin), plan_type
- **Attribution:** source, medium, campaign, content, term (UTM params)
- **Page:** page_title, page_location, content_group
- **PII hygiene:** Never send email, name, or phone as event properties. Use hashed user IDs only.

### GA4 Implementation

```javascript
// gtag.js custom event
gtag('event', 'signup_completed', {
  'method': 'email',
  'plan': 'free',
  'user_id': userId
});

// GTM dataLayer
dataLayer.push({
  'event': 'signup_completed',
  'method': 'email',
  'plan': 'free'
});
```

**Enhanced Measurement** (enable in GA4): page_view, scroll, outbound_click, site_search, video_engagement, file_download.

**Conversions:** Admin → Events → Toggle "Mark as conversion." Counting: once per session (form submit) or every time (purchase).

### UTM Parameters

Convention: `utm_source={channel}&utm_medium={cpc|email|organic|social}&utm_campaign={id}&utm_content={variant}&utm_term={keyword}`

- Apply to ALL paid and email links
- Never use on internal links (breaks session attribution)
- Lowercase, hyphens not spaces
- Document in a UTM tracking sheet

### Privacy & Compliance

- GDPR/CCPA: Implement consent management, block GA4 until consent granted
- GA4 data retention: 14 months max (Admin → Data Settings)
- IP anonymization enabled

---

## Analytics Interpretation

### GA4 Benchmarks

| Metric | Good | Warning | Poor | Action When Poor |
|--------|------|---------|------|------------------|
| Avg Time on Page | >3 min | 1–3 min | <1 min | Improve content depth |
| Bounce Rate | <40% | 40–70% | >70% | Add internal links, improve intro |
| Engagement Rate | >60% | 30–60% | <30% | Review content quality |
| Scroll Depth | >75% | 50–75% | <50% | Add visual breaks |
| Pages/Session | >2.5 | 1.5–2.5 | <1.5 | Improve internal linking |

### Google Search Console Benchmarks

| Metric | Good | Warning | Poor | Action When Poor |
|--------|------|---------|------|------------------|
| CTR | >5% | 2–5% | <2% | Improve title/meta description |
| Avg Position | 1–3 | 4–10 | >10 | Strengthen content, build links |
| Impressions | Growing | Stable | Declining | Refresh content |

### Traffic Quality Matrix

```
                    High Engagement
                          │
           ┌──────────────┼──────────────┐
           │  HIDDEN GEM  │   STAR       │
           │  Low traffic  │   High traffic│
           │  → Promote   │   → Maintain  │
Low ───────┼──────────────┼──────────────┼─── High
Traffic    │  UNDERPERFORM│   LEAKY      │   Traffic
           │  Low traffic  │   High traffic│
           │  → Rework    │   → Optimize  │
           └──────────────┼──────────────┘
                          │
                    Low Engagement
```

### Anomaly Detection

| Metric | Significant Change | Alert Level |
|--------|-------------------|-------------|
| Traffic | ±30% WoW | HIGH |
| CTR | ±1pp WoW | MEDIUM |
| Position | ±5 positions | HIGH |
| Bounce Rate | ±10pp WoW | MEDIUM |

---

## Product Analytics

### North Star Metric

The ONE metric that represents customer value:

| Company | North Star |
|---------|-----------|
| Slack | Weekly Active Users |
| Airbnb | Nights Booked |
| Spotify | Time Listening |
| Shopify | GMV |

Criteria: Represents customer value, correlates with revenue, measurable frequently, rallies the team.

### Key Metrics by Stage

| Stage | Metrics |
|-------|---------|
| **Acquisition** | Traffic sources, CPC, visitor → signup rate |
| **Activation** | Signup → first core action, time to value, onboarding completion |
| **Retention** | DAU/MAU (stickiness), D1/D7/D30 retention, churn rate |
| **Revenue** | MRR/ARR, ARPU, LTV, LTV:CAC ratio |
| **Referral** | Viral coefficient, referral signups, NPS |

### Retention Benchmarks

| Timeframe | Good | Bad |
|-----------|------|-----|
| D1 | 60–80% | <40% |
| D7 | 40–60% | <10% |
| D30 | 30–50% | <2% |

Good = flattening curve. Bad = steep drop-off.

### Dashboard Design

- **Executive:** North Star Metric (big number), revenue (MRR/ARR), key trends
- **Product:** Active users, feature usage, retention cohorts, funnels
- **Marketing:** Traffic sources, conversion rates, CPA, ROI by channel

---

## Funnel Analysis

### Core Workflow

1. Load and merge user journey data
2. Define funnel steps and calculate step-by-step conversion rates
3. Segment by user attributes (device, cohort, plan)
4. Visualize bottlenecks
5. Generate optimization recommendations

### Common Funnel Types

| Funnel | Steps |
|--------|-------|
| **E-commerce** | Promotion → Search → Product View → Add to Cart → Purchase |
| **SaaS Signup** | Landing Page → Sign Up → Email Verify → Onboarding Complete |
| **Content** | Article View → Comment → Share → Subscribe |

### Analysis Patterns

- **Bottleneck identification** — Steps with highest drop-off rates
- **Segment comparison** — Conversion across user groups
- **Temporal analysis** — Conversion over time
- **A/B testing** — Compare funnel variations

See `examples/` for Python implementations with Plotly visualizations.

---

## Funnel Validation (DotCom Secrets)

Score existing funnels against Russell Brunson's framework: **Hook → Story → Offer**.

### Scoring Dimensions

| Dimension | Weight | What It Measures |
|-----------|--------|------------------|
| Hook Strength | 2x | Stops the scroll, grabs attention |
| Story Connection | 1.5x | Creates emotional connection and belief |
| Offer Clarity | 2x | Clear, compelling, irresistible |
| Value Ladder Fit | 1x | Fits the ascension path |
| Traffic Match | 1.5x | Matched to traffic temperature |
| Conversion Path | 1x | Next step obvious and frictionless |

### Rating Scale

| Score | Verdict |
|-------|---------|
| 85–100 | Conversion Machine — Ready to scale |
| 70–84 | Strong Funnel — Fix weak points, then scale |
| 55–69 | Leaky Funnel — Fix before scaling traffic |
| 40–54 | Broken Funnel — Rebuild key components |
| 0–39 | Non-Functional — Start over |

### Traffic Temperature

| Temperature | They Know | Appropriate Funnel |
|-------------|-----------|-------------------|
| Cold | Nothing about you | Lead funnel, value-first content |
| Warm | Problem + your solution | Tripwire, webinar, challenge |
| Hot | Ready to buy | Sales page, order form, call booking |

For complete scoring criteria and examples, see [references/full-guide.md](references/full-guide.md).

---

## ROI Analysis

### Core Metrics

**ROI:** `(Net Profit / Total Investment) × 100%`
- ✅ INVEST: ROI > 100% (realistic case)
- ⚠️ REVIEW: ROI 50–100%
- ❌ REJECT: ROI < 50%

**Break-Even:** `Investment / Monthly Net Profit`
- ✅ INVEST: Break-even < 50% of realistic target
- ❌ REJECT: Break-even > 70%

**Payback Period:** `Investment / Monthly Net Profit`
- ✅ INVEST: < 12 months
- ⚠️ REVIEW: 12–24 months
- ❌ REJECT: > 24 months

### 3-Scenario Analysis

Always model Best / Realistic / Worst:

| Case | Assumptions | Revenue | Profit | ROI | Assessment |
|------|------------|---------|--------|-----|------------|
| **Worst** | Pessimistic | | | | Risk level |
| **Realistic** | Expected | | | | Target |
| **Best** | Optimistic | | | | Upside |

**Decision rule:** If worst-case ROI ≥ 0%, investment is low-risk.

### Executive Summary Template

```
[Investment] achieves [ROI%] ROI at [conversion/growth rate].
Break-even occurs at [threshold], with payback in [months].
Investment is [recommended/not recommended] because [reason].
```

For detailed formulas (NPV, LTV, CAC, sensitivity analysis), see [references/roi-reference.md](references/roi-reference.md).

---

## Validation & QA

### Before Launch
- [ ] Events fire in GA4 DebugView
- [ ] Properties have expected values
- [ ] No duplicate events
- [ ] Conversions marked correctly
- [ ] UTM parameters captured on landing

### Ongoing
- **Weekly:** Check for sudden drops in key events (>20% change = investigate)
- **Monthly:** Audit for new pages/features without tracking
- **Quarterly:** Full tracking plan review — remove stale events, add missing ones

---

## Tools

| Category | Tools |
|----------|-------|
| **Event Tracking** | Mixpanel, Amplitude, PostHog (open-source) |
| **Session Recording** | FullStory, LogRocket, Hotjar |
| **A/B Testing** | Optimizely, VWO |
| **Web Analytics** | GA4, Google Search Console |
| **Tag Management** | Google Tag Manager |

---

## Related Skills

- **ab-test-setup** — A/B test measurement and setup
- **seo-and-aeo-strategy** — Measuring SEO/AEO performance
- **conversion-rate-optimization** — Optimizing conversion after funnel analysis
- **executive-dashboard-generator** — Building dashboards from analytics data

© manojbajaj95 · MIT · manojbajaj95/claude-gtm-plugin

Similar skills

Everything for Marketing and content →

From the same set11

market-research-analysis Works out TAM, SAM and SOM, maps competitors and drafts a consulting-style report. Useful before a launch or when you need to size a market. CX Codex +1 871installs social-media-management A skill for planning and repurposing posts across LinkedIn, X, Instagram, TikTok and more. Useful when the content calendar lives only in your head. CX Codex +1 498installs marketing-campaign-management A skill for planning marketing campaigns: funnel stages, content calendar, buyer psychology and a catalog of 140 tactics. Useful when you need a launch plan, not generic advice. CX Codex +1 385installs conversion-rate-optimization Audits marketing pages and capture forms, pinpoints friction, and builds test hypotheses. Use it when landing page signups stall or before launching ad campaigns. CX Codex +1 350installs copywriting-core A skill for writing and editing marketing copy: landing pages, emails, headlines, CTAs. Built on positioning and customer language. CX Codex +1 345installs growth-strategy Designs compounding growth loops, evaluates network effects, and models unit economics. It shifts product teams from linear funnels to product-led loops. CX Codex +1 337installs lead-generation-and-demand A B2B demand generation playbook: ICP, funnel stages, channel picks, lead scoring and CAC math. Useful when you are building a pipeline from scratch. CX Codex +1 333installs go-to-market-strategy Takes a launch from GTM motion choice to launch day: positioning, channels, a six-week timeline and the marketing pack. CX Codex +1 328installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor