Google Play Reviews Scraper & Change Monitor
Pricing
from $9.50 / 1,000 review scan batches
Google Play Reviews Scraper & Change Monitor
Export Google Play reviews with ratings, app versions, and developer replies. Track known apps for new or edited reviews and reply changes, with stable keys for your feedback database.
Pricing
from $9.50 / 1,000 review scan batches
Rating
0.0
(0)
Developer
Luka
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
Turn Google Play reviews into a feedback table you can refresh after each release.
- Export reviews with app versions and published developer replies.
- Compare repeat scans for NEW, UPDATED, and DEVELOPER_REPLY_CHANGED records.
- Keep stable app + review keys for your existing feedback database.
π Start in 60 seconds
Enter a package ID such as com.spotify.music, leave Export reviews selected, and run. The default scans up to 100 reviews. Download the Dataset as JSON, CSV, or Excel.
π― Choose the right workflow
| Workflow | Result | Repeat behavior |
|---|---|---|
| Export reviews | Matching review rows from the requested window | Fresh export each run |
| Track review changes | NEW, UPDATED and DEVELOPER_REPLY_CHANGED rows | Compares with the same watch-list name, apps and filters |
The first monitoring run can emit existing reviews as NEW or seed a baseline without change rows. Subsequent runs recheck the entire selected window, including overlapping reviews. An older review outside that window is not rechecked. Increase the review-slot limit to deepen overlap.
π¦ What you get
Each review row has a stable appId + reviewId, review link, rating, text, update date, helpful count, published app version and developer reply fields. Optional source fields remain null. Change rows include old/new values and a deterministic changeId. A reply belongs to its source review; Google does not provide a separate reply ID in the verified response.
requestCountry and requestLanguage describe your storefront request. They do not identify where a reviewer lives or their personal device. Review author names are the public display names only.
ποΈ Input guide
Use up to 10 known app IDs or Google Play app URLs. Choose newest/helpful, storefront country and language. Optional rating/device filters apply at the source; date, keyword and exact app-version filters apply within the scanned window. Review slots include rows rejected by output filters.
Maximums: 10,000 review slots and 100 pages per app, 20,000 slots total per run, and 20,000 saved matching reviews per watch list. Each page requests up to 100 reviews. A source may return fewer or stop early. Collection uses at most 210 seconds and leaves time for delivery.
Use the same watch-list name and filters to compare repeated runs. Run each watch list sequentially. If a delivery stops, recover its original run before starting another run against that watch list; this prevents recharging an uncertain delivery.
π° Pricing
$0.0095 per batch of up to 100 distinct source reviews scanned per app. Partial batches count as one. Both workflows use this scan-capacity price, with no start fee for nonempty scans. Included export/change rows are not charged separately. Each paid batch has a scan receipt row in the same Dataset; use recordType to distinguish reviews, changes, and scan receipts.
| Scan | Total charge |
|---|---|
| 1 app, 1β100 scanned reviews | $0.0095 |
| 5 apps, 1,000 reviews each | $0.4750 |
| 2 apps, 10,000 reviews each | $1.9000 |
An unchanged monitoring run or a filter yielding no rows still incurs the verified scan-capacity charge. Tiny scans can cost more than per-review competitors. This is not a universal cheapest claim. A positively verified empty collection costs $0.003; invalid input, no targets, or wholly unverified source attempts are free. Your spending limit must cover the full requested scan before collection begins.
β Coverage you can trust
COMPLETE means the source ended for your requested app, sort and filters. CAPPED means a configured review/page boundary was reached while continuation remained. PARTIAL means some targets failed; FAILED means no requested source was verified. Details appear in the run's OUTPUT record.
Reviews may be edited or reordered during pagination. Duplicate source IDs are suppressed. Absence from a newest/helpful/capped window never produces a REMOVED event. Only observed changes to trustworthy matching reviews update the watch list.
π API and automation
Send the example JSON through the Actor API and download the default Dataset. Upsert reviews by stableId; deduplicate change events by changeId. Keep one watch-list name per feedback collection, with sequential runs. No private Google developer credentials are needed.
β οΈ Not yet supported
Global app discovery; all worldwide reviews; private reviewer contacts; identity enrichment; sentiment or AI scores; deletion events; guaranteed rechecks of reviews outside your bounded scan; simultaneous runs on one watch list.
β FAQ and support
Why are version/reply fields empty? Google does not publish them on every review. Missing values remain null.
Why did no change rows appear? The observed matching reviews may be unchanged, or the first run may be seeding a baseline. Check OUTPUT coverage and scanned counts.
Where can I report a problem? Open the Actor's Issues tab with the run ID, app ID and requested locale. Do not share credentials or private user information.
