ASOPROFESSIONALLET’S TALK ↗

THE ASO PROFESSIONAL FIELD GUIDE / App impressions vs product page views

SEEN IS NOT
THE SAME AS OPENED.

Distinguish app impressions from product page views before diagnosing discovery, listing engagement or conversion changes.

GET INTO THE DETAIL ↓
Gabriel Machuret examining app performance and research at work
GABRIEL MACHURET / ASO IN PRACTICE

MAKE THE THINKING VISIBLE

Similar-looking counts. Different observations.

Swipe horizontally to compare all columns →

Illustrative editorial review
MeasureQuestionCheck before comparing
ImpressionsWhere was the app seen?Surface, counting unit and source definition
Page viewsWas the product page viewed?Events versus unique audience
Custom ratioHow do the totals relate?Compatible scope; no assumed user-level sequence

Illustrative editorial framework, not client results, industry benchmarks or a prediction.

01

Name the surface and the unit.

An impression and a page view describe different observations. The exact definitions depend on the report. Record where the app was seen and whether the measure counts repeated events or unique devices or users. A label alone is not a measurement specification.

Apple’s metric reference distinguishes impressions from product page views and offers unique-device versions. Check the definition used by the exported report before building a ratio.

02

Do not assume a mandatory three-step funnel.

A tidy diagram of impression, page view and download can be useful for teaching, but it can also imply every person followed the same path. Store surfaces and reporting rules do not necessarily support that assumption.

Use the visual here as a comparison of observations, not proof of a sequential journey. Do not subtract two aggregate metrics and call the difference “people lost” unless the data actually supports that interpretation.

03

Check whether the audiences match.

Before comparing movement, align dates, markets, source filters and units. A total event count is not directly comparable with a unique audience count. Daily unique counts summed together may also differ from a deduplicated period count.

If definitions do not align, report the measures separately. The rate definitions guide shows how to label a custom ratio without pretending it is a native store metric.

04

Investigate divergence rather than naming a cause.

If exposure increases but page views do not, inspect the source mix and where the app appeared. That pattern may point to a different discovery context. It does not by itself establish that the icon or title is underperforming.

Review search versus browse alongside the timeline. Form a specific question about the audience or surface before commissioning new creative.

05

Report what the data can establish.

Explain which measure changed, over what period and for which audience. Include the limits of any ratio you calculated. If the source cannot connect exposure to a particular later action, preserve that uncertainty.

Bring the finding into the monthly report as an observation with a next investigation. Avoid filling the missing journey with a confident narrative.

CLEAR UP THE DETAILS

Common questions.

Is a page view always a separate user?

No. Check whether the report counts events or unique users/devices.

Can I divide page views by impressions?

You can calculate a descriptive ratio when the inputs are compatible, but label it clearly and do not assume it measures a linked user journey.

Does more exposure guarantee more downloads?

No. Audience relevance, discovery context and product choice still matter.

FOLLOW THE NEXT QUESTION

Keep learning.

PUT IT TO WORK ON YOUR APP

Want a second pair
of experienced eyes?

Explore the scope, deliverables and process before starting a conversation.

ASO AUDIT ↗