Skip to main content
App Store Optimization
App Store Optimization

App Store Conversion Funnel: 2 Stages, 2 Fixes

The App Store conversion funnel has two stages: tap-through and page conversion. Here's how to read App Store Connect and find which one is leaking.

By AppScreenshotStudio Team, App Store screenshot tooling for solo indie devs9 min read

Summarize this article with AI

The App Store conversion funnel has two stages: impression to product page view (tap-through), and product page view to install (page conversion). Each one leaks for different reasons and needs a different screenshot fix. App Store Connect reports the raw counts for both, so you can find the stage that's costing you installs instead of redesigning blind.

Most conversion advice treats your rate as one number to push up. Apple reports it that way too: its headline Conversion Rate is downloads divided by impressions [1]. That single figure is the product of two separate stages multiplied together, which means a healthy stage can hide a broken one. You can be losing people in search and never notice, because your page converts fine for the few who reach it.

This post is about reading the two stages apart, working out which one is leaking, and matching the fix to the leak. For what counts as a good number once you've found the leak, see the conversion rate benchmarks by category.

TL;DR:

  • The funnel is two stages: tap-through (product page views ÷ impressions) and page conversion (downloads ÷ product page views).
  • Apple's headline Conversion Rate is downloads ÷ unique impressions [1], which collapses both stages into one number and hides which is leaking.
  • Your first three screenshots work in both stages: they show in search results [2] and on the product page. Frames four through ten only move page conversion.
  • Low tap-through is an icon, name, subtitle, ratings, and first-frame problem. Low page conversion is a full-set, preview-video, and description problem.
  • App Store Connect already reports impressions, product page views, and downloads separately, so the diagnosis costs nothing.

What is the App Store conversion funnel?

The App Store conversion funnel is the path from a user seeing your app to installing it, in two measurable steps. First, an impression becomes a product page view when someone opens your listing. Second, a product page view becomes a download when they install. App Store Connect counts all three points, so the funnel is something you can read, not just estimate [1].

Here's the detail almost every guide gets wrong. Apple defines an impression as your app being viewed for more than one second on the Today, Games, Apps, or Search tabs, and its own definition states that impressions include product page views [1]. So the two metrics aren't separate buckets stacked end to end. Product page views are a subset of impressions. Product Page Views counts every time your listing opened, including StoreKit loads, and Total Downloads sums first-time downloads and redownloads [1]. Keep that containment in mind for the math below: the tap-through stage divides one Apple metric by a larger one that already contains it.

Why does a single conversion rate number hide the problem?

Because Apple's Conversion Rate is downloads divided by unique impressions [1], it multiplies both funnel stages into one figure. A 4% rate could mean strong tap-through and weak page conversion, or the reverse. The single number tells you something is off without telling you where, so any fix you pick from it alone is a guess.

Think of it as multiplication. Your headline conversion rate is roughly your tap-through rate times your page-conversion rate. Two apps can post the identical headline number with opposite problems underneath. App A gets tapped constantly but loses most visitors once they reach the page. App B barely earns a tap in search but converts hard on the page for the few who arrive. Same rate, opposite fix. If you only watch the blended number, you'll redesign App A's product page when its real leak is the search step, and you'll never know why nothing moved.

How do you calculate each funnel stage in App Store Connect?

Pull three numbers from App Store Connect: impressions, product page views, and total downloads. Tap-through is product page views divided by impressions. Page conversion is downloads divided by product page views. Multiply the two and you land back on Apple's headline conversion rate [1]. Two ratios, one diagnosis, no extra tooling.

StageFormulaWhat it measuresWhat moves it
Tap-throughProduct Page Views ÷ ImpressionsDid people who saw you open the listingIcon, name, subtitle, ratings, first screenshots in search
Page conversionDownloads ÷ Product Page ViewsDid people who opened installFull screenshot set, preview video, description, ratings
Apple's headline rateDownloads ÷ Unique Impressions [1]Both stages combinedEverything above

One honest caveat follows from the definition above: because Apple folds product page views into impressions [1], your tap-through ratio is a proxy, not a clean stage boundary. Don't fixate on its absolute value. Watch the trend week over week, and compare it across your traffic sources, where the gap between a search visitor and a browse visitor shows up. The seven App Store Connect metrics worth watching covers where each of these numbers lives in the dashboard.

Which screenshots affect which stage of the funnel?

Your first three screenshots affect both stages; frames four through ten affect only page conversion. Apple displays up to three screenshots or app previews in search results, depending on platform and orientation [2], so frames one to three compete for the tap before anyone opens your page, then do it again on the page itself. The later frames are only ever seen by people who already tapped in.

In the search result, your app icon does most of the tap-through work, but the first screenshots sit right beside it and pull weight, especially in landscape. SplitMetrics reports a banner-style landscape screenshot reaching 15.4% in a search test where the closest competitor sat at 4.7% [3]. What actually goes inside those frames (the hook, the educate frame, the proof frame) is its own playbook, covered in the first three screenshots guide. For the funnel, the point is narrower: frames one to three carry two jobs at once, which makes them the highest-impact frames you own and the hardest to read in isolation, because a change to them nudges both stages together.

How do you fix a leaking tap-through stage?

If product page views divided by impressions is low, people see you and scroll past. That's a search-result problem, not a product-page one. Work only on the elements that appear before the tap: app icon, app name, subtitle, star rating, and how your first screenshots read as small thumbnails in search [2][3]. Nothing below the fold can move this stage.

The common mistake is redesigning the whole set to fix tap-through. Frames four through ten never appear in search [2], so that work cannot touch this number. Start with the icon, which is the largest and cheapest lever to test. Then check whether your first frame is still legible shrunk to a search thumbnail, since text that reads fine at full size turns to mud at that scale. Then try a landscape banner against your portrait set [3]. Ratings matter here too, but those you earn over time rather than design this afternoon.

How do you fix a leaking page-conversion stage?

If downloads divided by product page views is low, people open your listing and don't install. The tap-through already worked, so your search elements are fine. This stage is won or lost on the full screenshot set, the app preview video, and the description: everything that only renders once someone is on the page. Redesigning the icon here would be effort spent on a stage that isn't broken.

This is where the deeper frames earn their place. Run the listing through an App Store screenshot audit to find the frame where attention drops, then rework the set as a sequence rather than ten isolated panels. Page conversion rewards a story: hook, then features, then proof, then the close. When you're not sure which direction reads strongest, it's faster to describe the angle, see a few full-set options, and refine the one that wins than to commit to a single design and hope. Confirm the change with a controlled product page test before you trust it.

What's a good rate for each funnel stage?

It depends entirely on your category and traffic mix, so there is no universal target. A game's tap-through and a finance app's page conversion live in different worlds, and a healthy number in one category is a warning sign in another. Compare each stage against your own App Store Connect peer benchmark and your own 30-day trend, not a cross-industry average from a blog.

Apple's peer benchmarks now show your conversion against your category's percentiles, which is the only fair comparison available. The full breakdown of what counts as good by category, and why published charts disagree by up to 1.5x on the same vertical, lives in good App Store conversion rate benchmarks. Read that for the numbers. Use this post to decide which stage to point them at.

Reading the funnel before you redesign

Before you touch a single screenshot, pull impressions, product page views, and downloads, and split your conversion rate into its two stages. The math takes five minutes and tells you whether you're fixing the search thumbnail or the product page. Most redesigns stall because they polish the stage that was already working.

Tap-through and page conversion fail for different reasons and reward different work: icon and first frames for the search step, the full set and preview video for the page step. Once you know which stage is leaking, you can audit the listing for that specific weakness and spend your iterations on the frames that actually move the number.

References

  1. Metric definitions, App Store Connect Analytics Helpdeveloper.apple.com
  2. App Store Searchdeveloper.apple.com
  3. Tap-Through Rate in App Store Search and Tips on Ranking Refinementsplitmetrics.com

Related Posts