When the user wants to A/B test App Store product page elements to improve conversion rate. Also use when the user mentions "A/B test", "product page optimization", "test my screenshots", "test my icon", "conversion rate optimization", "CPP", or "custom product pages". For screenshot design, see screenshot-optimization. For metadata optimization, see metadata-optimization.
The ab-test-store-listing skill helps design, run, and interpret A/B tests that improve App Store conversion rate. It positions the assistant as an expert in App Store product page optimization, working from a marketing context file when present and gathering the App ID, current conversion rate, daily impressions, and the element to be tested. It is intended for conversion rate optimization work and triggers on phrases like 'A/B test', 'product page optimization', 'test my screenshots', 'test my icon', 'CPP', and 'custom product pages', deferring to companion skills for screenshot design and metadata.
It explains the two App Store mechanisms available. Apple Product Page Optimization (PPO) is the native A/B testing tool: it can test the app icon, screenshots, and app preview video (up to three variants each) but cannot test the description, title, or subtitle. PPO has documented limitations, including testing only against organic traffic, a minimum 90% confidence to declare a winner, durations of 7 to 90 days, one test at a time, and automatic traffic splits. Custom Product Pages (CPP) provide up to 35 pages per app with unique screenshots, videos, and promotional text; these are targeted pages linked from specific campaigns rather than true random traffic splits.
The skill provides a prioritization matrix (impact versus effort) recommending the first screenshot as the highest-impact test, followed by the icon, then screenshot order and style. It walks through a five-step test design framework: writing a clear hypothesis, designing two to three variants while changing only one variable, estimating required sample size and duration from daily impressions, running the test in App Store Connect without stopping early, and interpreting results using statistical significance, lift with confidence intervals, and segment differences. It includes tables of concrete test ideas for icons, screenshots, and videos with expected impact ranges, and defines output formats for a test plan, results interpretation, and a three-month testing roadmap. Related skills include screenshot-optimization, metadata-optimization, app-analytics, and aso-audit.
Apple Product Page Optimization can test the app icon, screenshots, and app preview video, with up to 3 variants each. The description, title, and subtitle are not testable via PPO.
Always start with the first screenshot. It has the highest impact because it is the first thing users see in search results and around 80% of users never scroll past the first three screenshots.
PPO tests run for 7 to 90 days, and Apple requires a minimum of 90% confidence to declare a winner. The skill recommends aiming for 95% confidence before making decisions and not stopping tests early.
No. CPPs are targeted pages (up to 35 per app) linked from specific URLs or campaigns with unique screenshots, videos, and promotional text. They are not random traffic splits, so they are not a true A/B test.
The skill uses daily-impression rules of thumb: under 1000 impressions/day tests take 30-90 days, 1000-5000 take 14-30 days, and 5000+ take 7-14 days. You need at least 1000 impressions per variant for meaningful results.
Quick Setup:
.claude/skills/Repository
eronred/aso-skills