Official routes for your own app
| Aspect | Official API and exports | Scraping public listings |
|---|---|---|
| Coverage | Your own apps | Public listings, including competitors' apps |
| Reliability | Stable formats | Breaks when pages change |
| Completeness | Includes fields such as app version | Varies |
| Replies | The API lets you reply | Not possible |
| Terms | Sanctioned routes | Check terms and legal requirements first |
- Reply to Reviews API: retrieve and reply to reviews from your own systems, within quotas that can be raised by request.
- Cloud Storage reports: CSV files Google says are generated daily and gathered into monthly files.
- Play Console: read, filter and search reviews.
Google's Play Console help on reviews, exports and the API.
View and analyse your app's ratings and reviews (Play Console Help)Scraping public listings
Some teams scrape public Play Store pages, usually to study competitors' apps, which official APIs do not cover. Before scraping, check the terms of service and any legal requirements that apply to you; review how you store and use the data; and expect scrapers to break when pages change.
Trade-offs
- Coverage: APIs and exports cover your own apps; scraping can reach public listings.
- Reliability: official formats are stable; scrapers break.
- Completeness: exports include fields such as app version; scraped data varies.
- Replies: only the API lets you reply.
- Terms: official routes are sanctioned; scraping requires care.
Handling the data
- Store each review by its ID.
- Update edited reviews rather than duplicating them.
- Keep app version, language, date and rating.
- Keep raw data unchanged and work on copies.
Free review snapshot
Want this done for your own reviews?
No commitment. We use your details only to send your snapshot and follow up. Privacy policy
An example
A team scraped its own app's reviews for a year and kept hitting broken pages and missing versions. Switching to the Cloud Storage exports for its own app gave complete monthly files with app versions, and it kept public-listing collection only for two competitor apps after a terms review.
Common mistakes
- Scraping your own app when exports exist.
- Ignoring terms of service.
- Duplicating edited reviews.
- Dropping version data.
Common questions
Is there an API for competitors' reviews?
Google's official review tools cover apps you manage.
How often are exports updated?
Google describes reports generated daily.
Can the API reply to reviews?
Yes, that is its main purpose alongside retrieval.
Do we need engineers?
For the API, yes; exports can be downloaded manually.
Checklist
- Official routes for your own app.
- Terms checked for any scraping.
- Reviews stored by ID.
- Edits and versions handled.
In short
Use Google's exports and Reply to Reviews API for your own app; treat scraping of public listings carefully and check the terms; store reviews by ID with versions and edits.
Choosing a route
For your own app, start with the Cloud Storage exports for history and the Reply to Reviews API for ongoing collection and replies. For competitor apps, decide first whether you need their reviews at all; if you do, get a terms and legal check, collect only public review text and keep it separate from your own data.
A simple pipeline
A scheduled job pulls new reviews, upserts them by review ID, records version and language, and passes new ones to classification. A second job prepares the monthly view. Keep it small and well logged; most problems come from silent failures that nobody notices for weeks.
Data quality checks
Each month, check that review counts match what Play Console shows for the same period, that versions are populated, and that edited reviews replaced earlier versions rather than duplicating them.
Doing this with Falcon
Falcon classifies every Google Play review of your app into feature areas and specific issues with the sentiment of each mention, on the same taxonomy as your store reviews but kept separate. Negative share by area and month shows what is new or growing, and every issue opens the reviews behind it.