How to Use App Store Custom Product Pages (CPPs) to Boost Your Rork App Installs

You're running Apple Search Ads, getting taps, but barely any installs.

This is one of the most common frustrations for indie developers after publishing a Rork app. The issue usually isn't your targeting or bid strategy — it's that visitors landing on your product page arrived with a specific expectation, and your screenshots didn't speak to that expectation.

App Store Custom Product Pages (CPPs) directly solve this problem. Introduced by Apple in 2021 and refined over the years since, CPPs let you show different product page visuals to different audiences — without touching your app itself. In 2026, this feature is mature, powerful, and fully accessible to solo developers. If you've built an app with Rork and you're starting to invest in paid acquisition, understanding CPPs is probably the highest-leverage move available to you right now.

What Are Custom Product Pages?

By default, your app has one App Store product page — one set of screenshots, one preview video, one promotional text. Every visitor, regardless of how they found you, sees the same thing. CPPs change that.

With CPPs, you can create up to 35 additional versions of your product page. Each version can have its own:

Screenshots (up to 10 per device type: iPhone, iPad, Apple Watch)
Preview videos (up to 3)
Promotional text (the short text displayed at the very top of your page, up to 170 characters)

Everything else — your app name, description, price, ratings, and reviews — remains shared across all pages. You're not creating a different app listing; you're curating a different first impression.

The key mechanism is that each CPP receives a unique URL with a ppid parameter, like:

https://apps.apple.com/jp/app/my-app/id123456789?ppid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx

You control exactly where each URL goes: social media ads, influencer partnerships, email campaigns, QR codes in physical spaces, or Apple Search Ads campaigns. Whoever clicks that link sees the version of your page you designed for them specifically.

Why This Matters for Rork Developers

Rork lets you build and ship apps faster than any previous generation of tools. But building fast and reaching the right users efficiently are two separate challenges. CPPs are where those two challenges intersect.

Consider what happens when you have a fitness app built with Rork Max. Your single default page might show general workout tracking screenshots. But the people who find your app through different channels have very different mental models:

Someone searching "habit tracker app" is thinking about consistency, streaks, and building routines
Someone searching "calorie counter app" wants to see food logging and nutrition data
Someone clicking through from an Instagram fitness ad is responding to social proof and transformation stories
Someone clicking a review link from a fitness blog already trusts the recommendation and wants feature clarity

One page cannot speak equally well to all four of these visitors. CPPs let you meet each one on their own terms.

Creating a CPP in App Store Connect

Step 1: Build the page

Log in to App Store Connect and select your app
Navigate to the App Store tab → Custom Product Pages
Click the + button to create a new page
Give it a descriptive internal name — for example, "Instagram-diet-focused" or "ASA-morning-routine-keywords". Users never see this name; it's for your own tracking.
Select the applicable locale(s) and upload screenshots
Write your promotional text — this should reinforce the message of your screenshots, not repeat generic app copy
Submit for Apple review — typical turnaround is 24–48 hours

Once approved, your unique CPP URL is live and ready to use.

Step 2: Designing screenshots that actually convert

Don't fall into the trap of simply reordering your default screenshots for a CPP. The first screenshot in a CPP should answer the visitor's core question within two seconds: "Is this for someone like me, trying to solve the thing I'm trying to solve?"

Here's a practical framework for structuring screenshots by segment type:

// Screenshot strategy by visitor segment

[Segment A] Apple Search Ads — feature-intent keywords
  (e.g., "workout tracker", "sleep app", "budget planner")
Frame 1: Your core feature in use — shows the actual workflow, not a splash screen
Frame 2: Results or summary view — something that shows what sustained use looks like
Frame 3: Your strongest differentiator, ideally unique to your app

[Segment B] Apple Search Ads — outcome-intent keywords
  (e.g., "lose weight app", "save money app", "stop procrastinating")
Frame 1: An outcome screen — a graph going up, a number improving, a goal achieved
Frame 2: The daily use state — what a committed user's experience looks like
Frame 3: Social proof — a ratings pull quote, a user count, or a credibility signal

[Segment C] Social media traffic (Instagram, TikTok ads)
Frame 1: Emotional or lifestyle visual — aspirational, before/after, or relatable moment
Frame 2: A simple, clean UI walkthrough that builds confidence in the app
Frame 3: A low-friction CTA — free trial, no credit card, one-tap signup

For Rork Max apps using SwiftUI, the generated UI often looks polished enough to screenshot directly, but I'd recommend designing CPP-specific frames in Figma with intentional messaging layered on top. The extra hour of design work can meaningfully shift conversion rates.

Connecting CPPs to Apple Search Ads

CPPs reach their full potential when combined with Apple Search Ads Custom Product Page campaigns. This is where the segmentation becomes systematic rather than just ad-hoc.

Campaign setup

Log in to Apple Search Ads
Create a new campaign and select Custom Product Pages as the campaign type
When building an ad group, you'll be prompted to select a CPP — choose an approved one from App Store Connect
Add your keywords and bids for this specific ad group
Launch and begin accumulating data

The principle is simple: group keywords by shared intent, and assign each group a CPP designed for that intent. A habit-tracking app might have three ad groups:

"Habit tracker / routine builder / daily planner" → CPP showing streak-focused screenshots
"Meditation / mindfulness / breathing app" → CPP showing calm, minimalist screens
"Productivity / focus / time management" → CPP showing task completion and time-block views

Each CPP makes the app feel like it was built specifically for that visitor. That alignment is what drives install conversion.

Expected improvement range

When intent and visuals are aligned, CVR improvements in the 1.2x to 1.8x range compared to the default page are realistic. One app I worked on — a daily journaling app — saw about 1.4x improvement on emotional keyword segments after switching from the default page to a CPP with introspective, mood-focused visuals. Same budget, 40% more installs.

Results vary by category, competition, and how well your default page was already optimized. But even a 20% improvement in CVR means your paid acquisition becomes meaningfully more efficient.

Measuring Performance

Where to find the data

In App Store Connect, go to Analytics → Custom Product Pages. For each CPP you'll see:

Page Views: Total times the page was displayed
Installs: Installs attributed to clicks on this page
Conversion Rate (CVR): Installs ÷ Page Views, expressed as a percentage

Your goal is to compare each CPP's CVR against your default product page's CVR, which serves as your baseline.

How to read the data honestly

Avoid making decisions on small sample sizes. A CPP with 50 page views and a 10% CVR might look great, but it's not meaningful. Wait until you have at least 500–1,000 page views per CPP before drawing conclusions.

If you're running Apple Search Ads, the campaign-level data in Search Ads also shows conversion metrics tied to each CPP, which gives you a cleaner signal than the App Store Connect analytics alone.

Common Mistakes That Kill CPP Performance

Mismatched copy and visuals

Your promotional text and screenshots need to tell the same story. If your text says "AI-powered personal finance coach" but your screenshots show generic transaction lists, visitors feel a disconnect. Keep the message unified from top to bottom.

Launching too many pages at once

CPPs work best when approached as iterative experiments. Create 2–3 initially, measure results, then expand based on what you learn. Launching 15 pages simultaneously makes it impossible to understand what's driving differences in performance.

Cutting experiments short

Apple Search Ads campaigns need time to stabilize their delivery. Give each CPP at least 2–3 weeks of live traffic before comparing results. One-week snapshots are usually too noisy to be actionable.

Treating CPPs as a one-time task

CPP performance shifts as market conditions change — seasonality, competitive landscape, and even your app's rating can affect CVR. Review your CPP performance monthly and refresh underperforming visuals every quarter.

The First Step

Here's a practical starting point: identify your highest-performing Apple Search Ads keyword group, and create one CPP specifically designed for that keyword's search intent. Use screenshots that match what someone searching that query would expect to see.

Run it alongside your default page for three weeks. The CVR comparison will tell you whether this approach is worth expanding.

Rork has compressed the timeline from idea to published app dramatically. The next opportunity is to compress the timeline from published app to profitable app — and CPPs are one of the most direct levers you have for doing that.

For App Store Optimization fundamentals, see our ASO Beginner's Guide for Rork Apps. For Apple Search Ads campaign setup, our Apple Search Ads Beginner's Guide walks through the full setup step by step.