Give it the listings you care about - your app, a competitor's, a film or a book - choose how often it should look, and set the rating you consider bad. It re-scans Google Play on that schedule, flags everything at or below your threshold, and emails you the report. Ten columns per review, the same ones the scraper returns.
A monitor is a scraper with a calendar and an opinion about what matters. You supply both.
com.spotify.music - or full Play Store links, one per line. Movies and books are accepted too. Or upload a CSV, XLSX, TXT or Parquet file.If a scan comes back with nothing, the monitor is not lost - it is saved and re-runs on its schedule.
Five frequencies, from daily to once a quarter. The week after a release is when the daily scan earns its keep - that is when the crash reports arrive dressed as one-star reviews. A stable app that ships twice a year does not need the same attention, and paying for daily checks on a quiet listing is waste. Weekly is the default.
The negative threshold is a number you pick from 1 to 5, not a fixed rule - reviews rated at or below it are flagged. Set it to 2 if you only want the genuinely angry ones; leave it at 3, the default, and the lukewarm reviews come too, which on an app store is usually where the specific, fixable complaint is written down.
app_version sits in every row next to the rating, which is what makes an app monitor different from a shop monitor: you can see whether the complaints are landing on the build you shipped on Tuesday or on one people have not updated from. Paired with reply, it also tells you which of them your team has already answered.
These are the columns the monitor declares, in its own order - and they are the Google Play Reviews Scraper's columns, not merely similar ones. The monitor reuses that column constant and reads the same results endpoint, so a file from either arrives in the same shape.
com.spotify.music. Group by this column when a monitor covers more than one listing.This page describes what each column is for, not what it will contain. The list above is the service's own, and it is identical to the scraper's because the monitor literally reuses that column constant and fetches from the same results endpoint - so the shape of the file is not in question. What is absent is any measurement: we hold no run export for this monitor, so there are no fill rates here, no ranges and no distribution. The scraper page does carry measured figures, and they were measured on its exports; they are not restated here because a number borrowed from another service's runs is a guess wearing a decimal point. Two things are worth knowing before you set one up. The email address is required - unlike some of the other monitors on this platform, this form will not start without one. And the monitor makes two choices for you that the scraper leaves open: it always sorts by relevance and always asks for English, and it has no limit field at all. If you need a different sort, a different language or a capped run, the scraper is the tool, not the monitor.
All of them start from an app ID you can read out of the Play Store URL.
Set the frequency to daily for the fortnight around a launch. Reviews arriving at one and two stars with a fresh app_version are the fastest, cheapest crash-report channel you have, and they arrive before most of your users bother to file anything.
Filter the scan to rows flagged negative where reply is empty. That is your queue: the reviews a customer wrote, nobody replied to, and everyone shopping your listing can read.
Nothing about a monitor requires the listing to be yours. Point one at a competitor at a weekly cadence and you get their complaints as they arrive - which is the closest thing to a free user-research panel for a product you do not own.
No subscription, no minimum, no per-seat licence. Your first 500 rows are on us - after that it is pay-as-you-go.
For every new account, one time. No credit card. All scrapers unlocked. Enough to set a monitor on one listing, watch the first scan land and decide whether the cadence you picked is the right one before you spend anything.
Roughly $2 per 1,000 reviews, the same flat rate as every other scraper on the platform. A monitor bills for what each scan returns, so the frequency you choose is the cost lever - a quiet listing checked weekly costs very little, and a daily scan on a busy one is the expensive end.
Volume pricing, SLAs, dedicated workers and tailored onboarding for teams watching a portfolio of apps rather than one. Tell us your numbers and we will quote.
LIVESCRAPER10 at checkout.A monitor answers what is new. These answer what is already there.
The whole back catalogue rather than what arrived this week, and with the controls the monitor does without - a sort order, a per-query limit and a language select. Run it once for history, then set a monitor for everything after that.
The other half of the same app. A bug that shows up on one platform and not the other is a different investigation from one that shows up on both, and you cannot tell which you have from a single store.
The same idea pointed at the company rather than the app - billing, support and refunds. People who cannot get a refund rarely say so in a store review; they say it on Trustpilot.
Short answer: yes, when you only collect what is publicly visible on a store listing - and that is all this service reads.
A listing's review section is public. Anyone can open it without an account and read it, and collecting publicly visible information for product and competitive research is long-settled practice. As long as the data is publicly available and the process does not disrupt the service, there are no federal laws against it. Watching it on a schedule does not change that - it is the same page, read again.
Reviews are written by people, though, and this export carries a display name and an avatar link alongside the text. Publicly visible is not the same as free of obligation: if you store it you are handling personal data, and the GDPR and similar regimes apply regardless of where you got it. Reading complaints in aggregate to fix an app is an easy case, and replying to a reviewer in the store is normal practice; building a durable file on individual reviewers is neither, and this service is not intended for it.
Google's terms restrict automated access, so this remains a question of terms. We touch nothing behind a login, read only what an ordinary visitor sees, run no third-party trackers on the data layer, and your exports self-delete after 30 days.
The questions we hear most. Something else? Talk to us - humans write the answers, not bots.
Paste one app ID, pick a cadence, and let the bad reviews come to you instead of finding them a week late. Your first 500 rows are free.
App store reviews are a support queue that nobody assigned to anyone. They arrive continuously, they are public, and the ones that matter most - a crash on a specific build, a billing complaint, a feature that stopped working - are indistinguishable from the rest until somebody reads them. This service reads them for you. Give it app IDs or Play Store links, one per line, choose a scan frequency, set the star rating you consider negative, and every scan returns the new reviews as rows with the bad ones flagged.
Three settings shape a monitor. The frequency has five options, from once a day to once every three months, with once a week as the default - the week around a release is when daily earns its keep, and a stable listing rarely needs it. The negative threshold is a number from 1 to 5, and anything rated at or below it is flagged; 3 is the default, which catches the lukewarm reviews where the specific, fixable complaints usually sit. The third is an email address, and on this form it is required - the monitor will not start without one, unlike some of the other monitors here.
What comes back is ten columns, one row per review: app_id, author, author_image, rating, date, review, likes, app_version, reply and review_id. That is not merely the same shape as the Google Play Reviews Scraper - it is the same column set, reused, read from the same results endpoint. Two of those columns are why an app monitor is worth more than a generic review monitor: app_version says which build a complaint landed on, and reply says whether anyone on your side has answered it yet. Filtering to flagged rows with an empty reply is, in practice, the queue.
The honest limits are worth stating. We hold no run export for this monitor, so this page describes what each column is for and claims nothing about how full any of them will be; the scraper page's measured figures came from its own runs and are deliberately not repeated here. The monitor also makes two choices the scraper leaves to you - it always sorts by relevance, always requests English, and has no limit field - so if you need a different sort, another language or a capped run, use the scraper instead. And if a scan returns nothing, the monitor is saved and simply runs again on schedule. Set one up on the free tier, watch the first scan land, and adjust the cadence from what you see. Your first 500 rows cost nothing and need no credit card. See pricing for current rates.