Skip to main content
Google Play analytics uses a synced dataset. Appeeky imports Play Console CSV reports and Android vitals first, then dashboard endpoints read from the imported data instead of calling Google live on every page load. This avoids slow live GCS reads on every dashboard request and gives the UI the same shape as App Store Connect analytics.

Data Sources

Google captures daily rows, but report exports can lag Play Console by several days. Monthly CSV files are updated as Google publishes new data.

Import Report Families

curl
Use this endpoint for initial backfill and manual sync testing. Scheduled jobs can run the same import flow in the background.

Import One Report

curl
This is useful when testing one CSV object or replaying a failed import.

Sync Android Vitals

curl
Vitals sync queries the Google Play Developer Reporting API and stores daily crash/ANR metrics for dashboard reads.

Read App Analytics

curl
Response shape:

Read Account Analytics

curl
Use this to show an account-level overview across imported Play apps.

Sources and Countries

curl
This endpoint returns traffic source, country, and UTM breakdowns where Google includes them in the store performance report.

Search Terms

curl
Search-term rows come from the stats/store_performance/ traffic source export. Google may suppress low-volume rows, and some monthly exports may not include the Search term column. Expected row fields:

Dashboard Mapping

Revenue and buyer metrics require financial report access. They are separate from the four stats folders above.

Why Not Query GCS Live?

Live GCS requests are acceptable for testing, but not for every dashboard view:
  • Report files can be large.
  • CSV parsing is slower than reading already-synced analytics data.
  • Google exports are monthly files with daily rows inside.
  • The same report may be needed by multiple users, charts, and filters.
  • Background imports let the UI stay fast and consistent.
The recommended model is: