Overview
A custom product page is an alternate App Store page for a specific audience: its own screenshots and promotional text, on its own link. A product page test compares versions of your page against each other.
Both live under Experiments, on two tabs: Custom product pages and Product page optimization.
Eligibility
Custom product pages
Create starts a page. Give it screenshots and promotional text for the audience it is aimed at, then submit it the way you would a listing change.
A page has its own review state, so what you can edit depends on where it is in that lifecycle.
Product page optimization
Create test sets up a comparison between treatments of your product page. Apple runs the test and reports the result in App Store Connect.
Common questions
I cannot see the create button.
Apple has not reported your app as eligible. The button is hidden rather than shown-and-broken, which is why the tab can look empty.
Check the selected app and the eligibility context described by Apple, along with your workspace permissions. A paid plan alone does not establish provider eligibility. If the guide and current app state still disagree, report the exact surface and message to support.
Can the agent draft these?
Yes, with the Experiments scope granted, and only on an eligible iOS app. Its drafts arrive in the review inbox like any other proposal.
When should I consider a custom product page?
A custom product page can help present a particular app use case to a specific audience using its own App Store page and link. Start with the audience and message you want that page to communicate, then review the screenshots and promotional text together. The app must be eligible, and the page has its own provider lifecycle. Creating a draft is not the same as making it available to customers. Check its current review state and intended destination before using the page link in a campaign.
How does a product page test differ from a custom page?
A custom product page presents an alternative page for an audience or destination link. A product page optimization test compares treatments through Apple's experiment system. The two workflows answer different questions, so choose based on the decision you need to make. Spek can help prepare supported drafts and actions, but Apple determines eligibility and runs the store test. Check the experiment results in App Store Connect; Spek's keyword rankings are not a replacement for the store's treatment-level outcome.
What should I review before submitting experiment content?
Check the target app, audience, locale and page or treatment, then inspect the text and images for accuracy and consistency. Confirm the current provider state and the scope of the action you are about to take. An Agent proposal is a starting point for this review, not evidence that the store has accepted the content. Keep any launch or campaign dependency tied to the actual provider result so a prepared draft is not mistaken for a page already available to users.
Can I judge an experiment from Analytics rank changes alone?
No. Analytics describes search presence across tracked keywords, while an App Store product-page experiment measures its own treatments using Apple's experiment data. A rank movement can be useful context during the same period, but it does not identify which treatment performed better or establish a conversion effect. Read the test outcome in App Store Connect and keep its dates and scope clear. This lets the team discuss search observations and experiment results together without presenting them as the same measurement.