App Store Listings
Part of Mobile growth programme reviews
Deciding when to fix the app before buying more traffic
Use confirmed task failures, eligibility and mature outcomes to decide whether to repair the app, adjust targeting or test more spend.
Fix the app before expanding paid traffic when eligible people already arrive but a verified product failure prevents them from completing the advertised task. Consider more qualified reach when the task works for the intended audience and completed outcomes support the additional spend. If measurement is uncertain, settle that question before claiming either case.
Identify the blocking step
Trace the promise from the ad or listing through first open, eligibility, task start and confirmed result. Name where an eligible person cannot continue. Investigate the affected product route for a blank destination, repeated task error or failed confirmation. Low qualified entry with a working task points to a reach question instead.
Do not infer a broken app from downloads alone.
| Evidence | Initial decision | Check before acting |
|---|---|---|
| Eligible people repeatedly encounter a confirmed blocking failure | Repair or hold traffic to the affected route | Platform, app version, region and recovery path |
| The task works, but many acquired people are ineligible | Correct targeting or the promise | Actual eligibility and entry source |
| Qualified entry is low and eligible people complete the task | Consider a bounded acquisition test | Later outcomes and the cost the business can support |
| Events or populations do not reconcile | Investigate measurement | Event firing, identity, periods and report rules |
Set a spend gate
A working first task is necessary evidence, not the whole spend decision. Check the campaign can reach the locations and devices the app serves, its promise matches the available task, and the team can observe confirmed first value.
Where later use matters, inspect mature cohorts under a consistent action and window. A change in acquisition mix can shift the overall rate without a product change.
If a blocking path is confirmed, name the owner and successful state required before broad spend resumes. Verify the repair on the affected routes. If only one segment is affected, other eligible routes may still support a narrower campaign.
If the task works, set an eligible audience, accurate promise, business-chosen spending limit and confirmed first-value outcome for a small acquisition test. Add a later-use check when the task recurs.
Decide in advance what evidence would justify expansion, revision or stopping. Record the decision against completed user outcomes rather than the install chart alone.
Key metrics to evaluate before scaling paid traffic
- First-value conversion rate
- Must be confirmed for eligible users
- Eligibility rate of acquired users
- Compare actual eligibility vs. promised audience
- App version coverage
- Ensure all targeted versions support the task
- Cost per qualified acquisition
- Assess business affordability before scaling
