ASO workflow · measurement
Separate the App Store funnel before changing your listing
Impressions, product-page views, downloads, and activation answer different questions. Treating them as one conversion rate sends you after the wrong fix.
July 21, 2026 · Michael at Yuzool
A new app can have a healthy product-page conversion rate and still be invisible. It can also have plenty of impressions and a weak page. Or it can convert downloads and lose people during onboarding. Those are three different problems, and they need three different experiments.
The four numbers to keep apart
1. Impressions
How often Apple showed the app in search, browse, or a relevant surface. Low impressions are a discovery or relevance problem. Rewriting screenshots will not create demand for a phrase nobody is seeing.
2. Product-page views
How many people opened the listing after seeing it. Compare views with impressions to learn whether the title, icon, subtitle, and search intent earn the click.
3. First-time downloads
How many new people installed. Compare downloads with product-page views to understand whether the listing explains a compelling outcome clearly enough.
4. Activation
Whether a new user reaches the first useful moment: creates the first item, finishes the first task, or starts a trial. A download without activation is not yet a customer signal.
Use the ratios to choose the next action
Low impressions + healthy page conversion: keep the page stable and work on positioning, search language, category relevance, external discovery, and a small number of lower-competition phrases.
Healthy impressions + low page views: test the title, icon, subtitle, and first screenshot. The question is “why should I open this result?”
Healthy page views + low downloads: the page is getting attention but not making the value concrete. Rewrite screenshot one around the job it fixes, not a tour of features.
Downloads + weak activation: stop changing keywords for a moment. Inspect onboarding, paywall timing, first-run speed, and whether the promised outcome appears quickly.
What to write down each week
- Which search or browse surface produced the impressions?
- What promise did the title and first screenshot make?
- Where did the largest drop happen: impression → view, view → download, or download → activation?
- What single change will run next, and when will you check it?
This is the same discipline we use when growing Dispatch Kun and Rank: make one decision, ship one small change, and keep the evidence attached to the decision. More dashboards are not the goal. A clearer next action is.