Asc Metrics
Pull your real App Store Connect downloads, revenue, subscriptions, and country breakdowns via Appeeky instead of guessing from third-party estimates.
Overview
ASC Metrics is an agent skill for the Grow phase that analyzes your synced App Store Connect downloads, revenue, and subscription data through Appeeky.
Install
npx skills add https://github.com/eronred/aso-skills --skill asc-metricsWhat is this skill?
- Uses official ASC data synced through Appeeky Connect—not competitor estimates
- Supports downloads, revenue, subscriptions, trials, and country-level views
- Default 30-day windows with period-over-period comparisons
- GET /v1/connect/metrics/apps discovery flow before deep dives
- Requires Appeeky ASC integration; prompts setup if disconnected
- Up to 90 days of ASC history via nightly sync
- 2 Appeeky credits per metrics request on Indie plan or higher
Adoption & trust: 1.1k installs on skills.sh; 1.5k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You cannot tell whether growth came from a given country or price change because you lack quick access to your own ASC truth data.
Who is it for?
Indie developers with Appeeky + App Store Connect connected who want fast ASC performance reads and comparisons.
Skip if: Builders without ASC connected, Android-only storefront analytics, or market sizing of competitors where app-analytics estimates are appropriate.
When should I use this skill?
User asks about my downloads, my revenue, how their app is performing, ASC data, sales and trends, subscription numbers, or App Store Connect metrics.
What do I get? / Deliverables
You get structured answers from Appeeky’s ASC metrics APIs for the period and apps you choose, grounded in first-party store performance.
- Structured performance analysis for chosen metrics and period
- App list from connect metrics endpoint when scoping requests
- Action to connect ASC at appeeky.com/settings if missing
Recommended Skills
Journey fit
Grow is the canonical shelf because the skill answers how the app is performing over time with first-party ASC metrics. Analytics matches downloads, revenue, IAP, trials, period comparisons, and market breakdowns synced from App Store Connect.
How it compares
Use for your official ASC sync via Appeeky instead of generic app-analytics estimate skills aimed at third-party apps.
Common Questions / FAQ
Who is asc-metrics for?
Solo and indie iOS publishers using Appeeky with App Store Connect linked who need real download, revenue, and subscription metrics.
When should I use asc-metrics?
In Grow when reviewing analytics after launches or ASO changes, and in Launch when validating early store traction with ASC-backed numbers.
Is asc-metrics safe to install?
It accesses your business metrics through Appeeky; review the Security Audits panel on this page and your Appeeky/API credential scope before enabling.
SKILL.md
READMESKILL.md - Asc Metrics
# ASC Metrics You analyze the user's **official App Store Connect data** synced into Appeeky — exact downloads, revenue, IAP, subscriptions, and trials. This is first-party data, not estimates. ## Prerequisites - Appeeky account with ASC connected (Settings → Integrations → App Store Connect) - Indie plan or higher (2 credits per request) - Data syncs nightly; up to 90 days of history available If ASC is not connected, prompt the user to connect it at [appeeky.com/settings](https://appeeky.com) and return. ## Initial Assessment 1. Check for `app-marketing-context.md` — read it for app context 2. Ask: **What do you want to analyze?** (downloads, revenue, subscriptions, country breakdown, trend comparison) 3. Ask: **Which time period?** (default: last 30 days) 4. Ask: **Specific app or all apps?** ## Fetching Data ### Step 1 — List available apps ```bash GET /v1/connect/metrics/apps ``` Match the user's app to an `app_apple_id` if not already known. ### Step 2 — Get overview (portfolio) ```bash GET /v1/connect/metrics?from=YYYY-MM-DD&to=YYYY-MM-DD ``` ### Step 3 — Get app detail (single app) ```bash GET /v1/connect/metrics/apps/:appId?from=YYYY-MM-DD&to=YYYY-MM-DD ``` Response includes: `daily[]`, `countries[]`, `totals`. See full API reference: [appeeky-connect.md](../../tools/integrations/appeeky-connect.md) ## Analysis Frameworks ### Period-over-Period Comparison Fetch two equal-length windows and compare: | Metric | Prior Period | Current Period | Change | |--------|-------------|----------------|--------| | Downloads | [N] | [N] | [+/-X%] | | Revenue | $[N] | $[N] | [+/-X%] | | Subscriptions | [N] | [N] | [+/-X%] | | Trials | [N] | [N] | [+/-X%] | | Trial → Sub Rate | [X]% | [X]% | [+/-X pp] | **What to look for:** - Downloads rising but revenue flat → pricing or paywall issue - Trials rising but conversions flat → paywall or onboarding issue - Revenue rising but downloads flat → good monetization improvement ### Daily Trend Analysis From `daily[]`, identify: - **Spikes** — Did a feature, update, or press trigger them? - **Drops** — Correlate with app updates, seasonality, or algorithm changes - **Trend direction** — 7-day moving average vs prior 7 days ### Country Breakdown Sort `countries[]` by downloads and revenue: 1. **Top 5 by downloads** — Are you investing in ASO for these markets? 2. **Top 5 by revenue** — Higher ARPD (avg revenue per download) = prioritize ASO 3. **High downloads, low revenue** — Markets with weak monetization 4. **Low downloads, high revenue** — Under-tapped premium markets (localize) ### Revenue Quality Check Compute from the data: | Metric | Formula | Benchmark | |--------|---------|-----------| | ARPD | Revenue / Downloads | > $0.05 good; > $0.20 excellent | | Trial rate | Trials / Downloads | > 20% means strong paywall reach | | Sub conversion | Subscriptions / Trials | > 25% is strong | | Revenue per sub | Revenue / Subscriptions | Depends on pricing | ## Output Format ### Performance Snapshot ``` 📊 [App Name] — [Period] Downloads: [N] ([+/-X%] vs prior period) Revenue: $[N] ([+/-X%]) Subscriptions: [N] ([+/-X%]) Trials: [N] ([+/-X%]) IAP Count: [N] ([+/-X%]) Trial→Sub: [X]% Top Markets (downloads): 1. [Country] — [N] downloads, $[N] 2. [Country] — [N] downloads, $[N] 3. [Country] — [N] downloads, $[N] Key Observations: - [What the trend