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.
- Installs
- 3.4K
- Last 24h
- +17
- Trending rank
- #6495
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/appeeky/aso-skills --skill app-analytics- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads app-analytics automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
- Check for
app-marketing-context.md— read it for context - Ask: What analytics tools do you currently use?
- Ask: What are your top 3 questions about your app's performance?
- Ask: What decisions do you need data to make?
- 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 resultsretention-optimization— Interpret retention datamonetization-strategy— Revenue metric optimizationua-campaign— Attribution and UA metrics
FAQ
What does the app-analytics 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.
How do I install app-analytics?
Run npx skills add https://github.com/appeeky/aso-skills --skill app-analytics in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/app-analytics/ (personal) or .claude/skills/app-analytics/ (project).
Which AI agents can use app-analytics?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is app-analytics safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains app-analytics?
It is published by appeeky in appeeky/aso-skills. It has 3,381 recorded installs.
More from appeeky/aso-skills
aso-audit
appeeky/aso-skills
When the user wants a full ASO health audit, review their App Store listing quality, or diagnose why their app isn't ranking. Also use when the user mentions "ASO audit", "ASO score", "why am I not ranking", "listing review", or "optimize my app store page". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
keyword-research
appeeky/aso-skills
When the user wants to discover, evaluate, or prioritize App Store keywords. Also use when the user mentions "keyword research", "find keywords", "search volume", "keyword difficulty", "keyword ideas", or "what keywords should I target". For implementing keywords into metadata, see metadata-optimization. For auditing current keyword performance, see aso-audit.
monetization-strategy
appeeky/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
appeeky/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.
competitor-analysis
appeeky/aso-skills
When the user wants to analyze competitors' App Store strategy, find keyword gaps, or understand competitive positioning. Also use when the user mentions "competitor analysis", "competitive research", "keyword gap", "what are my competitors doing", or "compare my app to". For keyword-specific research, see keyword-research. For metadata writing, see metadata-optimization.
screenshot-optimization
appeeky/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.
Popular data & databases skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pgcron, pgmq), vector/semantic search (pgvector), and restoring dumps (pgrestore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-client-api
prisma/skills
Prisma Client API reference covering model queries, filters, operators, and client methods. Use when writing database queries, using CRUD operations, filtering data, or configuring Prisma Client. Triggers on "prisma query", "findMany", "create", "update", "delete", "$transaction".
prisma-database-setup
prisma/skills
Deprecated compatibility name for prisma-orm-setup. Use only when a user or existing integration explicitly invokes prisma-database-setup; otherwise select prisma-orm-setup.
prisma-cli
prisma/skills
Prisma ORM 7 CLI reference for existing Prisma 7 applications or explicitly selected Prisma 7 workflows. Covers prisma init, generate, migrate, db, dev, studio, and mcp. For setup, connection repair, or Prisma 8, use prisma-orm-setup; not the Prisma Platform CLI.
prisma-postgres
prisma/skills
Deprecated compatibility name for prisma-postgres-setup. Use only when a user or existing integration explicitly invokes prisma-postgres; otherwise select prisma-postgres-setup.
prisma-driver-adapter-implementation
prisma/skills
Required reference for Prisma ORM 7 SQL driver adapter work. Use when implementing or modifying adapters, adding database drivers, or touching SqlDriverAdapter, Transaction, savepoint, result mapping, or DriverAdapterError behavior. Covers current transaction lifecycle, optional savepoint hooks, original database-error preservation, and verification.