Download bands, revenue estimates and search indexes are different evidence

Each metric answers a narrower question than its label suggests. Keep the source’s unit, model and coverage visible.

Public download bands

A band such as “100K+ downloads” is a threshold display, not a precise current total or a time series. It may cover the lifetime of one store listing and does not reveal active users, buyers, refunds, country mix or recent momentum. Preserve the band exactly as displayed and the observation date. Do not replace it with the lower bound as though it were an exact count.

Synthetic example

A public listing says “100K+”. Store it as the text band 100K+. Do not store 100,000 as measured downloads, and do not infer monthly installs.

Modeled download and revenue estimates

Commercial intelligence providers estimate competitor performance using proprietary models. The output is useful for comparing compatible scopes, but it remains an estimate. Record provider, app, store, countries, devices, start and end dates, currency, accounting basis and known limitations.

Revenue is especially easy to misread. Appfigures documents its estimate as net revenue from paid downloads, in-app purchases and subscriptions across supported countries. That is not necessarily gross customer spend, company revenue, cash collected or profit. Its estimates route is available only on select plans and may need additional licences.

Keyword popularity and absolute volume

An index describes relative popularity on a defined scale. An absolute volume is a count of searches in a stated window. They are not interchangeable. AppTweak’s current documentation, in a notice dated 11 August 2026, distinguishes its `volume` estimate from Apple raw `search_popularity`; both remain source-specific metrics rather than universal counts.

Google Trends indexes

Google Trends describes search interest, not App Store searches and not absolute query counts. The public Trends interface commonly rescales results from 0 to 100 for the selected comparison. Google’s limited alpha API uses consistently scaled interest, but Google still says those values do not reflect absolute numbers. Web interest can suggest language or timing for further research; it cannot fill an App Store keyword-volume field.

MetricSafe interpretationUnsafe conversion
Public download bandA displayed lifetime threshold observed on one listingExact or monthly downloads
Modeled downloadsProvider estimate for a defined scope and periodVerified users or buyers
Modeled revenueProvider-defined estimated revenue basisProfit or gross customer spend
Popularity indexRelative score on the provider’s stated scaleSearches or percentage
Google Trends interestRelative web-search interest in the selected contextApp Store keyword volume

A minimum import record

Keep the raw value and name, metric type, provider, source URL, observed time, region, platform, app ID or keyword, period, currency where relevant, scale for indexes, estimation flag and limitations. Missing values stay null. Never generate a competitor estimate with a general-purpose language model and label it measured.

Beta boundary: AppScout does not include licensed competitor estimates or keyword-volume feeds by default. Owner-supplied internal exports require valid entitlement and provenance. Public catalogue and search observations do not provide these metrics.

Official source references