Live
Returned from the named external source during the current request or analysis run.
AppStoreStatistics separates public observations, cached source data, modeled estimates, authorized owner analytics, and beta provider signals. Every result should be interpreted using its source label, collection time, scope, and stated limitations.

Data classification
A label describes provenance and certainty. It does not describe whether a number is favorable or unfavorable.
Returned from the named external source during the current request or analysis run.
Collected from a public source and stored as a dated AppStoreStatistics snapshot.
A previously collected result reused when it remains valid or a live source is temporarily limited.
A modeled range derived from public signals; it is not an exact Apple-reported competitor metric.
Reserved for authorized owner analytics returned by a connected first-party account. It is never inferred.
Coverage depends on an evolving provider API or public source and may be incomplete.
Coverage by product area
The same number can mean different things depending on the storefront, collection window, source, and whether it was observed or modeled.
01
Public Apple Search and lookup responses
Method
Apps are identified by numeric Apple track ID. Search results remain storefront-specific, and lookup/search responses pass through the shared external-source gateway before reaching product workflows.
Limitation
Availability, ratings, localization, and returned search order can differ by country and collection time.
02
Stored public Apple chart-feed observations
Method
Chart order is stored as a dated snapshot. Rank movement compares the current stored position with the previous position available to the collection pipeline.
Limitation
A chart position is a visibility signal, not an exact download, install, revenue, sales, or proceeds figure.
03
Organic Apple Search results for a selected storefront
Method
Keyword rank is the target app's one-based position in the returned organic result list. Comparisons and gaps use the same result set to identify shared visibility, wins, missing terms, and rank differences.
Limitation
Paid Apple Search Ads are excluded. An app outside the scanned depth is reported as not found, not as permanently unranked.
04
Apple Search results, public rating counts, metadata terms, and stored ranking history
Method
Difficulty combines downloads-pressure proxies, ratings competition, ranking stability, and brand strength into an internal 0-100 score. Suggestions combine prefix expansion and recurring metadata terms, then deduplicate and score candidate phrases.
Limitation
Difficulty, relevance, competition, and opportunity are internal models rather than official Apple keyword-volume metrics.
05
Public storefront rating metadata and available public review feeds
Method
Rating totals and averages retain their storefront and collection context. Review summaries are calculated from the deduplicated sample actually loaded for the selected storefront.
Limitation
A review sample is not guaranteed to contain every review worldwide, and storefront totals can differ.
06
Stored app metadata and ranking observations in the AppStoreStatistics dataset
Method
Daily aggregation deduplicates apps by track ID and calculates documented counts, medians, shares, release activity, update activity, language coverage, and chart coverage under a versioned methodology.
Limitation
The figures describe the observed dataset and must not be presented as Apple's complete worldwide inventory or transaction totals.
07
Public rank history, category, country, pricing, ratings, reviews, monetization, lifecycle, and momentum signals
Method
The public statistics model combines available signals into ranges and attaches a confidence level, missing-signal list, source labels, and model version instead of presenting false precision.
Limitation
Competitor downloads and revenue remain estimates. Exact owner analytics are unavailable unless a supported first-party App Store Connect connection is active.
08
TikTok Commercial Content API, Meta Ad Library API, and clearly labeled public-source fallbacks
Method
Provider records are normalized into app, advertiser, account, creative, delivery, country, platform, reach, and targeting signals where the source returns them. Matching receives source and confidence context.
Limitation
Ads Intelligence is beta. Provider access, regional coverage, public-page rendering, missing media, and account matching can limit completeness.
These definitions prevent relative rankings, samples, and models from being cited as exact private performance data.
| Metric | Calculation | Correct interpretation |
|---|---|---|
| Keyword rank | One-based organic position of the target track ID in the returned storefront result list. | Not found means absent from the scanned depth, not permanently unranked. |
| Rank movement | Current stored position compared with the previous stored position for the same scope. | Movement describes relative visibility, not installs or revenue. |
| Keyword difficulty | 0-100 internal score from ratings pressure, ratings competition, result stability, and brand strength. | Model score, not official Apple search volume or difficulty. |
| Review average | Arithmetic mean of scores in the deduplicated public review sample actually loaded. | Sample statistic rather than a worldwide review total. |
| Statistics medians and shares | Calculated from the apps present in the dated, deduplicated AppStoreStatistics snapshot. | Observed dataset statistic rather than a complete Apple inventory claim. |
| Downloads and revenue | Modeled as ranges from available public rank, category, country, pricing, rating, lifecycle, and momentum signals. | Estimated and confidence-labeled unless an authorized owner source explicitly returns exact data. |
Source resilience
External providers can rate limit, time out, or return incomplete data. The platform handles those conditions without silently turning an old result into a live result.
The workflow requests the named public or authorized source.
Timeouts, request spacing, retries, and backoff limit provider pressure.
A valid stored response may be reused when live retrieval is temporarily limited.
Source, freshness, warning, fallback, and confidence context remain visible.
Estimated data
Competitor download and revenue models combine only the public signals available to the analysis. Wider ranges and lower confidence communicate missing history, ratings, reviews, monetization, or chart presence.
Exact data
The Exact label is used only when a supported first-party connection returns owner-authorized analytics. Current availability depends on the integration state; when no connection is active, the product reports that status and keeps public estimates separate.
Provider documentation explains field availability. AppStoreStatistics remains responsible for how collected values are normalized, labeled, and presented.
The platform combines public Apple metadata and chart/search observations with provider-specific TikTok and Meta advertising data. Every major product area identifies whether its result is live, observed, cached, estimated, exact, or beta.
Freshness depends on the source and workflow. Data pages display their observation or snapshot time, while interactive analyses prefer live data and label any cached fallback used during source limits.
No. Public competitor downloads and revenue are modeled ranges based on available public signals. Exact values require authorized first-party analytics and are never inferred from a competitor's public listing.
The shared gateway applies request spacing, retries, backoff, caching, and circuit-breaker behavior. If a valid cached result exists it can be shown with a Cached label; otherwise the interface reports that no source data is available yet.
No. Chart rank is an observed relative position. It can support a labeled model, but it is not a direct disclosure of downloads, installs, sales, revenue, or proceeds.
Use the source directly