Apple gives you two ways to show different screenshots to different people: Product Page Optimization and Custom Product Pages. They sound alike, both live in App Store Connect, and both let you upload alternate screenshots. But they answer different questions:
- Product Page Optimization: Which version of my product page converts best?
- Custom Product Pages: What should this particular audience see?
Side by Side #
| Product Page Optimization | Custom Product Pages | |
|---|---|---|
| Purpose | A/B test your default product page | Tailored pages for specific audiences |
| Who sees it | A random share of normal App Store visitors | People who follow the page's URL, or search a keyword you assigned to it |
| How many | 1 test at a time, up to 3 treatments | Up to 70 pages |
| How long | Up to 90 days | Stays live until you remove it |
| What can vary | Screenshots, app previews, app icon | Screenshots, app previews, promotional text |
| Own URL | No | Yes |
| Search keywords | No | Yes, can replace your default page for chosen keywords |
| Deep link into the app | No | Yes (iOS 18 and later) |
| Results | Conversion rate, improvement and confidence per treatment | Impressions, downloads, conversion, retention and proceeds in App Analytics |
| App Review | Treatments are reviewed; a new icon must be in the app binary | Pages are reviewed, independent of app updates |
When to Use Product Page Optimization #
Use it when you want to improve the page most people see. Almost all of your organic traffic lands on your default product page. A test there tells you whether a new first screenshot, caption style or icon converts better, with real visitors and a confidence level.
When a treatment wins, you apply it and it becomes your default product page.
Typical uses:
- Testing a new first screenshot or caption style (see 25 screenshot A/B test ideas)
- Testing a new icon before a rebrand
- Checking that a redesign doesn't lower conversion before you ship it to everyone
Read how to A/B test your App Store screenshots for the setup.
When to Use Custom Product Pages #
Use them when different people come for different reasons. A photo editor might have one page for people searching "remove background", one for an Instagram ad about filters, and one for a partner's newsletter. Each page shows the screenshots that match what that person came for.
Typical uses:
- Matching ads: send each campaign to a page that shows what the ad promised
- Search: assign keywords so a page with matching screenshots replaces your default page in those results
- Features or seasons: a page for a big feature or a holiday, linked from your own marketing
Apple says custom product pages increase conversion by 2.5 percentage points on average compared with the default page, because the page matches what people expect.
Use Both, in This Order #
They work well together:
- Optimize the default page first. It gets most of your traffic, so a win there pays off most. Run a Product Page Optimization test and apply the winner.
- Then build custom pages for the audiences you can reach separately: ad campaigns, keyword groups, features.
- Bring what you learn back. If a custom page for one keyword converts much better, that angle is worth a Product Page Optimization test on your default page.
The Common Problem: More Screenshot Sets #
Both features multiply the screenshots you need. Three test variants or ten custom pages, each in every language and device size, is a lot of sets to make and keep up to date.
Screenshot Studio keeps every language and device size in one project, so a variant is one design change, not dozens of files. For tests, it uploads a variant straight into your Product Page Optimization test. For custom product pages, export the sets and add them in App Store Connect.
Before you start a test, check how long it will take with the A/B test calculator.