How to use third-party ranking data carefully
Follow these steps in order. Each one is something we do on client work.
- Know it's an estimate. Third-party tools model rankings and downloads; your console data is the source of truth.
- Track your category and keywords. Watch trends, not single days.
- Compare competitors' metadata changes. See what they changed and when.
- Cross-check with your console. App Analytics and Play Console show real impressions.
- Decide what to test. Turn observations into a test plan.
- Re-check monthly. Trends matter more than snapshots.
Sensor Tower app rankings: key rules and context
What you get. Chart history by country and category, estimated downloads/revenue, keyword rankings and ad intelligence (on paid plans).
Limits. Estimates come from models; small apps can be badly off. Keyword volume scores are relative, not absolute.
Alternatives. Other tools offer similar data; see ASO tools and ASO search volume.
Use it well. Watch competitors' metadata changes and chart moves after updates.
Worked example (hypothetical)
This example is illustrative. The app is made up, and so are any numbers in it.
Say a tool shows PuzzleMint dropping in a category chart on a weekday. Before reacting, we'd check App Analytics: if impressions are steady, it's likely noise from chart movement among others, not a problem with the listing.
Common mistakes
- Treating estimates as facts. Use them as signals.
- Reacting to one day. Look at weeks.
- Copying competitors. Learn, don't clone.
- Ignoring your own data. It's more accurate.
If you want this handled for you, our pricing page lists every fixed package.
App Store vs Google Play: where your words go
The two stores index different fields. This is the comparison we use when we plan a listing for both.
| Element | App Store | Google Play |
|---|---|---|
| Title | 30 characters (app name) | 30 characters (app name) |
| Second line | Subtitle, 30 characters | Short description, 80 characters |
| Hidden keywords | Keyword field, 100 bytes | None; the visible text does the work |
| Long text | Description, 4,000 characters | Full description, 4,000 characters |
| Editable without review | Promotional text, 170 characters | Listing edits still go through review |
| Native A/B tests | Product page optimization (up to three treatments) | Store listing experiments (up to two variants) |
How we measure the result
Here is how we judge whether Sensor Tower app rankings work is paying off. We log the date of each metadata change and compare the four weeks before it with the four weeks after it. When nothing moves at all, the chosen terms were likely too competitive or not relevant enough, and we return to keyword research.
Checklist
Copy this list into your release notes or ticket and tick each item off before you ship.
- Third-party data labelled as estimate
- Trends tracked
- Competitor changes logged
- Console data compared
- Test plan written
Sources
- Apple: Search on the App Store (accessed 26 October 2026)
- Apple App Store Connect Help: App information (accessed 26 October 2026)
- Apple App Store Connect Help: Platform version information (accessed 26 October 2026)
- Play Console Help: Create and set up your app (accessed 26 October 2026)
- Apple App Store Connect Help: Overview of product page optimization (accessed 26 October 2026)
- Play Console Help: Run store listing experiments (accessed 26 October 2026)
Questions
Are Sensor Tower downloads accurate?
They're estimates.
Is it free?
Limited free data; main features are paid.
Does Apple publish downloads?
Only to the developer.
Can I see competitor keywords?
Tools estimate them.
Do you use these tools?
We use several in research.
Is Sensor Tower data accurate?
It's a modelled estimate. Use it for direction and verify with App Store Connect and Play Console data.