DEV Community

Shotlingo
Shotlingo

Posted on Originally published at shotlingo.com

Apple Custom Product Pages: set one up in five steps

If you run paid campaigns or social promotions for your iOS app and still send every visitor to the same App Store listing, you are using one page for every audience. Apple Custom Product Pages (CPP) let you build alternate versions of your product page inside App Store Connect, and each one gets its own URL.

Here is what they are and the five steps to set one up.

What a Custom Product Page can change

Each custom page can have its own screenshots, app preview videos and promotional text. The app name, subtitle, icon, description and keywords stay the same as your default listing. You can have up to 35 active custom product pages per app.

Because the metadata stays the same, your default page keeps doing the organic search work. The custom pages are for the traffic you send yourself.

CPP is not PPO

People mix these up. Custom Product Pages target different audiences with different content, and you drive the traffic through each page's URL. Product Page Optimization (PPO) tests which content converts best on your default page, and Apple splits the organic traffic for you. If you want a statistical winner, use PPO. If you want a page for one specific audience or campaign, use CPP.

The five steps

  1. Create the variant. In App Store Connect, open your app, go to Custom Product Pages and add a new page. Give it a clear internal name, for example Runners-Q2-Meta. Users never see it.
  2. Customize it. Upload screenshots for every device size you support. You can also replace the app preview video and the promotional text. Treat each variant like its own creative brief.
  3. Submit for review. Each custom page goes through App Review, and you can submit it without a new app build.
  4. Get the unique URL. Once approved, the page gets a URL with a ppid parameter that tells Apple which variant to serve. Visitors without iOS 15 or later see your default page.
  5. Send the right traffic to it. Use the ppid link in ad campaigns, social posts, newsletters, partner pages or QR codes.

Measure each page against the default

In App Analytics, open the Sources panel and look at Custom Product Pages. For every variant you see impressions, product page views, conversion rate and downloads. Compare conversion rate, not only total downloads, and give each variant enough page views before you draw conclusions.

Mistakes to avoid

  • Treating CPP like an A/B test. It does not split traffic for you.
  • Building too many variants too fast. Start with three to five audiences you can maintain.
  • Forgetting localization. A custom page is per locale, like the default page.
  • Leaving the first screenshot unchanged. If it is the same in every variant, you are barely customizing anything.
  • Ad and page that do not match. The hook in the ad should match the hero shot on the page.

The full version, with the category examples and the FAQ, is in our guide: App Store Custom Product Pages (CPP): Setup in 5 Steps. I work on ShotLingo, a tool for building and localizing App Store screenshots, at shotlingo.com.

What would you add to this list?

Top comments (0)