Asc Metrics

作者 appeeky3919d7c27402无许可证2.1K 个星标收录于 2026年10月8日更新于 2026年10月8日仓库2天前更新

When the user wants to analyze their own app's actual performance data from App Store Connect — real downloads, revenue, IAP, subscriptions, trials, or country breakdowns synced via Appeeky Connect. Use when the user asks about "my downloads", "my revenue", "how is my app performing", "ASC data", "sales and trends", "my subscription numbers", "App Store Connect metrics", or wants to compare periods or top markets. For third-party app estimates, see app-analytics. For subscription analytics depth, see monetization-strategy.

AI 生成的概览

分析开发者通过 Appeeky 同步的自有 App Store Connect 数据,涵盖下载量、收入、订阅与市场分布。

功能
引导智能体从 Appeeky Connect 接口拉取指定应用和日期范围的第一方 App Store Connect 数据。它会进行同期对比、分析每日趋势、按国家拆分结果,并计算 ARPD、试用转订阅率等收入质量指标。最终产出包含关键观察与建议行动的业绩快照,并对超过 20% 的变化发出提醒。
适用场景
适用于用户询问自己应用在 App Store Connect 中的下载量、收入、应用内购买、订阅、试用或国家分布时。也适合做同期对比、热门市场分析,以及诊断自有指标的突然下跌或飙升。
运行要求
需要已连接 App Store Connect 的 Appeeky 账户,Indie 或更高套餐(每次请求 2 个积分),并能访问 Appeeky Connect API。数据每晚同步,最多保留 90 天历史。仅为说明文档,不附带脚本。

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 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

Analysis Frameworks

Period-over-Period Comparison

Fetch two equal-length windows and compare:

MetricPrior PeriodCurrent PeriodChange
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:

MetricFormulaBenchmark
ARPDRevenue / Downloads> $0.05 good; > $0.20 excellent
Trial rateTrials / Downloads> 20% means strong paywall reach
Sub conversionSubscriptions / Trials> 25% is strong
Revenue per subRevenue / SubscriptionsDepends 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 means]- [Any anomaly and likely cause]- [Opportunity identified]
Recommended Actions:1. [Specific action based on data]2. [Specific action based on data]

Trend Alert

When a significant change (>20%) is detected, flag it:

⚠️  Downloads dropped [X]% this week    Possible causes: [list 2-3 hypotheses]    Next steps: [specific diagnostic actions]

Common Questions

"Why did my downloads drop?"

  1. Pull daily trend — when did it start?
  2. Check if an update shipped on that date
  3. Check keyword rankings (use keyword-research skill)
  4. Check competitor activity (use competitor-analysis skill)

"Which countries should I localize for?" Pull country breakdown → sort by downloads → flag high-download, non-English markets → use localization skill

"Is my monetization improving?" Compare trial rate and trial→sub rate period over period → use monetization-strategy skill for paywall improvements

Related Skills

  • app-analytics — Full analytics stack setup and KPI framework
  • monetization-strategy — Improve subscription conversion and paywall
  • retention-optimization — Reduce churn using the metrics as input
  • localization — Expand top-performing markets seen in country data
  • ua-campaign — Validate whether paid installs show in downloads spike

来源与署名

来源:appeeky/aso-skills位于skills/asc-metrics提交3919d7c

许可证: 无许可证

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架