How many installs it takes to rank in an App Store category
Category charts run on daily install volume. How to work out the number your app needs, where it comes from, and how to scale without tripping review.
Category charts are the cheapest organic traffic in the store, and they are also the most misread. Teams treat "get into the top 20" as a creative problem, then spend a quarter on positioning while the chart quietly rewards one thing: how many people install the app today, relative to everyone else in the category.
That framing is useful, because it turns the goal into arithmetic. Before deciding on a channel, a budget, or a launch date, you can work out the number.
Start with the number, not the campaign
Category rankings are driven by daily install volume and refresh roughly every hour. Nothing about that changes with your creative, your icon, or your description: those affect how many people convert once they land, which feeds the same number from the other end.
So the first task is a benchmark. Find the apps sitting at the position you want and estimate what they pull in a day. Tools like AppTweak, Sensor Tower, or Appfigures will get you within a workable range; you are looking for an order of magnitude, not a precise figure.
Then compare it with what you have. If the apps around rank 20 average roughly 8,000 installs a day and you are doing 2,000, your gap is a factor of four. That single number tells you more about feasibility than any strategy deck: it tells you whether the position is a month of work or a quarter, and whether the budget you have can buy it at all.
Do this per country. Category charts are ranked inside a storefront, and the difference between them is not small: a position that costs low hundreds of daily installs in a smaller MENA market can cost tens of thousands in the US. Teams that skip this step usually benchmark against the US by accident and conclude the whole thing is unaffordable.
Where the volume comes from
Once you know the gap, there are two ways to close it, and most apps that hold a position use both.
Paid campaigns
Paid user acquisition is the baseline. It is predictable, it brings users who may actually stay, and it carries no platform risk. What it does not do is move fast or cheaply enough on its own in a competitive category, and it has a ceiling. Run a channel hard enough and the audience you can reach in it thins out, CPI climbs, and daily volume starts sliding even though the budget is flat. That ceiling is the single most common reason a climb stalls halfway.
To get more out of it: segment campaigns by audience and cut the ones that underperform early, retarget users who opened the page and did not install, and keep testing creatives, because a 20 percent CPI improvement is 20 percent more volume for the same money.
Keyword installs
Keyword campaigns close the gap that paid traffic leaves. The user searches a term, finds your app in the results, and installs from there. That is what a keyword campaign does. The install counts toward the same velocity the category chart reads, and the search behavior builds visibility for that keyword at the same time.
The practical advantage is control. You choose the terms, the daily volume, and the ramp, which means you can hold a specific number instead of hoping a channel delivers it.
Build a ramp, not a spike
Whatever the mix, the shape of the curve matters as much as its height.
An app that does 2,000 installs a day for six months and then 9,000 tomorrow has a pattern that stands out from everything around it. It attracts review, and the position rarely survives the end of the campaign anyway, because the chart reads velocity, and when the volume stops the rank goes back.
A ramp that works looks boring on a graph. Add 20 to 30 percent a week, hold each step long enough to see what organic does behind it, and treat any week where organic installs fall while paid ones rise as a signal to slow down rather than push.
The same logic applies to how the volume is split. All of it arriving through one route, at one time of day, at an identical retention profile, is a pattern. Splitting across app downloads and keyword installs, varying the terms, and spreading delivery across the day gives you the same total with a distribution that reads like a lot of separate decisions, which is what real demand is.
Track the result somewhere you don't control
This is the part most teams skip, and it is the only part that settles arguments later.
Before you start, record your category position, your positions on the keywords you plan to target, and your daily installs from App Store Connect. Then track all three daily while the campaign runs, not from a vendor dashboard but from Connect.
You want to be able to answer three questions at the end: did the category position move, did the keyword positions move, and did organic installs go up or just paid ones. A campaign that lifts the chart while organic stays flat has bought you a number rather than growth, and it is better to know that in week two than in month three.
The reason to insist on Connect specifically is that a dashboard showing installs the store cannot confirm is not evidence of anything. If both sources agree, you have a result you can put in front of a board.
When the category chart is the wrong target
Sometimes the arithmetic says no, and that is a useful answer too.
If the apps at your target rank are doing 40,000 installs a day and your entire acquisition budget buys 3,000, the category is not the lever this quarter. Keyword positions are the lever instead. They cost a fraction of the volume, they bring users who searched for something specific, and they compound. A handful of terms where you rank in the top three can be worth more than a week at number 18 in a chart nobody scrolls.
The same applies right after launch, when there is no baseline to grow from. An app that the store has not indexed yet will not show up for any search term at all, which is what app downloads without a search term are for. Build search visibility first, let the category chart follow from the volume that produces, and revisit the benchmark once you have real numbers to compare against.
Frequently asked questions
- How many installs do I need to rank in an App Store category?
- There is no universal number. Category charts are relative, so the figure depends entirely on what the apps around your target position are getting each day in that specific country. In a low-competition market a few hundred daily installs can put an app in the top 20; in the US top 20 of a large category, the same position can take five figures. Measure the apps at your target rank first, then work backwards.
- How often do App Store category rankings update?
- Roughly hourly, based on a rolling window of recent install velocity. That is why a single spike moves an app for a few hours and then drops it back, since the chart is reading rate of installs, not the total you have accumulated.
- Is it safer to scale gradually or to push volume all at once?
- Gradually. A flat baseline that jumps several times over in one day is the pattern most likely to draw manual review, and a position bought that way rarely holds once the campaign stops. Adding 20 to 30 percent per week gives you a curve that looks like growth rather than an event.
- Do keyword installs help with category rank as well as search rank?
- Yes, indirectly. Every install counts toward the velocity the category chart reads, regardless of how the user reached the page. The difference is that a keyword install also builds search visibility for that term, so the same volume does two jobs instead of one.
- How do I know the ranking came from the campaign and not from something else?
- Track category position and keyword position daily from before you start, and reconcile installs against App Store Connect rather than a dashboard. If you cannot see the same movement in Connect, you cannot claim it.
