Google Play App Details and ASO Data Extractor

App metadata, installs, ratings and developers from Google Play Fields are sourced directly from accessible public pages or feeds.

Business use and first result

For: App store optimization and product research.

Why run it: Collect public Google Play app details to compare mobile app positioning and metadata.

What to inspect: Available app metadata, developer, ratings and install-related indicators.

First run: use the documented sample input below, inspect the Dataset rows and source links, then reuse the saved output for a later comparison only where snapshots are supported. Confirm the input scope and current Pay Per Event pricing before scheduling ongoing use.

Scope and limitations: Public store fields vary by app, country and time; no private app analytics.

Why use this Actor

Market demand for structured public Google Play App Details & ASO Data Extractor results

Key features

• Buyer-native inputs aligned to google play app scraper.
• Predictable structured output in the default Apify Dataset.
• Pay Per Event pricing tied to measurable result rows or reports.
• Optional MCP connector delivery for downstream automation and AI agents.

Quick start

Start with this working example and replace the target values with your own:

{
  "ids": [
    "com.spotify.music"
  ]
}

The Actor writes structured results to the default Apify Dataset and can be used from the Store, API, schedules, Tasks, automations and MCP-compatible AI workflows.

Input

• ids — Public source IDs or handles: Public Google Play package IDs, e.g. com.spotify.music
• language — Language: Optional input language controlling a public source request. Do not include private credentials.
• country — Country: Optional input country controlling a public source request. Do not include private credentials.

All integration and advanced analysis fields are optional. The default example is intentionally runnable without configuring MCP or a previous-run baseline.

Output

The Dataset exposes predictable machine-readable output. Representative fields include results, summary.

Pricing

This Actor uses Pay Per Event. The current factory base price is $0.001200 per result event. The Apify Store remains the source of truth for the price and plan/tier details shown to the buyer.

Use cases

• Run the buyer-ready workflows exposed as Apify Tasks without preparing a custom integration first.
• Use the Actor from API or schedules for recurring collection, comparison or monitoring.
• Feed the structured Dataset output into spreadsheets, databases, automations or AI agents.
• Compare repeat runs when the product supports snapshots or previous-run inputs.

Automation and AI

Use the same Actor through Apify API, schedules, public Tasks and the Apify MCP server. Outputs are structured for downstream workflows and AI agents rather than requiring manual copy/paste.

Limitations

• Public websites and upstream APIs can change markup, access rules, rate limits or field availability without notice.
• Fields that are not publicly available are returned as unavailable or omitted rather than fabricated.
• Analytical outputs depend on the quality and coverage of the supplied or collected source data.
• Treat marketplace, reputation, workforce, safety or commercial signals as decision support and validate material decisions against the underlying source evidence.

Detailed documentation

Why use this Actor

App metadata, installs, ratings and developers from Google Play. Manually copying records from public websites is slow and error-prone, especially when the same public profiles, packages or channels must be inspected repeatedly. This Actor accepts identifiers that buyers already have, makes direct source requests, and normalizes the observed fields into Apify Dataset rows with source links and a UTC timestamp.

Use it to build structured research tables, operational dashboards, change-monitoring pipelines or AI agent workflows. It does not produce invented rows and does not claim access to private records.

Key features

• Source-specific extraction with explicit, traceable URLs for the source records.
• Buyer-native inputs: a list of public IDs or handles; no pre-existing Apify Dataset required.
• Typed fields for record identity and selected observed metadata; a dataset view is included.
• Empty or inaccessible results raise a clear error rather than reporting imaginary success.
• Optional MCP connector delivery for accounts that provide and authorize an appropriate compatible connector.
• Bounded input and per-source fetch limits to control cost and avoid accidental large runs.

Input

Pass one to five entries through the ids array. For Google Play, use package names such as com.spotify.music. For Telegram, use public channel usernames such as durov without @. For YouTube, use a channel ID beginning with UC. Incorrect, deleted, private or inaccessible identifiers cannot be extracted. Other optional fields shown in the input form, when present, configure language, country or maximum returned rows.

Output

The default Dataset contains records with identifiers and a scrapedAt UTC timestamp. Field availability depends on what the source actually exposes. The run summary is saved under the SCRAPE_SUMMARY key-value record. Use Dataset export to retrieve JSON, CSV or Excel formats, or consume records through Apify APIs.

Example

Input JSON:

{"ids": ["com.spotify.music"]}

The successful output contains one or more normalized, verifiable source rows. Fields like author names, subscriber counts, app installs or videos are only included where applicable and observed.

Use cases

Use this Actor in recurring product research, competitive monitoring, app-store analytics, creator research and automated decision pipelines. Analysts can compare snapshots externally to detect changes; AI agents can consume the structured schema instead of parsing full pages. Keep in mind that this Actor provides the collected facts, not inferred or certain decisions.

Pricing

The factory intends pay-per-result pricing of USD 0.0012 for each primary delivered record, subject to the pricing displayed in the Apify Marketplace if/when this product is published. Network/proxy/resource costs and account plan conditions may also apply. Check the actual Apify pricing before running.

Limitations

Only publicly accessible content is queried. Website interfaces and undocumented feeds can change, leading to temporary errors. Some sites rate-limit bulk extraction. No restricted, private or authentication-protected content is bypassed. App review data can differ by country or language. Channel RSS covers only recent published videos, not subscriber counts or private analytics. Telegram public previews provide only currently visible messages and may not contain a channel's full history.

Trust and operation

Generated records are source observations rather than fabricated demonstrations. Inputs are processed within Apify execution. Avoid feeding private identifiers. If a source stops publishing a public endpoint, this Actor should report failure; consumers should not assume an empty response means zero underlying activity.