App Store Connect Analytics: Practical Guide for Indie Developers
Use App Store Connect Analytics to understand discovery, downloads, revenue, subscriptions, and the weekly decisions behind your app business.
App Store Connect Analytics is where you investigate how people find, download, use, and pay for your app. Start there when a number moves and you need to understand why. Do not use it as the final record of what Apple will deposit in your bank account.
The useful approach is small: follow the path from discovery to download, then check whether the people you acquired are active and paying. This guide shows the metrics that answer those questions and the reporting surface to use when Analytics is not the right one.
Choose the right App Store Connect reporting surface
App Store Connect has three overlapping views of your business. Mixing them is how an ordinary reporting delay turns into a false alarm.
- Analytics: investigate discovery, downloads, engagement, sales, and subscriptions. It is best for asking what changed and narrowing the answer by source, territory, device, app version, or other available dimensions.
- Sales and Trends: track next-day app units and operational sales data. Use it for recurring daily or weekly business checks and detailed downloadable reports.
- Payments and Financial Reports: reconcile final payments. Those reports are based on settled transactions and finalized proceeds, so they are the accounting view.
Apple describes the same split in its reporting tools overview. Use Analytics to investigate a question, Sales and Trends for next-day operational reporting, and financial reports for final payments.
Start with the acquisition path
Read these three signals together, in this order:
Impressions → Product Page Views → Downloads
An impression means your app was viewed for more than one second on an App Store tab, including product page views. A product page view means someone reached your listing. Downloads then tell you whether exposure and interest became installs. Apple calculates conversion rate as total downloads and pre-orders divided by unique device impressions.
This is a diagnostic path, not a scorecard. For example:
- Impressions up, page views flat: you have more exposure, but the placement or message may not be convincing people to open the listing.
- Page views up, downloads flat: inspect your product page promise, screenshots, price, rating, and the audience your traffic is bringing.
- Downloads up, conversion rate flat: you may have more traffic, not a stronger product page. Check whether a source, territory, campaign, or editorial placement supplied the volume.
A conversion rate alone cannot prove that a screenshot, keyword, or campaign caused the change. It tells you which part of the path needs a closer look.
Use the right download number
Analytics separates First-Time Downloads, Redownloads, and Total Downloads. Total Downloads is the sum of the first two. A redownload is not an update, auto-download, or device restore.
For acquisition, start with First-Time Downloads. For overall App Store install activity, use Total Downloads. Do not substitute either number for App Units in Sales and Trends without checking the definition and reporting surface first. Apple's metric definitions are the source of truth when two labels look similar.
Find the source behind a change
After you spot a download change, go to the acquisition and source views before deciding what it means. Apple lets you break metrics down by sources such as App Store Search, App Store Browse, app referrers, web referrers, campaigns, territory, and device when those dimensions are available.
Ask a narrow question. “Did search drive the increase in Germany after the new release?” is useful. “Where did all these downloads come from?” is too broad to produce an action. Compare a stable period with the changed period, then write down the event you think may explain it: release, feature, campaign, pricing change, editorial placement, or nothing known yet.
Read revenue as operating data, not a payout forecast
Analytics sales metrics include Sales, Proceeds, Paying Users, In-App Purchases, and refund metrics. Sales is the amount billed to customers. Proceeds is Apple's estimate of what you will receive after applicable taxes and Apple's commission. It can differ from the final payment because of exchange rates and the transaction lifecycle.
That makes proceeds useful for weekly business direction. It does not replace the finalized payment record. When you need to reconcile a transfer, move to Payments and Financial Reports instead.
Read subscriptions as a lifecycle
If you sell auto-renewable subscriptions, avoid reducing the business to one active-subscriber total. Analytics can show active plans, free trials, paid offers, paid plans, billing issues, renewals, churn, and monthly recurring revenue.
A practical weekly read starts with three questions: are paid plans growing, are offers converting to paid plans, and did churn or billing issues move? Then filter by offer, territory, or acquisition source if you have a specific hypothesis. If you do not sell subscriptions, skip this section completely.
Use cohorts and benchmarks for context
A weekly chart tells you what changed. A cohort helps you see whether a group of users behaves differently over time. Apple offers download and subscription cohorts for questions such as whether a new source converts to paid more quickly, or whether an offer retains subscribers longer.
Benchmarks answer a different question: is this result typical for apps like mine? Apple compares eligible apps with similar peers across metrics such as conversion rate, retention, crash rate, and proceeds per paying user. Treat the result as context, not a ranking or a target to chase.
Treat usage and quality numbers as directional
Installations, sessions, active devices, retention, crashes, and deletions help you understand the experience after download. They do not describe every person who installed your app. Apple says usage data depends on users who opted in to share diagnostics and usage data, and some data can be withheld when privacy thresholds are not met.
This matters most for small apps. A blank chart is not proof that no one used the app, and a deletion-to-download ratio is not reliable when one side uses opt-in data. Use these metrics to compare your own periods and segments, then verify a serious quality issue with crash reports, support, or your own product analytics.
Why a metric can be missing or delayed
Not every metric exists for every app. App Store metrics need at least five first-time downloads or pre-orders, while download metrics need five first-time downloads. Usage metrics need at least five active devices in the selected date range and only include people who opted in to share usage data.
Sales data appears after at least one paid app or In-App Purchase. Subscription data appears after you have an active subscription product and subscriber. A campaign does not appear until more than a day has passed since launch and at least five App Units are attributed to it. These availability rules are why a blank chart often means “not enough eligible data yet,” not zero.
Timing is a separate issue. Sales and Trends daily reports are normally available the following day, weekly reports on Monday, and monthly reports five days after month end. Apple says they are generally available by 8 a.m. Pacific Time. Check the current availability schedule before treating the latest day as zero.
A 20-minute weekly App Store Connect review
- Check First-Time Downloads, Total Downloads, and conversion rate.
- Compare the change with the main source and top territories.
- Review sales, estimated proceeds, paying users, and refunds.
- For subscription apps, check paid plans, offer conversion, churn, and billing issues.
- Review active devices, retention, or crashes only as directional signals.
- Write one hypothesis and one next action. A useful review ends with a decision, not another dashboard tab.
When a dashboard becomes worth using
App Store Connect is excellent for investigating one app and one question. The friction changes when you repeat the same review every week, manage several apps, or need to separate client accounts. That is when recurring exports and browser tabs start hiding the story rather than clarifying it.
If you want your downloads, proceeds, subscriptions, and territories in one place without exporting reports, Appstead keeps them in local-first workspaces, one per account. You can also start with the App Store Connect API key setup guide when you are ready to connect a live workspace.
Frequently asked questions
What is App Store Connect Analytics used for?
Use it to investigate how people discover, download, engage with, and pay for your app. It also includes subscription, retention, quality, and feature-specific data when those capabilities apply to your app.
What is the difference between Analytics and Sales and Trends?
Analytics is for interactive exploration across the customer journey. Sales and Trends supplies next-day operational data on app units and sales. Payments and Financial Reports is the final-payment surface.
Why does App Store Connect Analytics show no data?
Check whether the metric meets Apple's availability rules first. App Store metrics need at least five first-time downloads or pre-orders, while download metrics need five first-time downloads. Usage needs five active opt-in devices in the selected date range, sales needs a purchase, and campaigns need more than a day plus five attributed App Units. Privacy rules can also withhold low-volume usage and quality data.
Is proceeds the same as my Apple payout?
No. Analytics proceeds is an estimate. Use Payments and Financial Reports to reconcile finalized payments.
Which metrics should an indie developer check every week?
Start with First-Time Downloads, Total Downloads, conversion rate, source, territory, sales, proceeds, paying users, and refunds. Add subscription and usage metrics only when they apply to your app and the data is available.