In one line
Product page views count how many times someone tapped through from a store search result or recommendation list and actually opened your product page. It is the denominator used to calculate store conversion.
Not the same as impressions
An impression is your app appearing in a list — including everyone who scrolled past on icon and title alone. Product page views count only the people who tapped in.
The numbers make the split concrete. 4,300 views on 12,900 impressions is a 33% tap-through. The other 67% dropped out at the list stage, which is an icon, title, and rating problem. Of the 4,300 who did come in, whoever did not install is a screenshot, description, and price problem. Both look like "did not install" and have entirely different causes.
Why this is the denominator
Using impressions as the denominator blends the two problems into one number, so failing to earn the tap and failing to persuade on the page become indistinguishable.
With product page views as the denominator, the rate answers "of the people who reached the page, how many installed" — isolating the page's persuasive power. 1,935 installs on 4,300 views is 45%.
The stores name and define it differently
App Store Connect calls it Product Page Views; Google Play Console calls it Store listing visitors. Apple provides unique-device variants separately, while Google counts visitors deduplicated.
Because the definitions differ, adding the two stores together into a single conversion rate is not valid. Read iOS and Android separately.
Where it is used
Splitting views and installs by traffic source shows whether a drop in store conversion came from the page or from the traffic mix. Upload a store console CSV to ASO Store Conversion Analysis to see that decomposition directly.
Go deeper
How to separate the two causes by source is covered in Store Conversion Dropped: Page Problem or Traffic Mix?.