# Google Play Reviews Scraper + Pain Point Analysis (`pappy-dev/google-play-reviews`) Actor

Scrape Google Play Store reviews for any Android app (no login, no API key) and get pain-point / feature-request analysis on top: verbatim complaints ranked by how much more often a term shows up in negative reviews, not a keyword bag.

- **URL**: https://apify.com/pappy-dev/google-play-reviews.md
- **Developed by:** [Backyard Tools](https://apify.com/pappy-dev) (community)
- **Categories:** Developer tools, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Google Play Reviews Scraper + Pain Point Analysis

Scrape Google Play Store reviews for any Android app — no login, no API key — and get
pain-point / feature-request analysis on top: verbatim complaints ranked by how much more
often a term shows up in negative reviews, not a keyword bag.

### Tested (2026-09-02)

5/5 well-known apps returned real reviews on the first request:

| App | Package | Reviews returned |
|---|---|---|
| Spotify | com.spotify.music | 20/20 requested |
| WhatsApp | com.whatsapp | 20/20 requested |
| Instagram | com.instagram.android | 20/20 requested |
| Duolingo | com.duolingo | 20/20 requested |
| Discord | com.discord | 20/20 requested |

Single-request latency in that test: ~0.2s for 30 reviews from one app.

### How it works

Reads the same internal endpoint the Google Play Store *website* calls to render its own
review list. No login, no cookie, no JavaScript execution — a plain HTTP POST. This is not
an official Google API (Google does not publish one for reading another developer's
reviews), so the endpoint and response shape can change without notice; this actor will be
kept in sync if that happens.

### Input

```json
{
  "targets": ["com.spotify.music", "com.duolingo:en:gb"],
  "maxItems": 500,
  "analyses": ["overview", "top-complaints"]
}
```

`targets` accepts a bare package name (defaults to English / US) or
`"package:language:country"` to pull a specific locale.

### Output

One dataset item per review:

| Field | |
|---|---|
| `review_id` | Google's internal review id |
| `author` | reviewer's public display name (not a real name — this is the handle shown on Google Play itself) |
| `rating` | 1–5 stars |
| `text` | review body |
| `date` | ISO 8601 timestamp |
| `group` | app version the review was left on (used by the version-regression analysis) |
| `reply` / `replied_at` | the developer's public reply, if any |
| `thumbs_up` | how many users marked the review helpful |

No email, phone number, or physical address is ever present in this data — Google Play
reviews simply don't carry those fields.

### Analyses (billed once per run, not per review)

| Analysis | What you get |
|---|---|
| `overview` | count, average rating, negative share (with a lower-confidence bound so 3 reviews don't look like a trend) |
| `top-complaints` | actual excerpts from low-rating reviews, ranked by complaint-language density |
| `top-requests` | actual excerpts asking for a feature |
| `group-regressions` | which app version's ratings dropped relative to the rest |
| `trend` | monthly volume and negative share |

### Use Cases

- **App review monitoring** — track new reviews and sentiment shifts for your own app
- **Competitor app research** — `top-complaints` / `top-requests` surface what a rival app's users complain about or ask for most, in their own words
- **Release regression detection** — `group-regressions` flags which app version's ratings dropped relative to the rest
- **Feature prioritization** — rank real feature requests by how often they appear across all reviews

### Pricing

Pay per event: **$0.20 per 1,000 reviews** collected, plus **$0.05 per analysis** you select
(deselect analyses you don't need — nothing is charged for an analysis you didn't ask for).

# Actor input Schema

## `targets` (type: `array`):

パッケージ名。または "パッケージ名:言語:国"（例: "com.spotify.music" または "com.spotify.music:en:us"）。省略時は en/us

## `maxItems` (type: `integer`):

1 run で取得する最大件数

## `analyses` (type: `array`):

実行する分析（1 種につき 1 イベント課金）

## Actor input object example

```json
{
  "targets": [
    "com.spotify.music:en:us"
  ],
  "maxItems": 500,
  "analyses": [
    "overview",
    "top-complaints",
    "top-requests",
    "group-regressions",
    "trend"
  ]
}
```

# Actor output Schema

## `items` (type: `string`):

取得した各件（type=item）と、選択した分析の結果（type=analysis）

## `overview` (type: `string`):

件数・平均評点・期間・ネガティブ比率（下側信頼限界つき）

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "targets": [
        "com.spotify.music:en:us"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("pappy-dev/google-play-reviews").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "targets": ["com.spotify.music:en:us"] }

# Run the Actor and wait for it to finish
run = client.actor("pappy-dev/google-play-reviews").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "targets": [
    "com.spotify.music:en:us"
  ]
}' |
apify call pappy-dev/google-play-reviews --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pappy-dev/google-play-reviews"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/MHaVa0mQuHGQmQhIZ/builds/IfDc036WjwR68QEJY/openapi.json