App Store Optimization
Retention and activation for discovery
Treat the first week as discovery work, because the recommendation systems now do. Scoped as its own piece because that is how it is usually bought.
Retention and activation for discovery: what it is and what it is not
Treat the first week as discovery work, because the recommendation systems now do. In practice that means onboarding instrumentation, so you know which step loses people rather than guessing, and then the harder half: activation definition for your product: the action that predicts somebody comes back.
Why this work exists
Nothing about this is difficult. It is just rarely anybody’s job, so it waits.
It belongs to App Store Optimization and is described here because it is the piece clients recognise and ask for.
The nearest piece of work to it is finding the search terms the store suggests that the keyword tools miss. Where that is already handled, this moves faster than the estimate; where it is not, the two get done together or neither of them holds.
What good looks like
It is right when the next person to touch it does not have to start by working out what was done last time.
The gap between that and where most accounts start is why this is scoped as retention and activation for discovery rather than as a line inside something larger. Working out whether the problem is impressions or the install decision is the usual second step once it is in place.
When this is the right work
The symptoms that point at this rather than something else:
- Installs are healthy and day-seven retention is not
- Recommendation placement never improves however much you spend on acquisition
- Nobody can say what activation means for your app
If none of those is true, something else is probably the constraint, and the App Store Optimization overview maps the alternatives. The usual neighbours are testing the first screenshot, which decides more than the title does and getting the subtitle to carry a benefit rather than a feature list.
What the work covers
The constituent pieces:
- Onboarding instrumentation, so you know which step loses people rather than guessing. Straightforward in principle; the detail is where it stops being quick.
- Activation definition for your product: the action that predicts somebody comes back. Skipped more often than any other part of this, and regretted more often too.
- Day one, seven and thirty cohort work, with changes judged on cohorts rather than on averages. Worth doing badly rather than not at all, if time is short.
- Habit design for the frequency your product can honestly support, usually the first thing to show a result, so it goes early.
How it runs
How an engagement on this actually proceeds.
Removing before adding
The first pass takes things away. Adding to a setup nobody has pruned in two years makes the next person’s job harder, not easier.
Agreeing what failure looks like
The conditions under which this would be called off are written down at the start. It is uncomfortable and it prevents a year of drift.
Handing back the keys
Access, documentation and whatever was built end up with the client in a form they can use without us, which is the only honest definition of finished.
What each part runs into
The obstacles differ by part and by market:
- Onboarding instrumentation, so you know which step loses people rather than guessing, and in Jaipur the constraint on it is a buying pattern that resolves faster than the reporting cycle
- Activation definition for your product: the action that predicts somebody comes back, harder in Gurugram because of a sector mix that pulls the brief in several directions
- Day one, seven and thirty cohort work, with changes judged on cohorts rather than on averages – in Hyderabad, complicated by the fact that a seasonal peak that arrives before the content is indexed
- Habit design for the frequency your product can honestly support, which in Indore runs into a reporting line that averages away the market in question
What goes wrong first
Buying installs to move a rank. It damages the retention signal that decides the next three months of placement.
This is the version most often delivered, which is why the discipline has a worse reputation than it deserves.
How it is measured
Day-seven retention by cohort, activation rate, and sessions per weekly active user. The measure is specific on purpose: a headline figure that cannot move inside the engagement is not useful.
It is worth tracking alongside one commercial number, so a technical win that sells nothing is visible as such.
What you end up with
Delivered as an activation definition, an instrumented onboarding funnel, and a prioritised list of the drop-offs worth fixing.
Structured so one section can be lifted out and sent on without the rest.
How it differs by sector
How the sector changes it:
- Manufacturing and industrial brings its own limit: low volume, high value, and a specification sheet that decides the deal.
- Automotive, constrained by the fact that Local inventory, model-level demand, and a buyer who arrives having already decided.
- Ecommerce and retail: Margin per order decides everything, and the product feed is usually the weakest asset. so this work has to account for that before anything else.
The industry pages carry the rest of that detail. Manufacturing and industrial and Automotive are the two where this piece of work most often decides the outcome.
Common questions
Is retention really an ASO factor?
On the recommendation surfaces, yes. Apple’s systems favour apps people return to, and that is where a growing share of discovery happens.
What retention number should we aim for?
Category dependent, and the useful target is a direction rather than a benchmark. Teams that move day-seven retention meaningfully tend to see placement follow within about six weeks. If this page raised a question it did not answer, try Gurugram or Houston.
What happens if we stop after this?
You keep everything: An activation definition, an instrumented onboarding funnel, and a prioritised list of the drop-offs worth fixing. Documented so your own team can continue it, including the parts we would have done next and why. What this leaves out is in Home and trade services, and some of it in Legal and professional services.
What if we disagree with the diagnosis?
Then we look at the data together. Day-seven retention by cohort, activation rate, and sessions per weekly active user is the test, and a finding that cannot survive being questioned is not a finding worth acting on. Where this gets detailed is Ecommerce SEO; where it gets argued about is Entity and Semantic SEO.
Does anything need doing before retention and activation for discovery?
Sometimes. The signals above are the honest test, and where something upstream is the real constraint we will name it even though it is not the work on this page. The cheapest version of this is in Noindex or Robots.txt disallow. The one that lasts is in Performance Max or Standard Search.
Ask about retention and activation for discovery
Whatever context you have is enough to start. The first reply is a read on the problem, not a proposal.
Find the constraint before funding the plan
We will tell you if the answer is that you do not need us yet. That happens often enough to be worth saying out loud.