Why the same listing change reads differently on Play

App Store Connect and Play Console do not share a dictionary. “Product page view” and “store listing visitors” are cousins, not twins. Acquisition reports on Play further split traffic in ways that tempt a one-to-one join with iOS source types. That join is almost always wrong. In the Play Console Funnel Clinic we spend the first evening just aligning names before anyone proposes a creative change.

Video behaviour differs too. Play visitors often give the preview more time than iOS visitors give a screenshot carousel. An iOS-weighted sequence that buries proof of the core job until frame four can underperform on Android, where the video may already have done that job — or failed to. The edtech case on our reviews page moved video emphasis without copying the iOS carousel length.

Short description versus subtitle

Play’s short description is a conversion surface at impression time in a way the iOS subtitle is not. Teams that only localise screenshots and leave a weak short description are testing the wrong room. Conversion insight means asking which metric you expected to move. Impressions and listing conversion are different rooms.

Reporting without false symmetry

When we ask alumni to report both stores, we want two recaps, not a blended “mobile” slide. Different denominators, different holiday effects if the install base differs by platform, different sample sizes. A Thailand iOS listing and a Thailand Play listing can disagree in April for reasons that have nothing to do with screenshots.

If your org is Android-first, start with the clinic on the labs page. If you hold both stores, the flagship Conversion Lab still helps — just do not expect module one to speak Play fluently.