FunnelHound / Guides / Tap-through rate
What is a good App Store tap-through rate?
Tap-through rate (TTR) is product page views ÷ impressions — the share of people who saw your app in the App Store and opened its listing. For search traffic, roughly 3–6% is typical; browse and featuring placements run far lower. A low TTR points at what searchers see before tapping: icon, name, subtitle, rating and the first screenshots.
How tap-through rate is calculated
The formula is simple: TTR = product page views ÷ impressions. An impression is your icon visible on screen for at least one second anywhere in the store; a page view means the user opened your full listing — the definitions and their quirks are covered in the impressions vs product page views guide. A 4% TTR means 4 of every 100 people who saw your icon cared enough to tap. Watch your denominators: App Store Connect reports both total and unique-device counts for each metric, and mixing a unique numerator with a total denominator quietly deflates the rate. Use the same basis on both sides, and compare periods with a similar traffic mix.
Benchmarks: what "good" looks like
For search traffic, roughly 3–6% is the typical band — searchers have intent, so they tap more. But the number varies hard by category and, above all, by placement. Search results, where users asked for something like you, convert to page views at several times the rate of Today-tab or browse features, where your icon is shown to people mid-scroll who never asked. That means a blended TTR is nearly meaningless during a featuring week: thousands of low-intent browse impressions pour into the denominator and your rate "collapses" while nothing about your listing changed. Judge TTR per source, against your own history and category — not against a single global average.
What a searcher sees before tapping
TTR is decided by the search result card, not by your product page. Before tapping, a searcher sees your icon, app name, subtitle, star rating and — for many results — the first screenshots rendered right in the results list. That's the entire ballot. If your TTR is low, the diagnosis is confined to those five elements:
- Icon: contrast and recognizability at small sizes beat detail. It must read at a glance next to nine competitors.
- Name: front-load the value keyword — users scan the first two or three words.
- Subtitle: state the benefit, not a slogan.
- Rating: below ~4.0 stars, everything else works harder for less.
- First screenshots: for search layouts that show them, they are search creative, not page decoration.
Testing: what moves TTR and what can't
Apple's Product Page Optimization (PPO) tests deserve a precise reading: PPO treatments affect only your product page — screenshots, preview videos, promo text — so a winning screenshot variant improves page-view-to-download conversion, not TTR. The exception is the icon: an icon test changes what appears in search results too, so icon variants are the one PPO lever that moves tap-through. Think of the funnel as two leaks in sequence — TTR is the first leak (impression → page view) and page-view-to-download conversion is the second. Diagnose them separately: fixing screenshots when the leak is your icon burns a test cycle on the wrong stage.
Watching TTR without opening a laptop
A tap-through problem is invisible if you only glance at downloads — the drop happens two stages upstream. FunnelHound pulls impressions and page views from the App Store Connect API and shows a tap-through gauge with your category benchmark drawn on the dial, right on your iPhone, alongside the rest of the Impressions → Installs → Purchases funnel and the source split that tells you whether a TTR dip is real or just a browse-traffic surge.
Catch the first leak in your funnel
FunnelHound shows your tap-through rate against your category benchmark, on a gauge on your iPhone — straight from App Store Connect.
Get FunnelHoundData notes: the 3–6% search TTR band is a directional median from public ASO benchmark reports; placement mix, category and brand strength shift it substantially. App Store Connect data lags real activity by roughly 2–3 days. PPO behavior per Apple's Product Page Optimization documentation as of 2026.