Sales Reports and App Analytics: Apple vs Google Play
Both platforms offer built-in financial and behavioral analytics tools, but the structure and depth of reporting differ noticeably. Here’s where to find what, and the practical differences that matter.
Apple: reports in App Store Connect
Sales and Trends
Data on sales, downloads, updates, and refunds, filterable by territory, device, and OS version. Data typically updates with a one-day delay.
App Analytics
A separate section for behavioral analytics: product page view counts, conversion to download, cohort-based retention, and engagement (sessions, session length).
Payments and Financial Reports
Detailed financial reports by region, including Apple’s commission and final payout amounts — available a few days after the reporting period closes.
Data export
Most reports can be exported to CSV for further analysis, and for deeper automation, pulled through the App Store Connect API (see the separate getting-started article).
Google Play: reports in Play Console
Statistics
Install, uninstall, active user, and rating metrics, with flexible filtering by device, country, and Android version.
Financial reports
A detailed breakdown by sale, including country and transaction type (one-time purchase, subscription) — organized by settlement periods matching the payout cycle.
Android vitals
A section unique to Google Play, tracking technical stability metrics: crash rate, ANR (Application Not Responding) rate, and app startup time — this directly affects the app’s visibility in Google Play search.
Export and automation
Reports can be downloaded manually, and for automation, pulled via the Google Play Developer Reporting API — separate from the main Android Publisher API used for publishing (see the Service Account article).
Key differences
| Apple | Google Play | |
|---|---|---|
| Data lag | Usually 1 day for sales, longer for financial reports | Usually faster for core metrics |
| Technical stability metrics | Limited, via Xcode Organizer (crashes) | A full dedicated Android vitals section |
| Regional granularity | High | High |
| API for automating reports | App Store Connect API | Google Play Developer Reporting API |
Practical tips
- Set up regular financial report pulls via API if you manage multiple apps — manually reconciling data per app is tedious and error-prone.
- Check Android vitals at least weekly — poor stability metrics directly hurt organic visibility on Google Play, unlike Apple, where it doesn’t affect ranking as directly.
- Use cohort retention analysis in App Analytics/Statistics to gauge real retention, not just install counts — installs without retention usually signal an onboarding problem, not a traffic acquisition problem.
FAQ
Can I get a consolidated report covering both platforms in one place?
There’s no built-in tool combining Apple and Google Play data — that requires third-party BI tools (Looker Studio, Tableau, and similar), fed by both platforms’ APIs.
Do the reports show real-time data?
No — both platforms deliver data with a lag, ranging from a few hours to a full day depending on the report type; neither guarantees instant accuracy.
Do I need separate access (a role) to view financial reports?
Yes — on both platforms, access to financial data is a distinct permission, not automatically included in base roles like Developer/App Manager.
This article is independent and not affiliated with Apple Inc. or Google LLC. For official information, see developer.apple.com/app-store-connect and support.google.com/googleplay/android-developer.
Related: Setting Up a Service Account for Google Play Developer API · Apple Developer API & App Store Connect API: Getting Started · How to Publish an App on Google Play: Step-by-Step