Data methodology
How Peekly estimates app revenue and downloads
Peekly separates public store facts from modeled estimates. This page explains the data sources, calculation principles, update cycle and limitations behind the figures shown across the product.
Methodology version 1.0 · Updated August 6, 2026
What Peekly tracks directly
Peekly collects facts that are publicly visible on the Apple App Store and Google Play. These include an app's name, publisher, category, price, in-app purchase signals, rating, review count, release date, latest update, screenshots, description and store URL.
Peekly also stores daily ranking snapshots by store, country, chart and category. This produces observable movements such as a new Top 100 entry, a rise or fall in rank, the number of countries where an app ranks and review velocity over time.
What is estimated
Apple and Google do not publish exact competitor revenue. Apple also does not publish exact iOS download counts. Monthly revenue and some download figures shown by Peekly are therefore estimates, not statements from the app publisher or either store.
Peekly cross-references market-intelligence data with ranking trajectories, download signals, category and country, pricing, subscriptions, paywalls, ratings and daily historical snapshots. Signals are weighted by their stability and historical relationship with observed market performance.
How figures should be interpreted
Revenue figures represent estimated mobile store revenue for the displayed monthly period. They do not represent audited company revenue and can exclude advertising revenue, physical goods, services paid outside the stores and web checkout revenue.
Figures are rounded because their purpose is to compare scale, direction and opportunity. Low-volume apps can be displayed as a range, such as less than $5,000, instead of a false point estimate. When Peekly lacks a reliable revenue signal, the public page says that there is not enough data.
Freshness and corrections
Store facts and ranking snapshots refresh on a daily collection cycle. Each public app page exposes its latest known data-update date to search engines and assistants. Sitemap modification dates are generated from the real underlying refresh date, not from the time the sitemap is requested.
Apps can change price, country availability, monetization or publisher information between collection cycles. Publishers and users can report a factual error through the Peekly contact page. Corrections to source data are reflected after verification and the next refresh.
Use estimates for comparison, not accounting
Peekly is designed to identify momentum, compare apps and validate markets. Do not use an estimate as audited financial information or as the sole basis for an investment decision.
