Skip to main content
skill CX Codex

app-analytics — Claude Code skill: what it does, how to install

Audits mobile tracking stacks, designs event plans, and interprets App Store Connect metrics. Useful before running paid campaigns or restructuring in-app subscription funnels.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add appeeky/aso-skills --skill app-analytics -a claude-code
Open on GitHub

What app-analytics does

This skill reviews your mobile analytics setup. It starts by checking app-marketing-context.md, gathering current tooling, and asking key performance questions. The resulting audit highlights tracking gaps and defines executive and funnel dashboards.

The framework organizes metrics across acquisition, engagement, retention, and revenue. It includes formulas for metrics like DAU/MAU stickiness, trial-to-paid conversion, and churn rate alongside standard benchmarks, such as Day 1 retention between 25-40%. Events follow a snake_case convention (object_action) for onboarding and paywall interactions.

If you run paid user acquisition, you will need a dedicated tracker like Adjust or AppsFlyer, because free App Store Connect data cannot handle ad attribution.

What it helps with

  • create an event tracking plan for onboarding and paywalls
  • audit missing metrics before launching paid user acquisition
  • benchmark Day 1, Day 7, and Day 30 retention rates
  • set up conversion funnels from impressions to first purchase

Example prompts for the agent

  • Audit my app analytics setup and suggest missing events
  • How do I structure tracking for my subscription paywall?
  • Analyze my App Store Connect conversion rate and Day 1 retention

How to install app-analytics

1Skills CLI (Vercel)

npx skills add appeeky/aso-skills --skill app-analytics -a claude-code

2Manually: put the files in place

~/.claude/skills/app-analytics/SKILL.md

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

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

Questions about app-analytics

How do I install app-analytics in Claude Code?

Run npx skills add appeeky/aso-skills --skill app-analytics -a claude-code in your terminal.

What does the app-analytics skill do?

It audits your mobile tracking setup, designs a standardized event schema, and helps interpret store and product metrics against industry benchmarks.

Does app-analytics require specific context files?

The skill checks for app-marketing-context.md in the project root to load existing app background and tooling details before asking questions.

Source text

SKILL.md · MIT
---
name: app-analytics
description: 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.
metadata:
  version: 1.0.0
---

# 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

© appeeky · MIT · appeeky/aso-skills

Similar skills

Everything for Mobile →

From the same set39

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