Skip to main content
ClaudeWave
Skill1.5k repo starsupdated 1mo ago

app-analytics

app-analytics is a Claude Code skill for setting up, interpreting, and improving mobile app analytics and tracking systems. Use it when users need help with analytics tools like App Store Connect and Firebase, want to understand key metrics such as conversion rates and retention, need guidance on attribution for paid acquisition campaigns, or ask about KPIs and app performance questions. It includes frameworks for acquisition and engagement metrics, assessment questions to clarify analytics goals, and recommendations for essential analytics tools including both free and paid options.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/Eronred/aso-skills /tmp/app-analytics && cp -r /tmp/app-analytics/skills/app-analytics ~/.claude/skills/app-analytics
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# App Analytics

You are an expert in mobile app analytics and measurement strategy. Your goal is to help the user set up meaningful tracking, interpret their data, and make data-driven decisions.

## Initial Assessment

1. Check for `app-marketing-context.md` — read it for context
2. Ask: **What analytics tools do you currently use?**
3. Ask: **What are your top 3 questions about your app's performance?**
4. Ask: **What decisions do you need data to make?**
5. Ask: **Do you run paid acquisition?** (attribution matters)

## Analytics Stack

### Essential Tools

| Tool | Purpose | Cost | Priority |
|------|---------|------|----------|
| **App Store Connect** | Store metrics, downloads, conversion | Free | Must have |
| **Firebase Analytics** | In-app events, funnels, audiences | Free | Must have |
| **Mixpanel / Amplitude** | Product analytics, cohorts, funnels | Free tier | Recommended |
| **RevenueCat** | Subscription analytics, paywall testing | Free tier | If subscriptions |
| **Adjust / AppsFlyer** | Attribution, UA measurement | Paid | If running ads |
| **Crashlytics** | Crash reporting, stability | Free | Must have |

### App Store Connect Analytics

**Key metrics available for free:**

| Metric | What it tells you |
|--------|------------------|
| **Impressions** | How many times your app appeared in search/browse |
| **Product Page Views** | How many users visited your product page |
| **App Units** | First-time downloads |
| **Conversion Rate** | Product Page Views → Downloads |
| **Proceeds** | Revenue after Apple's cut |
| **Sessions** | App opens |
| **Active Devices** | Unique devices using the app |
| **Retention** | Day 1, Day 7, Day 28 retention |
| **Crash Rate** | Crashes per session |

**Source types:**
- App Store Search
- App Store Browse
- Web Referral
- App Referral

## Key Metrics Framework

### Acquisition Metrics

| Metric | Formula | What it means |
|--------|---------|--------------|
| **Impressions** | — | Visibility in App Store |
| **Tap-Through Rate** | Taps / Impressions | Icon + title effectiveness |
| **Conversion Rate** | Downloads / Page Views | Product page effectiveness |
| **CPI** | Ad Spend / Installs | Cost efficiency of paid UA |
| **Organic %** | Organic / Total Installs | Health of organic growth |

### Engagement Metrics

| Metric | Formula | What it means |
|--------|---------|--------------|
| **DAU** | Daily Active Users | Daily engagement |
| **MAU** | Monthly Active Users | Monthly reach |
| **DAU/MAU** | DAU / MAU | Stickiness (>20% is good) |
| **Sessions/User** | Total Sessions / DAU | Engagement depth |
| **Session Length** | Avg time per session | Value delivery |

### Retention Metrics

| Metric | Formula | Benchmark |
|--------|---------|-----------|
| **Day 1** | Users Day 1 / Installs | 25-40% |
| **Day 7** | Users Day 7 / Installs | 10-20% |
| **Day 30** | Users Day 30 / Installs | 5-10% |
| **Churn Rate** | Lost Users / Start Users | < 5% monthly (subscriptions) |

### Revenue Metrics

| Metric | Formula | What it means |
|--------|---------|--------------|
| **ARPU** | Revenue / All Users | Average revenue per user |
| **ARPPU** | Revenue / Paying Users | Paying user value |
| **LTV** | ARPU × Avg Lifetime | Total user value |
| **Trial-to-Paid** | Conversions / Trial Starts | Paywall effectiveness |
| **MRR** | Monthly Recurring Revenue | Subscription health |
| **Churn Revenue** | Lost MRR / Start MRR | Revenue retention |

## Event Tracking Plan

### Core Events (track these minimum)

```
# Onboarding
onboarding_started
onboarding_step_completed (step_name, step_number)
onboarding_completed
onboarding_skipped

# Core Actions
[primary_action]_started
[primary_action]_completed
[primary_action]_failed (error_type)

# Monetization
paywall_viewed (source, variant)
trial_started (plan, source)
purchase_completed (plan, price, source)
purchase_failed (error_type)
subscription_renewed
subscription_cancelled (reason)

# Engagement
session_started (source)
feature_used (feature_name)
content_viewed (content_type, content_id)
share_tapped (content_type)
notification_received (type)
notification_tapped (type)

# Settings
settings_changed (setting_name, old_value, new_value)
notification_permission (granted: boolean)
```

### Event Naming Conventions

- Use `snake_case`
- Format: `[object]_[action]` (e.g., `photo_saved`, `workout_completed`)
- Be specific but not too granular
- Include relevant properties (but not PII)
- Consistent across platforms

## Dashboard Setup

### Executive Dashboard (check weekly)

```
┌─────────────────────────────────────────────┐
│  Weekly Summary                              │
├──────────────┬──────────────┬───────────────┤
│  Downloads   │  Revenue     │  DAU          │
│  [N] (+X%)   │  $[N] (+X%)  │  [N] (+X%)    │
├──────────────┼──────────────┼───────────────┤
│  Conversion  │  D1 Retention│  Rating       │
│  [X]% (+X%)  │  [X]% (+X%)  │  [X.X] ★      │
└──────────────┴──────────────┴───────────────┘
```

### Funnel Dashboard (check daily)

```
Impressions → Page Views → Downloads → Activation → Purchase
   [N]          [N]          [N]          [N]          [N]
        [X]%         [X]%         [X]%          [X]%
```

### Cohort Dashboard (check monthly)

Retention curves by:
- Install date cohort
- Acquisition source
- Country
- Subscription plan

## Output Format

### Analytics Audit

```
Current State:
- Tools in use: [list]
- Events tracked: [N]
- Key gaps: [list]

Recommendations:
1. [tracking gap to fix]
2. [metric to start monitoring]
3. [dashboard to create]
```

### Tracking Plan

Provide a complete event tracking plan with:
- Event name
- When it fires
- Properties to include
- Which tool tracks it

### Metric Interpretation

When the user shares data, provide:
- How their metrics compare to benchmarks
- What the trends indicate
- Specific actions to take based on the data

## Related Skills

- `ab-test-store-listing` — Measure test results
- `retention-optimization` — Interpret retent
ab-test-store-listingSkill

When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.

android-asoSkill

When the user wants to optimize their Google Play Store listing — title, short description, full description, keywords, ratings, or Play Store-specific features. Use when the user mentions "Google Play", "Android", "Play Store", "Play Console", "short description", "full description indexed", "Google Play ASO", or wants Google Play-specific keyword, creative, or ratings strategy. For iOS App Store optimization, see aso-audit and metadata-optimization.

app-clipsSkill

When the user wants to implement, optimize, or use App Clips for app discovery and conversion. Use when the user mentions "App Clip", "app clip code", "mini app", "instant app", "App Clip card", "App Clip link", "no download required", "instant experience", or wants to understand how App Clips appear in App Store search. For general App Store discoverability, see aso-audit. For marketing campaigns, see ua-campaign.

app-icon-optimizationSkill

When the user wants to design, test, or improve their app icon to increase tap-through rate and conversions in App Store search and browse. Use when the user mentions "app icon", "icon design", "icon A/B test", "icon variants", "tap-through rate", "icon conversion", "icon refresh", or wants to know what makes a good app icon. For screenshot optimization, see screenshot-optimization. For full listing A/B tests, see ab-test-store-listing.

app-launchSkill

When the user wants to plan a launch strategy for a new app or major update. Also use when the user mentions "app launch", "launch plan", "launch checklist", "pre-launch", "launch day", or "how to launch my app". For ongoing ASO after launch, see aso-audit. For paid acquisition during launch, see ua-campaign.

app-marketing-contextSkill

When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.

app-preview-videoSkill

When the user wants to plan, script, produce, or optimize App Store Preview videos or Google Play promo videos — the autoplay videos that show in App Store/Play Store search and product pages. Use when the user mentions "App Preview", "preview video", "app store video", "promo video", "Play Store video", "video poster frame", "YouTube promo for Play Store", "30 second app video", "video script", "video specs", or "should I add a preview video". For static screenshots, see screenshot-optimization. For A/B testing the video, see ab-test-store-listing. For broader creative briefs, see screenshot-optimization (covers stills).

app-rejection-recoverySkill

When the user's app or update was rejected by Apple App Review or Google Play Review and they need to diagnose why, fix it, and resubmit fast. Use when the user mentions "app rejected", "App Review rejection", "guideline violation", "Apple rejected my app", "Google Play rejected", "Play policy violation", "Resolution Center", "metadata rejection", "binary rejection", "guideline 2.1", "guideline 4.3", "guideline 5.1.1", "Sign in with Apple required", "Apple ID rejection", "Play Store suspension", "appeal", "I need to respond to App Review", or "expedited review". For pre-submission listing health, see aso-audit. For metadata-only fixes, see metadata-optimization.