The Google Play reviews scraper for product feedback
Pull customer reviews for any Google Play app.
Kavex's Google Play reviews scraper exports the customer reviews for any Android app into a spreadsheet. Play Store reviews are one of the most candid sources of product feedback there is, users say exactly what they love, what crashes and what they wish the app did, and the thumbs-up count tells you which complaints other users agree with. You give a list of app IDs or Play Store URLs, and Kavex returns every review with its star rating, full text, author, app version, thumbs-up count and date. It is built for product teams mining feedback, founders watching a competitor's reviews, and support teams turning recurring complaints into a backlog.
A RUN OF 1,000 REVIEWS ON THIS SOURCE, AT 1 PER REVIEW
Say what you want. Read the price first.
Everything else is a ceiling or a filter. The estimate moves with the numbers you type, so the run never surprises you at the end.
Provide Google Play app IDs (the package name, for example com.spotify.music) or full Play Store URLs, one per line. For each app Kavex reads its review pages and returns every review with the star rating, full review text, author name, the app version reviewed, the thumbs-up count and the date posted.
Paste your app IDs or Play Store URLs on the configure page, set how many reviews to pull per app, and run. Kavex paginates the reviews for you. Use the Google Play Search scraper first to find the apps worth pulling feedback on.
Charged per delivered row. If the source holds fewer than you asked for, the rest of the credits go back to your balance the second the run ends.
One thousand reviews, itemised.
One line, because this source has nothing bundled on top. You pay the rate times the rows the run actually delivered.
| Line | Rate | Units | Credits |
|---|---|---|---|
| Play Reviews | 1 / review | 1,000 reviews | 1,000 |
| 1,000 reviews | 1 / review | 1,000 credits | $1.00 |
$0.001 PER FINISHED REVIEW · ONLY DELIVERED ROWS ARE BILLED
What people point it at.
Four ways this source is used today. Every one of them is the same run, the same export and the same credit pool.
- Product feedback mining, surface recurring requests and bugs from real users
- Competitor analysis, read what an app's users complain about most
- Tracking sentiment after a release by filtering reviews on app version
- Building a support backlog ranked by the thumbs-up count on each complaint
The rest of the reviews & reputation stack.
Same credit pool, same export. Chain the output of one run into the next without paying for the list twice.
Asked before the first run.
Short answers, no accordion to click through. If something is still missing, the help pages go deeper.
What is an app ID and where do I find it?
It is the package name in a Play Store URL, the value after id= (for example com.spotify.music). You can paste the whole URL instead and Kavex extracts the ID for you.
How many reviews does it return per app?
You set a per-app limit on the configure page; Kavex returns the most recent reviews up to that limit.
Does it tell me which app version was reviewed?
Yes, each review carries the app version it was written against, so you can isolate feedback before or after a specific release.
What does the thumbs-up count tell me?
It is how many other users marked a review as helpful, a fast way to find the complaints and requests the wider user base agrees with.