Google Play keyword install campaign duration: how many per day, how many days

A Google Play keyword install campaign should run for 14 to 21 days at a pace of 50 to 200 installs per day, adjusted for keyword competition. Google's Play Store algorithm rewards sustained daily velocity, not burst delivery, so campaigns shorter than two weeks often fail to move a keyword rank meaningfully even when the total install count is large.

How does the Google Play algorithm read install velocity?

Play's ranking model treats install rate as a rolling signal, not an accumulator. A campaign that dumps 5,000 installs in three days looks like a promotion spike, gets discounted (or partially filtered), and produces short-lived rank movement that reverts within a week. The same 5,000 installs paced across 21 days looks like real, growing demand, and the algorithm anchors the new rank position.

Two mechanics drive this:

• Rolling window: Play weighs the last 7 to 14 days of installs more than older ones. Campaigns shorter than that window can't fill it fully.
• Anti-manipulation dampening: Sudden install spikes trigger heuristics that dampen the rank lift. A slow rise doesn't trip them.

The practical implication: total install volume matters, but install velocity spread over the algorithm's own attention window matters more.

What's the right daily volume for Google Play keyword installs?

Daily volume depends on total campaign size and keyword competition. Use this as a starting grid:

Total quantity	Recommended days	Daily rate
Under 5,000	14 days	50 to 150 installs / day
5,000 to 15,000	21 days	100 to 200 installs / day
15,000 to 50,000	30 days	300 to 500 installs / day, split across weeks
50,000+	45+ days	500 to 1,000 installs / day, phased

Two rules on top of the grid:

1. Never exceed 5x the app's organic daily install rate. If your app currently pulls 100 organic installs a day, capping your paid keyword installs at 500 per day keeps the growth curve believable. Higher than 5x reads as a promotion, not organic demand.
2. High-competition keywords need the longer end of the range. A generic keyword like "photo editor" needs weeks of sustained volume to move; a niche long-tail like "vintage film photo editor" can move on much less.

How does keyword competition change the recommendation?

Keyword competition determines how much sustained pressure the algorithm needs to see before it moves your rank. Three tiers:

• Low competition (long-tail, niche): 14 days is usually enough. 50 to 100 installs per day. Rank often lifts within the first week.
• Medium competition (branded terms, sub-category leaders): 21 days. 100 to 200 installs per day. Rank climbs in weeks 2 and 3.
• High competition (generic, top-1000 keywords): 30+ days. 300+ installs per day, and often needs to be paired with rating and review orders to hold the position after the campaign ends.

You can eyeball competition by searching the keyword yourself on Google Play and counting how many apps in the top 20 are billion-download brands. If more than half are, treat it as high competition.

Why not just run a shorter, more aggressive campaign?

Three reasons short-and-heavy campaigns underperform long-and-steady ones:

• Rank whiplash: aggressive campaigns often push a keyword up 30 spots in a week, then fall back 25 spots the next week when the velocity stops. Net gain: 5 spots for the full budget.
• Filter risk: Play's anti-manipulation dampening filters percentage of installs it decides are inorganic. Aggressive shapes trip this more.
• No compounding organic: a 3-day burst doesn't hit the "organic momentum" threshold where users searching the keyword start seeing your app and installing organically. A 21-day drip does. The last third of a well-paced campaign is often mostly organic installs.

Compare the two shapes over 21 days for the same 5,000 unit budget:

Shape	Days delivering	Daily rate	Rank lift, day 30
Burst	3 days	1,666 / day	+8 spots, back to baseline by day 21
Steady drip	21 days	238 / day	+18 spots, sustained past day 60

What about iOS App Store campaigns?

iOS is a different animal. Apple's index refreshes faster (2 to 3 days vs Google's 3 to 5) and the ranking model is less velocity-dependent. iOS campaigns can run in 7 to 14 day windows and still hit rank cleanly. We're publishing a companion iOS playbook shortly; until then, halve the "days" column in the grid above and keep the same daily rates.

Frequently asked questions

How many keyword installs per day should I order for Google Play?

For most campaigns, 50 to 200 keyword installs per day is the right zone. Under 5,000 total: 50 to 150. Between 5,000 and 15,000 total: 100 to 200. Above 15,000: 300+ but split across a longer window. Never exceed five times your app's organic install rate for that country.

How long should a Google Play keyword install campaign run?

14 to 21 days for most keywords. Low-competition long-tail keywords can move on 14 days. Medium-competition keywords need the full 21 days to hold rank. Highly competitive generic keywords need 30+ days and usually a follow-up ratings and review order to lock in the new position.

Can I hit rank faster by running a shorter, higher-daily campaign?

Usually no. Google Play's algorithm dampens aggressive install spikes as suspected promotion. A 3-day burst of the same total volume typically produces less than half the sustained rank lift of a 21-day drip, and the lift decays faster once the campaign ends.

What if my keyword is very competitive?

For high-competition keywords, extend to 30+ days and increase daily volume to 300 to 500 units, split across the window. Also plan a ratings and review order to run in the last week of the install campaign, so the improved star rating locks in the higher rank position after installs stop.

How does this compare to iOS App Store campaigns?

iOS is faster: Apple's index refreshes in 2 to 3 days, so 7 to 14 day campaigns are typical for iOS keywords. Daily volumes are similar. If you're running the same keyword on both stores, expect the iOS campaign to hit rank a week or two before the Google Play campaign catches up.

Sources

• Google Play Console Help: Understanding your app's performance (2024, retrieved 2026-06-19)
• Play Console Academy: App visibility on Google Play (Google, 2024, retrieved 2026-06-19)
• App Store Optimization: A Practitioner's Guide, chapter 4 (Appfigures, 2024, retrieved 2026-06-19)