App Store and Google Play Review Monitor
Pricing
from $0.09 / 1,000 review rows
App Store and Google Play Review Monitor
App Store and Google Play reviews for any app, by country store, newest first. Schedule it and get only the reviews posted since your last run, plus one rating trend row per app: rating, rating count, and the stars of the new reviews. No login, no key. Clay ready.
Pricing
from $0.09 / 1,000 review rows
Rating
0.0
(0)
Developer
Mamba Labs
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
13 hours ago
Last modified
Categories
Share
Get the reviews of any app on the Apple App Store and Google Play, by country store, newest first. Run it once for a pull of recent reviews, or schedule it with a state key and each run returns only the reviews posted since the last one. Every app also gets one trend row per country: its rating, rating count, the change since the last run, and the stars of the new reviews. Rows are flat, so they export to CSV or drop into a Clay table.
Features
- Both stores, one row layout. App Store and Google Play reviews come back in the same columns: stars, title, text, author, app version, date, helpful votes, and the developer reply where Google Play shows one.
- Country stores. Pick the countries you care about. App Store reviews are separate per country, so a
gbrun returns UK reviews. - Only new reviews. With a
state_key, each run remembers the reviews it returned for each app and country and skips them next time. Paging stops at the first review already returned, so a daily run reads one page. - Date window and star filter. Return only reviews since a date or a number of days, and only the star ratings you want, for example 1 and 2 stars for a complaints feed.
- Rating trend row. One
app_summaryrow per app and country with the app rating, rating count, rating change, new ratings since the last run, and the average and star split of the new reviews. - Developer domain. Every row carries the developer name and the website the developer lists in the store, with its domain, so you can join reviews to a company list.
How it reads the stores
No login, no API key, and no other developer's actor. App facts come from Apple's public iTunes lookup service and from the Google Play app page. Reviews come from Apple's public customer reviews feed (newest first, 50 per page, at most 500 per country store) and from the public reviews endpoint the Google Play app page itself loads (newest first). A host that refuses a request is retried through the Apify proxy.
Input
| Field | Type | Default | What it does |
|---|---|---|---|
apps | array | App Store URLs or ids (id618783545), Google Play URLs or package names (com.Slack), up to 100 | |
countries | array | us | Two letter store codes, up to 10 |
max_reviews_per_app | string | 100 | Reviews per app and country store per run, newest first. App Store at most 500, Google Play up to 2000 |
since | string | Only reviews on or after a date (2026-10-01) or within a number of days (30) | |
star_ratings | array | all | Only these star ratings, for example 1, 2 |
only_new | string | true | Skip reviews returned by an earlier run with the same state key |
state_key | string | Names the saved state; one key per schedule | |
reset_state | string | false | true to start over |
include_summary | string | true | The app trend row per app and country |
language | string | en | Google Play language |
max_charge_usd | string | Stop before a row would pass this amount | |
proxy_mode | string | auto | auto (direct, then the Apify proxy for a host that refuses), direct, or residential |
Every field accepts text, as Clay sends it: "true", "50", a comma separated list, or a JSON array.
Output
| Field | Rows | Example |
|---|---|---|
row_type | all | review, app_summary, app_error |
store, country, app_id, app_name | all | google_play, us, com.Slack, Slack |
developer_name, developer_website, developer_domain | all | SLACK TECHNOLOGIES L.L.C., http://slack.com, slack.com |
review_id, review_date, rating, review_title, review_text, author_name, app_version, thumbs_up | review | 5, Excellent App |
developer_reply, developer_reply_date | review, Google Play | the reply text and date |
review_url, app_url | review, summary | links |
app_rating, app_rating_count, installs | summary | 4.64, 224822, 50M+ |
previous_app_rating, rating_change, rating_count_change, previous_check_at | summary, from the second run | 4.63, 0.01, 412 |
new_reviews_found, new_reviews_avg_rating, new_reviews_by_star_json | summary | 30, 3.37, {"1":8,"2":2,"3":4,"4":3,"5":13} |
row_status, error_reason, billable_events_json | all | ok, null, {"review-row":1} |
The run summary (key-value store record RUN_SUMMARY) lists app stores read, reviews returned, first checks, unchanged apps, and errors.
Pricing
Pay per event. You pay only these events; the Apify platform and proxy costs of your run are paid by Mamba Labs.
| Event | Free plan | Bronze | Silver | Gold |
|---|---|---|---|---|
Review row (review-row), one review returned | $0.0001 | $0.000095 | $0.00009 | $0.000085 |
App trend row (app-summary), one per app and country store per run | $0.001 | $0.00095 | $0.0009 | $0.00085 |
Actor start (apify-actor-start), once per run | $0.0006563 | $0.0006563 | $0.0006563 | $0.0006563 |
Free rows: app_error rows for an app or input that could not be read. On the Apify free plan the actor stops at 1.50 USD of evaluation a month (about 15000 review rows); any paid Apify plan removes that cap. Set include_summary to false to pay for review rows only.
Example: a daily run over 5 competitor apps in the US store with 40 new reviews costs 40 review rows ($0.004) plus 5 app trend rows ($0.005), $0.0096563 with the actor start.
Usage examples
Apify Console or API
Clay
Send an app URL or package name per row in apps, with max_reviews_per_app and a since window, and read rating, review_text, and review_date. Use the app_summary row for the app rating and developer_domain to join to your company list.
Scheduled monitoring
Save the input as an Apify task with a state_key and schedule it. Each run returns only reviews posted since the run before, and one trend row per app and country.
MCP
The MCP server @mambalabsdev/mcp-app-store-google-play-review-monitor exposes this actor as a tool for Claude and other MCP clients.
Error handling
| Situation | What you get |
|---|---|
| Input with no app, or nothing recognizable | One free row, row_status error, error_reason starting with input_invalid:, and the run ends successfully. Nothing is charged by the actor |
| One entry is not an app next to valid ones | One free app_error row for that entry; the rest run |
| The app is not in that country store | One free app_error row with not_found |
| A store refuses every route | One free app_error row with row_status blocked |
| A later review page fails | The reviews read so far are returned and the trend row says partial |
| The state store cannot be opened | Every app reads as a first check, and the run summary says so |
| Max charge reached | The run stops before the next billable row; that app's state is not saved, so its reviews come back next run |
Limitations
- The App Store feed serves the 500 newest reviews per country store. Older App Store reviews are not reachable through it.
- The App Store feed carries no developer replies; Google Play replies are returned.
- Google Play shows one review list per language, not per country, so its reviews are returned once per app, under the first country in
countries. - A review edited by its author can come back with a new date but keeps its id, so it is not returned twice.
- You are responsible for how you use the data and for the terms of the stores you read.
More from Mamba Labs
Built by Mamba Labs.
