Apple Custom Product Pages: How to A/B Test Your App Store Listing
Apple Custom Product Pages and Product Page Optimization let you A/B test your App Store screenshots, icons, and previews without risking your main listing. Here's how both features work and what to test first.
Apple Custom Product Pages: How to A/B Test Your App Store Listing
Apple Custom Product Pages and Product Page Optimization let you A/B test your App Store screenshots, icons, and previews without risking your main listing. Here's how both features work and what to test first.
Two Features, Two Purposes
Apple offers two related but distinct features for testing and customizing your App Store listing:
- 1.Product Page Optimization (PPO): A/B testing your default product page. You create up to 3 treatment variants (with different screenshots, icons, or previews) and Apple splits traffic between your original and the treatments. You see which variant converts best, then apply the winner to your default page.
- 2.Custom Product Pages (CPP): creating up to 70 unique product pages per app, each with different screenshots, icons, and previews. Each CPP has a unique URL that you can link to from Apple Search Ads, social media, email campaigns, or your website. Users who arrive via a CPP URL see that specific page instead of your default.
Key difference: PPO is for testing (find the best version). CPP is for targeting (show the right version to the right audience). Many apps use both: PPO to find the best default page, and CPPs to target specific audiences.
Product Page Optimization: How It Works
PPO lets you A/B test your default product page elements:
What you can test:
- •App icon
- •Screenshots (all device sizes)
- •App preview videos
What you can't test:
- •App name, subtitle, description, keywords (these require a new submission)
- •Promotional text (can be updated anytime without testing)
- •Category, age rating, privacy policy
How to set up a PPO test:
- 1.Go to App Store Connect → your app → Product Page Optimization
- 2.Click 'Create Test'
- 3.Create up to 3 treatment variants
- 4.For each variant, upload different screenshots, icon, or preview
- 5.Set the traffic split (e.g., 50% original, 50% treatment)
- 6.Start the test
- 7.Apple collects data and shows you conversion rates for each variant
- 8.When you have a statistically significant winner, apply it to your default page
Requirements:
- •Your app must have enough daily impressions for meaningful results (Apple recommends 1,000+ daily impressions)
- •Tests run for a minimum of 7 days
- •You can run one test at a time per app
Custom Product Pages: How They Work
CPPs let you create targeted product pages for different audiences:
What you can customize per CPP:
- •Screenshots (all device sizes)
- •App icon
- •App preview videos
What stays the same across all CPPs:
- •App name, subtitle, description, keywords
- •Promotional text
- •Category, age rating, privacy policy
- •In-App Purchases
How to create a CPP:
- 1.Go to App Store Connect → your app → Custom Product Pages
- 2.Click 'Create New Page'
- 3.Upload different screenshots, icon, or preview
- 4.Apple generates a unique URL for this page
- 5.Use this URL in your Apple Search Ads campaigns, social media, email, or web links
- 6.Users who click the URL see this specific page instead of your default
Use cases for CPPs:
- •Apple Search Ads: show different screenshots for different keyword campaigns (e.g., 'meditation' vs 'sleep tracking' for a meditation app)
- •Social media campaigns: tailor screenshots to the platform (e.g., TikTok audience vs LinkedIn audience)
- •Email campaigns: show seasonal or promotion-specific screenshots
- •Regional targeting: show different screenshots for different markets (though full localization is better)
- •Feature-specific campaigns: highlight a specific feature that matches the ad's promise
What to Test First
When starting with PPO, prioritize these tests:
- 1.First screenshot (highest impact): the first screenshot is what most users see in search results. Test different captions, backgrounds, and layouts. This is the single highest-impact test.
- 2.Screenshot set order: test different orderings of your screenshots. The first 3 screenshots carry the most weight.
- 3.Screenshot style: test flat vs 3D device frames, different background colors, different caption styles.
- 4.App icon: test different icon designs. The icon affects click-through rate from search results and browse.
- 5.App preview video: if you have a preview video, test different openings (the first 3 seconds matter most).
What not to test first:
- •Minor changes (e.g., 2px difference in caption position): too small to produce significant results
- •Multiple variables at once: test one thing at a time to know what caused the difference
- •Low-traffic apps: if you don't have 1,000+ daily impressions, PPO data won't be significant
How to Create Screenshots for Testing
For PPO and CPPs, you need multiple screenshot variants. Here's the efficient workflow:
- 1.Create your base screenshot design in a screenshot generator
- 2.Export the base set at all required device sizes
- 3.Duplicate the project and change one element (caption, background, layout)
- 4.Export the variant set
- 5.Upload to App Store Connect as a PPO treatment or CPP
This is where a screenshot generator with project saving shines: you can create one base design, duplicate it, make small changes, and export multiple variants in minutes. Manual Photoshop workflows take hours for the same.
Tips for test variants:
- •Change one variable at a time: if you change both caption and background, you won't know which caused the difference
- •Make meaningful changes: test 'Track Sleep Patterns' vs 'Sleep Better Tonight', not 'Track Sleep' vs 'Track Sleep.'
- •Test bold hypotheses: '3D device frame' vs 'flat frame' is a meaningful test. '3D at 15 degrees' vs '3D at 20 degrees' is too subtle.
- •Keep variants on-brand: even test variants should look professional. A bad variant that wins is still bad.
Interpreting Test Results
Apple shows you these metrics for PPO tests:
- •Conversion rate: the percentage of product page views that result in installs. This is the primary metric.
- •Improvement: the percentage difference between the treatment and the original.
- •Confidence: how statistically significant the result is. Apple shows this as a percentage.
- •Impressions: how many users saw each variant.
How to interpret:
- •High confidence (>90%) + positive improvement: apply this variant to your default page
- •High confidence + negative improvement: keep your original, the variant is worse
- •Low confidence (<90%): the test needs more data. Let it run longer or increase traffic.
- •No difference: the change didn't matter. Try a more significant change next.
Common pitfalls:
- •Stopping tests too early: wait for statistical significance, not just early leads
- •Testing too many things at once: isolate variables to understand what works
- •Ignoring seasonality: a variant that wins during holidays may not win year-round
- •Not testing long enough: 7 days is the minimum; 14 days accounts for day-of-week variation
- •Over-optimizing: once you find a winner, move on to testing something else. Diminishing returns on the same variable.
Combining PPO and CPPs for Maximum Impact
Advanced strategy: use both features together:
- 1.Use PPO to find your best default page: test screenshot variants and apply the winner to your default listing.
- 2.Use CPPs for audience-specific targeting: create custom pages for different Apple Search Ads campaigns, social media audiences, or regional campaigns.
- 3.Use PPO insights for CPPs: if PPO shows that '3D device frames' convert better, use 3D frames in your CPPs too. But if a specific audience responds differently (e.g., enterprise users prefer flat frames), create a CPP with flat frames for that audience.
- 4.Test CPPs with PPO: you can run PPO tests on your CPPs too, not just your default page. This lets you optimize each audience-specific page.
- 5.Track performance per CPP: App Store Connect shows analytics per CPP, so you can see which custom pages convert best and double down on what works.
Create Screenshots for A/B Testing
Create multiple screenshot variants for PPO and CPPs in minutes. Free, no sign-up, export at all device sizes.
Create Screenshots for A/B Testing (Free)Related Articles
ASO Best Practices for 2026: The Complete Guide
The definitive guide to App Store Optimization in 2026. Learn the latest best practices for screenshots, keywords, localization, and conversion optimization.
ASO Trends to Watch in 2026
Stay ahead of the curve with the top ASO trends for 2026. Auto localization, dark mode, video-first listings, and more.
App Store vs Google Play: Screenshot Differences Explained
Learn the key differences between App Store and Google Play screenshot requirements, sizes, and best practices.