Google Play App Intelligence - Ratings, Updates & Prices

SOURCE COVERAGE & PRACTICAL LIMITS

Full product guide

Documentation captured from build 1.0.4. Example outputs retain their original sample context; they are not live results.

App listings, observed over time

Build a competitor-app or product watchlist from public Google Play detail pages. Each saved row records one app in a requested country and language, with available listing metadata and optional saved comparisons.

Open this Actor in Console · First run · Results · Cost · Full guide

Try this Actor

1. Choose a small scope. Use the US app watchlist below for Duolingo, Spotify and Todoist, with US country context, English listing text and at most three saved observations. The guide also includes a single-app UK example.
2. Run and review. Open the dataset and inspect country/language context and fieldWarnings. The run's key-value-store SUMMARY explains failed sources, partial coverage and saved baselines.
3. Use the results. Export CSV for the overview or JSON for offers, warnings and comparisons. Keep the source URL with each app observation.

Read this before using the data: An install band is not an exact download count, and rating counts are not written-review counts. Differences between saved listings do not prove a release or new user activity. The Actor does not search apps or scrape reviews.

US App Watchlist - Duolingo, Spotify & Todoist — copy this input into the JSON editor in Console.

{
  "appIds": [
    "com.duolingo",
    "com.spotify.music",
    "com.todoist"
  ],
  "country": "US",
  "language": "en",
  "maxResults": 3
}

Result preview

The dataset view highlights these columns:

• App ID · appId
• App title · title
• Country context · country
• Language · language
• Rating · rating
• Ratings count · ratingCount

Use the original source links and the field definitions below when interpreting the results. CSV works well for flat columns; JSON preserves nested values.

Usage and pricing

Base result rate on the FREE tier: $2.5 per 1,000 app observations. The Pricing tab shows your plan's result rate and any Actor Start charge. Set a small result limit for the first run; the requested limit is not a guarantee of that many results.

Full guide

Monitor a supplied watchlist of Android apps from their public Google Play detail pages. Each saved row contains the app identity, requested country and language, rating and rating count, published price and currency, and available developer/listing fields. English listings also expose the published install band, update date, release notes, and developer-declared data safety summary.

Useful for competitor watchlists, release monitoring, changes to published monetization labels, and rating trends between saved observations. No Google account, owner credentials, API key, browser or proxy is required. This Actor does not fetch reviews, search results, charts, or the separate data safety endpoint.

Quick start

Run with {} for one current Duolingo observation. Or supply appIds, appUrls, or both. The fallback is used only when both source lists are empty. There is no catalog discovery: use known package IDs or Google Play detail URLs.

US App Watchlist - Duolingo, Spotify & Todoist

Inspect three public app listings for ratings, prices, install bands and published updates.

Use the copyable first-run input above.

Todoist UK - Country-Specific App Snapshot

Read one exact app URL with its UK country context and English public metadata.

{
  "appUrls": [
    "https://play.google.com/store/apps/details?id=com.todoist&hl=en&gl=GB"
  ],
  "maxResults": 1
}

Todoist - Ratings & Published Update History

Compare Todoist with its last saved US observation. First run establishes history; unchanged observations remain visible.

{
  "appIds": [
    "com.todoist"
  ],
  "country": "US",
  "language": "en",
  "comparePrevious": true,
  "snapshotName": "example-todoist-us",
  "maxResults": 5
}

Inputs

Output and interpretation

• Identity: appId, title, country, language, sourceUrl, finalUrl, observedAt.
• Published structured fields: rating, ratingCount, price, currency, offers, category, contentRating, operatingSystem, iconUrl, description, developerName, developerWebsite. The developer website is the publisher-linked website or support URL, not a verified company homepage.
• English visible-label fields: installBand, updatedOnText, updatedDate, releaseNotes, developerPrivacyPolicyUrl, declaredDataSafetySummary, containsAdsLabel, inAppPurchasesLabel. Boolean labels record label presence; absent labels do not prove a business model.
• Comparison: comparisonStatus is not_requested, baseline, unchanged or changed; changedFields, changeTypes, and previous explain the last saved comparison. Text hashes cover description, release notes and declarations; previous snapshots retain their hashes, not the previous long text.
• Diagnostics: fieldWarnings explains unsupported enrichment or truncation. Missing source fields are null. Long description/release/declaration text is bounded to 30,000/20,000/10,000 characters respectively; changes outside those bounds are not observed.

Prices are exact decimal strings in the source currency; zero is a published free price. A price direction is reported only when both amounts have the same known currency. Multiple distinct offers remain in offers and leave the single price/currency fields null. Offer availability is the publisher's structured offer label, not a verified device-installation or regional purchase check.

An install band such as 10M+ remains a band, not an exact download count. ratingCount counts ratings, not written reviews. updatedDate is a published calendar date in YYYY-MM-DD form; it is not an invented release timestamp. The Actor does not promise version numbers, exact installs, ranking, download eligibility, review text, or a security grade.

The data safety summary is the developer's public declaration. It is not independently verified. Only the existing app detail page is read; no data safety expansion endpoint or support page is fetched. Public support emails, addresses and phone numbers are not extracted into dedicated fields.

Google can vary published ratings and counts by country, serving cache, or update timing. Change flags describe differences between saved public observations; they do not prove new user activity or a release event.

Saved history and repeat runs

With comparison enabled, history lives in the named key-value store google-play-apps-{snapshotName}, scoped by package ID, requested country, and language. Only a confirmed saved observation advances its baseline. Failed or unaffordable output does not replace history. Unchanged rows skipped with onlyChanges retain their prior saved baseline. No missing/deleted app inference is made.

Use the same namespace for sequential scheduled runs and different namespaces for independent workflows. A pre-write reread detects known overlap, but it is not an atomic lock; avoid concurrent runs sharing a snapshot name. History storage remains until you delete the named store. The first comparison run emits baseline rows. A successful changes-only repeat may emit zero rows and zero result charges.

Coverage, access and billing

The Actor makes bounded GET requests to public app detail pages and obeys robots.txt. It validates app identity before emitting a row and refuses private network destinations and unsafe redirects. Google Play's public HTML is not a supported data API and can change; robots rules, rate limits, missing apps, regional differences, or consent pages may prevent collection. Such failures appear in the SUMMARY key-value-store record, not in paid error rows. If every source fails, the run fails. A mixed run preserves successful rows and reports partial coverage.

SUMMARY reports confirmed rowsSaved, rowsObserved, unchangedSkipped, failedSources, per-source coverage and baseline writes, and whether a result, spending, or time limit stopped the run. Selected result caps are distinguished from operational failures. Country is requested context, not a claim that Google returned personalized account/device data.

Proposed Store pricing is $0.0025 per saved app observation, plus a $0.00005 run start; the current Store pricing panel is authoritative. Unchanged observations are paid rows unless onlyChanges skips them. Failed fetches, invalid source data and skipped unchanged records are not billable result rows. Account storage or platform costs can depend on your Apify plan.

Local development

Node.js 20.18.1 or newer. Run npm ci, npm test, then npm start with local Apify INPUT storage. The lock pins Apify SDK 3.7.2 and a patched basic-ftp override. No API token is required for local public-source collection.

Help with your run

Open the Issues tab on this Actor with the run URL, the input field that caused trouble and what you expected to receive. Remove API keys and private information before posting.

Explore more Mayd-It Actors

Understand your run

Open Run report in the run’s Output tab for saved-record counts, reported source issues and limits, and suggested next steps. Use CSV export to take the saved results into a spreadsheet. The existing JSON results and detailed machine-readable summary remain available.

The report reflects this run’s recorded coverage. A successful run or a saved result does not establish that every possible source record was collected.