Google Play Reviews Scraper & Daily Monitor
Pricing
from $0.50 / 1,000 reviews
Google Play Reviews Scraper & Daily Monitor
Monitor public Google Play reviews daily with onlyNew and Apify Schedules. Export new and detected text/rating edits by app and locale. $0.50 per 1,000 saved review rows, plus $0.003 per optional app report. No Google login or API key required.
Pricing
from $0.50 / 1,000 reviews
Rating
0.0
(0)
Developer
Erzia
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
13 days ago
Last modified
Categories
Features
Share
Daily monitoring: new and edited Google Play reviews
Use onlyNew: true to monitor reviews since your previous run. Create an Actor task and schedule it daily in Apify Schedules, for example cron 0 9 * * * at 09:00 UTC. Keep stateStoreName, app, country and language unchanged between runs. The Actor emits new reviews and detected text/rating edits; unchanged reviews produce no review rows and no review charges. Edited reviews are also billed once per emitted row. Optional app reports have their own charge.
Quick start: daily Google Play review monitoring
- Enter one package ID or Play listing URL, then choose country and language.
- Enable onlyNew, choose a persistent stateStoreName and set a review cap sufficient for your volume.
- Run a small baseline and inspect review, app and error rows. The baseline is billable.
- After the first run finishes, repeat the same input. Unchanged reviews produce no review rows; reports can still be billed.
- Save a task, add it to Apify Schedules with UTC cron 0 9 * * *, enable it and verify the next run. Keep monitor runs sequential.
{"apps": ["com.whatsapp"],"country": "us","language": "en","maxReviewsPerApp": 200,"sort": "newest","onlyNew": true,"stateStoreName": "gplay-daily-example-state","includeAppInfo": true}
This is a recent-feed monitor, not a guarantee of complete history. Saving the task does not schedule it. New and detected text/rating-edited review rows cost $0.0005 each; a completed optional app report costs $0.003 even with no changes.
For an app with about 50 new reviews/day, a 30-day month gives 1,500 × $0.0005 = $0.75, plus 30 daily app reports × $0.003 = $0.09, for $0.84 total in Actor event charges. This example assumes no additional edited review rows and excludes any separately applicable account/storage/integration fees. With includeAppInfo: false, the reports are omitted and there is no app-info charge.
The $0.84 monthly example assumes 1,500 emitted review rows and 30 completed reports. If a separate first baseline is outside that volume, add its saved rows at $0.0005 each and its report at $0.003. Detected text/rating edits are billable review rows too.
{"apps": ["com.whatsapp"],"country": "us","language": "en","onlyNew": true,"stateStoreName": "gplay-reviews-monitor-state","maxReviewsPerApp": 200,"includeAppInfo": true}
The first monitoring run emits up to maxReviewsPerApp latest matching reviews as changeType: "new", saves the baseline and marks the app report firstRun: true. Later reports have firstRun: false, newReviews and editedReviews. An unchanged run emits zero review rows, reports both counts as 0, and charges zero review events. A successful app report is still charged, including on an empty app. An empty successful first run also saves a baseline.
State lives in the named key-value store gplay-reviews-monitor-state by default, rather than the run's default store. Each key is derived from the full (appId, country, language) tuple; countries, languages and apps do not share review histories. State contains up to 5,000 recent review IDs, a SHA-256 hash of each review's text and rating, and the newest review date. Each emitted review is checkpointed before billing, so later page/report failures do not cause that row to be emitted and charged again on the next run. Changing a review's helpful votes, version or developer reply alone does not count as an edit. Keep monitor runs sequential; the store is not a lock for overlapping runs.
Monitoring always requests sort: newest, regardless of the supplied sort setting. After an unchanged known review followed by older reviews, it scans one additional page to detect edits to known reviews, then stops if the feed remains older. Unknown historical reviews behind this boundary are not imported from the guard page, so a repeat does not backfill beyond the first run's limit. A newer or undated item breaks the boundary and continues the scan. The saved-row cap and rating/date filters still apply. This monitors the recent feed: edits deeper than the scanned window, deleted reviews and history beyond the retained 5,000 IDs cannot be tracked reliably. Choose a limit and schedule frequent enough for your volume.
Use a new stateStoreName for an independent baseline or after changing filters. Deleting the store resets monitoring, so previously emitted reviews can become new again. onlyNew defaults to false; ordinary collection does not open or update monitor state.
Collect public Google Play reviews by app, country and language, and get an app report in the same run. Filter by rating and date, compare feedback across app versions, and export review text with developer replies. No Google account or API key. $0.50 per 1,000 saved reviews, plus optional app reports.
How it works without an API key
The Actor reads Google Play's public web pages through the open-source google-play-scraper library. No login, Google Play Console access or browser session is needed.
- Enter package IDs such as
com.whatsappor links such ashttps://play.google.com/store/apps/details?id=com.whatsapp&hl=en. - Choose a country, language, review order and limit, and optional rating or date filters.
- Click Start. Export the dataset to JSON, CSV or Excel, or retrieve it through the Apify API.
The Actor calls gplay.app({ appId, lang, country }) for app details and gplay.reviews(...) for reviews. Every app is looked up, including when reports are disabled, so unavailable IDs produce an error instead of a misleading empty report. Reviews are requested in chunks of 150 with paginate: true, following nextPaginationToken until the saved-review limit, the end of available results, a date cutoff in newest order, an error or the spending limit.
What you get
- Review text and context. Public user name, rating, text, helpfulness votes, reviewed version, date and developer reply.
- Country and language selection. All apps use the requested
countryandlanguage. Locale parameters in submitted URLs do not override these settings. - App reports. Developer, current version, store rating, ratings and review counts, installs, price and icon, plus statistics calculated from reviews saved in this run.
- Focused collection. Inclusive rating and date filters; duplicate app IDs and review IDs are skipped within each app.
- Pay per saved result. No start fee. Errors, duplicates and reviews excluded by filters are not charged. Runs stop when Apify reports the spending limit reached.
Who uses it
| Who | What for |
|---|---|
| Product managers | Find recurring requests and complaints in recent reviews. |
| Mobile developers and QA teams | Compare feedback by reviewed version and investigate reported regressions. |
| ASO and marketing teams | Compare public feedback and developer responses across competitors. |
| Analysts and researchers | Export review text for classification, sentiment analysis and reporting. |
What data you get
Reviews (one row per saved review, type: "review")
| Field | Meaning |
|---|---|
appId, country, language | Package ID and requested country and language |
reviewId | Google Play review ID as a string |
userName | Public display name |
rating | Integer star rating from 1 to 5 |
text | Full review text |
thumbsUp | Helpful votes returned by Google Play |
appVersion | App version attached to the review |
date | Review timestamp normalized to ISO UTC |
replyText, replyDate | Developer reply and its ISO UTC timestamp, when available |
url | Public review URL returned by the library, or a Play app URL with the review ID |
changeType | Monitoring only: new for a new ID or edited when a known review's text/rating hash changed |
Optional fields missing from the response are null. Entries without a valid rating or string review ID are skipped. Review text and replies are preserved as returned by the library.
Apps (one report per completed app, type: "app")
| Field | Meaning |
|---|---|
appId, country, language, url | App and requested locale identity, and public listing URL |
title, developer | App name and developer |
score, ratings, reviews | Store rating, rating count and written-review count returned by Google Play |
installs, minInstalls | Displayed install range and its numeric lower bound |
price, free | Numeric listed price for the requested country and whether the app is free |
genre, version | Category and current app version |
updated | App update timestamp normalized to ISO UTC |
icon | App icon URL |
reviewsCollected | Number of reviews actually saved after filters and deduplication |
avgRatingOfCollected | Mean rating of saved reviews, rounded to four decimal places; null when none match |
ratingDistribution | Counts of saved reviews for each star rating, with all keys 1 through 5 present |
shareWithDeveloperReply | Fraction of saved reviews with nonblank developer reply text, from 0 to 1, rounded to four decimals; null when none match |
topVersions | Up to ten reviewed versions as { "version": "2.0", "count": 12 }, ranked by review count, then version name |
error | null for a completed report |
firstRun | Monitoring only: whether this app and locale had no saved baseline |
newReviews, editedReviews | Monitoring only: counts of new and edited review rows saved in this run, including zero |
Report statistics describe only the saved, filtered sample. They are separate from Google's store rating figures. Reviews without a version still count in rating and reply statistics, but not in topVersions. A reply share of 0.25 means 25% of saved reviews have developer reply text.
Errors (type: "error", no charge)
Error rows contain appId (or null for an invalid input), country, language, the original input, url and an error message. Unknown apps and unavailable listings generate error rows even when includeAppInfo is off. A request failure after some reviews have been saved keeps those reviews, adds an error row, and omits the app report. Previously saved reviews remain billable. Invalid run settings fail validation before collection.
The dataset has two ready table views: Reviews and Apps, following the shared dataset convention. Views select columns; use type to distinguish review, app and error rows when exporting a mixed dataset. The Apps view includes error columns. Views do not filter row types.
Pricing
Pay per event, with no start fee:
| Event | Event name | Price |
|---|---|---|
| Saved review | review | $0.0005 ($0.50 per 1,000 reviews) |
| App report | app-info | $0.003 per app |
Worked examples, assuming the stated number of reviews is actually saved:
- One app, 200 reviews and one report: 200 × $0.0005 + $0.003 = $0.103.
- Ten apps, 200 reviews each and ten reports: 2,000 × $0.0005 + 10 × $0.003 = $1.03.
- Review-only collection of 1,000 reviews: 1,000 × $0.0005 = $0.50, with
includeAppInfo: false.
Filtered-out reviews, duplicates and failed lookups cost nothing. A completed app report is billable even if no reviews match your filters. Spending-limit termination can leave saved reviews without a final app report.
Input example
{"apps": ["https://play.google.com/store/apps/details?id=com.whatsapp&hl=en"],"country": "us","language": "en","maxReviewsPerApp": 200,"sort": "newest","includeAppInfo": true}
Input fields
| Field | Default | Meaning |
|---|---|---|
apps | Required | Non-empty string list of package IDs or Google Play app URLs |
country | "us" | Two-letter country code for all apps |
language | "en" | Language code passed as lang, for example en, de or pt-BR |
maxReviewsPerApp | 200 | Maximum saved reviews after filters, from 1 to 5,000 |
sort | "newest" | newest, rating or helpfulness, mapped to the library's corresponding sort constants |
minRating | Unset | Inclusive minimum star rating, from 1 to 5 |
maxRating | Unset | Inclusive maximum star rating, from 1 to 5 |
dateFrom | Unset | Inclusive absolute date or relative period |
onlyNew | false | Enable persistent monitoring. First run establishes a billable baseline; later runs emit new IDs and detected text/rating edits. |
stateStoreName | "gplay-reviews-monitor-state" | Named state store. Keep it stable between sequential runs; use a different name after changing filters. |
includeAppInfo | true | Save and charge for one app report per completed app |
Dates accept an absolute value such as 2026-01-31 or a period such as 7 days, 3 months, 1 year, 2 hours or 15 minutes, following the sibling Actors' conventions. Relative periods are resolved once at run start. Invalid dates or input settings fail validation. Reviews with unknown dates are excluded when a date filter is active.
The review limit applies after filters. Restrictive filters can require scanning many pages. In newest order, the Actor stops after processing a page containing a dated review older than dateFrom, even if that older review fails a rating filter. In rating and helpfulness order, older reviews are excluded without ending pagination because later pages may contain newer matches.
Output examples
These templates show output fields without inventing Google Play review data or app metrics. Angle-bracket strings stand for values returned at run time; rating, vote, price, count, average and share fields are numbers in actual output. free is a boolean. Missing optional values are null.
{"type": "review","appId": "com.whatsapp","country": "us","language": "en","reviewId": "<review ID>","userName": "<public display name>","rating": "<integer rating>","text": "<review text>","thumbsUp": "<helpful vote count>","appVersion": "<reviewed version>","date": "<ISO UTC timestamp>","replyText": "<developer reply>","replyDate": "<ISO UTC timestamp>","url": "<public review URL>"}
{"type": "app","appId": "com.whatsapp","country": "us","language": "en","title": "<app title>","developer": "<developer name>","score": "<store rating>","ratings": "<store rating count>","reviews": "<store written-review count>","installs": "<displayed install range>","minInstalls": "<numeric install lower bound>","price": "<numeric listed price>","free": "<boolean>","genre": "<category>","updated": "<ISO UTC timestamp>","version": "<current app version>","url": "<public listing URL>","icon": "<icon URL>","reviewsCollected": "<saved review count>","avgRatingOfCollected": "<mean of saved ratings>","ratingDistribution": {"1": "<count>", "2": "<count>", "3": "<count>", "4": "<count>", "5": "<count>"},"shareWithDeveloperReply": "<fraction from 0 to 1>","topVersions": [{ "version": "<reviewed version>", "count": "<review count>" }],"error": null}
Three independent illustrative selected-field examples: a new row, an edited row, and a separate unchanged run report. They are not one run and are not real Google Play reviews.
[{"type": "review","appId": "com.whatsapp","country": "us","language": "en","reviewId": "ILLUSTRATIVE_NEW_ID","rating": 2,"text": "Illustrative review text, not a real user review.","date": "2026-11-09T08:00:00.000Z","changeType": "new"},{"type": "review","appId": "com.whatsapp","country": "us","language": "en","reviewId": "ILLUSTRATIVE_EDITED_ID","rating": 3,"text": "Illustrative edited text, not a real user review.","date": "2026-11-08T08:00:00.000Z","changeType": "edited"},{"type": "app","appId": "com.whatsapp","country": "us","language": "en","firstRun": false,"newReviews": 0,"editedReviews": 0,"reviewsCollected": 0,"avgRatingOfCollected": null,"ratingDistribution": {"1": 0,"2": 0,"3": 0,"4": 0,"5": 0},"error": null}]
Integrations and automation
- Schedule daily runs with
onlyNew: trueto monitor new feedback and text/rating edits. Developer replies are included on emitted rows; reply-only changes are not monitored. - Export results or connect them to your reporting workflow through Apify integrations.
- Use the Apify API to supply inputs and retrieve dataset rows. Output links expose the
reviewsandappsdataset views.
FAQ
Do I need a Google account or API key? No. The Actor reads publicly available Google Play data without authentication.
Where does the data come from? Data comes from Google Play's public web pages through the open-source google-play-scraper library. This is not Google Play Console data or an official Google API contract. Google may change its pages and underlying requests, which can affect the library and this Actor.
Can I get every historical review? The Actor saves up to 5,000 matching reviews per app per run. It follows the pagination tokens Google Play exposes, but availability is not guaranteed. A saved-review limit is not a guarantee that the requested number exists or can be retrieved.
Why are there fewer reviews than requested? There may be fewer available reviews, filters may exclude some, review IDs may repeat, or Google may return an empty page or no next token. A date cutoff, spending limit or request error can also stop collection. Invalid or repeated pagination tokens produce an uncharged error row and omit the report.
Does the app URL choose the country or language?
The Actor extracts only the package ID. country and language control requests, defaulting to us and en. Google Play determines which review content is available for those settings; the Actor does not translate reviews or infer a reviewer's country.
Why does the collected average differ from the store rating?
The collected average uses only saved written reviews matching your filters. Google's score, ratings and reviews fields describe the broader listing data returned by the library. Sort order and filters also affect the sample.
What happens on request failures? Each library call is retried on errors up to three total attempts, with waits of 1 second and 2 seconds. The Actor also waits 800 milliseconds between review pages. Persistent failures produce error rows; no error event is charged.
What happens when I reach my spending limit?
The Actor checks eventChargeLimitReached after each saved review or app report is charged, then stops saving further rows or looking up later apps. An interrupted app may have saved review rows without an app report.
Is an empty report charged?
Yes, if app lookup and review collection complete successfully with includeAppInfo: true. It includes app metadata and zero collected reviews. Set includeAppInfo: false for review-only billing; app validation still runs without an app-info charge.
Something does not work? Open an issue on the Actor's Issues tab with the run link and the affected app, country and language.
Limits
- At most 5,000 saved reviews per app per run, with pages requested in chunks of 150.
- Only public Google Play app listings and reviews; no private Google Play Console data.
- Country availability, language selection, optional fields and pagination depend on Google's responses and the library.
- Reviews can change while pagination is in progress. Results are a snapshot of the available data during the run.
- Successful reports describe the saved sample. A partial request failure retains already saved reviews and omits the report.
Related competitor research tools
Keep a weekly visual archive of competitor pricing pages with a separate screenshot workflow. Website Screenshot & PDF Generator.
API access
Use the Actor API examples to pass explicit input and retrieve results. UI prefills are not API inputs.
Use with AI agents
Connect an MCP-compatible client to https://mcp.apify.com?tools=actors,erzia/googleplay-reviews-scraper. Inspect Actor details and pricing before running. Pass the full quick-start input explicitly. Read the dataset after the run; starting an Actor does not create a recurring schedule. Authentication and any task/schedule setup are separate. Guide: https://docs.apify.com/mcp