App Store Connect changed how it reviews store-page changes this month: developers can now group in-app purchases, subscriptions, custom product pages, and product page optimization tests into a single submission, with one centralized review status instead of several separate ones. That’s a real workflow win, but it also creates a new tracking gap. When a custom product page, a product page optimization test, and a new in-app purchase all ship together in one review, it’s tempting to measure their combined effect on conversion rate as a single number — which tells you the bundle worked, but nothing about which piece actually moved the needle.
That matters because these three levers behave differently. A product page optimization test changes what a visitor sees before they decide to download. A custom product page changes which audience sees which pitch. A new or restructured in-app purchase changes what happens after install. Bundling the review doesn’t mean the effects are the same, and teams that stop tracking them separately just because Apple stopped reviewing them separately will lose the ability to tell a winning headline from a winning price point.
Data Points to Track
- Conversion rate by product page variant, tracked independently for each product page optimization test arm, not just the store-listing average across all variants
- Custom product page traffic source, logged per page so you know which acquisition channel each variant is actually being shown to
- In-app purchase attach rate post-install, tracked separately from download conversion rate, since a change to the store page and a change to the paywall affect different stages of the funnel
- Review-to-live latency, tracked per submission, to measure whether the new grouped review process is actually shipping changes faster
- Statistical significance and sample size per test arm, tracked explicitly, since a bundled submission increases the temptation to call a test early
Setup Steps
- Keep product page optimization tests, custom product pages, and IAP changes tagged as distinct experiments in your analytics tooling even when they ship through the same App Store Connect submission.
- Attribute post-install events back to the specific product page variant a user saw, using App Store Connect’s test IDs, so downstream revenue can be traced to the store-page change that drove it.
- Set a minimum sample size and duration per test arm before evaluating results, independent of how quickly the grouped review approves the submission.
- Track review turnaround time for grouped submissions against your historical baseline for separate submissions, to confirm the new workflow is delivering the speed benefit it promises.
- Report store-page and paywall changes on separate dashboards, cross-referenced by submission ID, so a stakeholder glancing at either one gets an accurate read on what actually happened.
Actionable Insights
If one product page variant wins clearly on download conversion but attach rate for a bundled IAP change doesn’t move, that tells you the store page is working and the paywall isn’t — two very different fixes. If review-to-live latency drops significantly under the grouped submission process, that’s a real operational gain worth building into release planning, since faster iteration compounds over a quarter of testing. And if a custom product page’s traffic source shows most conversions coming from a channel you didn’t design the page for, that’s a mismatch worth fixing before scaling spend into it.
Related Resources
Need help tracking this in your app?
Our team sets up analytics pipelines for mobile and web teams every day. Talk to us and get your first events flowing in under an hour.
Talk to an expert