---
title: "Store conversion rate"
description: "A definition of listing conversion rate as a funnel of ratios — impressions to views to installs — and why the split is usually the diagnosis."
excerpt: "Never act on conversion rate as one number: split it by ratio and traffic source first — the split is usually the diagnosis."
source_url: "https://appstorehelper.com/glossary/store-conversion-rate"
mirror_url: "https://appstorehelper.com/mirror/glossary/store-conversion-rate"
section: "A shared ASO and creative-ops vocabulary"
locale: "en"
published_at: "2026-07-30"
updated_at: "2026-07-30"
reading_time: "4 min read"
tags:
  - "conversion rate"
  - "glossary"
  - "ASO metrics"
  - "funnel"
---

## Direct definition

Store conversion rate is the share of people who see your app in the store and go on to install it. Both platforms report versions of it — App Store Connect distinguishes impressions (appearances in search, browse, or lists) from product page views, and Play Console reports store listing visitors to installers — which creates two meaningfully different ratios: view-to-install (how well the product page converts people who arrived) and impression-to-install (how well the whole presence converts people who merely saw it). The distinction is diagnostic: a weak impression-to-view ratio implicates the search-result card — icon, title, first screenshots — while a weak view-to-install ratio implicates the full page: deeper screenshots, description, ratings.

## Why it matters

Conversion rate is the half of ASO that multiplies everything else. Ranking improvements pour more visitors into the same funnel; a conversion improvement raises the yield of every visitor from every source, paid included. It is also the metric that store algorithms themselves respond to — listings that convert their impressions tend to earn more of them.

## Reading the funnel

| Ratio | Weak number implicates | Typical fixes |
| --- | --- | --- |
| Impressions → page views | Search-result card: icon, title, first screenshot | Sharper hook frame, clearer title promise |
| Page views → installs | Full page: screenshot sequence, description, rating | Proof frames, objection answers, rating repair |
| Impressions → installs | The listing overall, or traffic relevance | Check keyword relevance before touching assets |

Benchmarks vary enormously by category, brand traffic share, and traffic source — compare against your own history and traffic mix, not a global average.

## Signs conversion is being managed

- Conversion is read per traffic source; search, browse, and referral convert differently and mixing them hides changes.
- Branded and generic search are separated — brand queries convert at rates that flatter the blended number.
- Every conversion movement gets attributed to a ratio (card or page) before any asset is changed.
- Experiments target the implicated surface, one variable at a time.

## What usually goes wrong

### One blended number

A rising share of branded traffic lifts blended conversion while generic conversion quietly falls — the listing looks healthier as it gets worse at its real job.

### Comparing against category folklore

"Good apps convert at 30%" folklore ignores that a utility with brand traffic and a game acquiring cold users live in different statistical worlds.

### Fixing the page when the card is broken

Teams redesign deep screenshots when the leak is impression-to-view — visitors never reached the page the redesign improved.

## Operating rule

Never act on conversion rate as one number. Split it by ratio and by traffic source first; the split is usually the diagnosis.