app-analytics

When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.

703 stars

Best use case

app-analytics is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.

Teams using app-analytics should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/app-analytics/SKILL.md --create-dirs "https://raw.githubusercontent.com/Eronred/aso-skills/main/skills/app-analytics/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/app-analytics/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How app-analytics Compares

Feature / Agentapp-analyticsStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

When the user wants to set up, interpret, or improve their app analytics and tracking. Also use when the user mentions "analytics", "tracking", "metrics", "KPIs", "App Store Connect analytics", "install tracking", "funnel", "attribution", or "how is my app performing". For A/B testing, see ab-test-store-listing. For retention metrics, see retention-optimization.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

Related Guides

SKILL.md Source

# 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 retention data
- `monetization-strategy` — Revenue metric optimization
- `ua-campaign` — Attribution and UA metrics

Related Skills

crash-analytics

703
from Eronred/aso-skills

When the user wants to monitor, triage, or reduce their app's crash rate — including setting up Crashlytics, prioritizing which crashes to fix first, interpreting crash data, and understanding how crashes affect App Store ranking. Use when the user mentions "crash", "crashlytics", "crash rate", "ANR", "app not responding", "crash-free sessions", "crash-free users", "symbolication", "stability", "firebase crashes", "app crashing", or "crash report". For overall analytics setup, see app-analytics.

ua-campaign

703
from Eronred/aso-skills

When the user wants to plan or optimize paid user acquisition campaigns. Also use when the user mentions "Apple Search Ads", "user acquisition", "paid ads", "UA", "ad campaign", "install campaign", "Facebook ads for apps", "TikTok ads", or "cost per install". For organic growth, see aso-audit. For launch-specific UA, see app-launch.

subscription-lifecycle

703
from Eronred/aso-skills

When the user wants to optimize their subscription business end-to-end — from trial start through renewal, cancellation, and win-back. Use when the user mentions "subscription lifecycle", "trial conversion", "churn", "cancellation", "win-back", "lapsed subscribers", "dunning", "billing retry", "grace period", "renewal rate", "subscriber LTV", or "resubscribe". For paywall design and pricing strategy, see monetization-strategy. For subscription analytics dashboards, see app-analytics.

seasonal-aso

703
from Eronred/aso-skills

When the user wants to optimize their App Store listing for seasonal events, holidays, or trending moments — including keyword opportunities, metadata updates, screenshot theming, and timing strategy. Use when the user mentions "seasonal", "holiday", "Christmas", "New Year", "Valentine's Day", "summer", "back to school", "seasonal keywords", "trending now", "limited time", or wants to capitalize on a calendar event. For general keyword research, see keyword-research. For full metadata rewrites, see metadata-optimization.

screenshot-optimization

703
from Eronred/aso-skills

When the user wants to design, optimize, or evaluate App Store screenshots and preview videos. Also use when the user mentions "screenshots", "app preview", "product page design", "screenshot design", "creative assets", or "what should my screenshots show". For A/B testing screenshots, see ab-test-store-listing. For full ASO audit, see aso-audit.

review-management

703
from Eronred/aso-skills

When the user wants to analyze, respond to, or improve their app reviews and ratings. Also use when the user mentions "reviews", "ratings", "negative reviews", "how to get more reviews", "review response", or "my rating is dropping". For broader ASO audit, see aso-audit. For retention issues causing bad reviews, see retention-optimization.

retention-optimization

703
from Eronred/aso-skills

When the user wants to reduce churn, improve user engagement, or increase lifetime value. Also use when the user mentions "retention", "churn", "users leaving", "engagement", "DAU/MAU", "user activation", or "why are users uninstalling". For onboarding-specific issues, see app-launch. For monetization, see monetization-strategy.

rating-prompt-strategy

703
from Eronred/aso-skills

When the user wants to improve their app's star rating, increase ratings volume, optimize when and how they prompt users for a review, or recover from a bad rating period. Use when the user mentions "app rating", "star rating", "review prompt", "SKStoreReviewRequest", "In-App Review API", "ask for review", "low rating", "rating drop", "get more reviews", or "recover from 1-star". For responding to reviews, see review-management. For overall ASO health, see aso-audit.

press-and-pr

703
from Eronred/aso-skills

When the user wants to get press coverage, media mentions, or editorial features for their app — including writing press releases, pitching journalists, getting on "best apps" lists, or building an app press kit. Use when the user mentions "press", "PR", "media coverage", "TechCrunch", "journalist", "press release", "app press kit", "get featured in media", "editorial coverage", "review from a blogger", or "app launch announcement". For Apple editorial featuring, see app-store-featured. For launch strategy, see app-launch.

onboarding-optimization

703
from Eronred/aso-skills

When the user wants to improve their app's onboarding experience, increase activation rate, reduce Day 1 drop-off, or optimize the first-run flow. Use when the user mentions "onboarding", "first-run", "activation", "tutorial", "day 1 retention", "new user flow", "permission prompts", "sign-up conversion", "onboarding funnel", or "users dropping off early". For overall retention strategy, see retention-optimization. For paywall placement, see monetization-strategy.

monetization-strategy

703
from Eronred/aso-skills

When the user wants to design or optimize their app's monetization — pricing, paywalls, subscriptions, or in-app purchases. Also use when the user mentions "pricing", "paywall", "subscription", "IAP", "how to monetize", "revenue optimization", "free trial", or "conversion to paid". For retention impact, see retention-optimization. For competitive pricing, see competitor-analysis.

metadata-optimization

703
from Eronred/aso-skills

When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.