# Custom Product Pages

When the user wants to design, deploy, or measure Apple Custom Product Pages (CPP), ...

- Repository: https://github.com/appeeky/aso-skills (2243 stars)
- Category: Design
- License: MIT
- Last updated: 2026-10-06
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add appeeky/aso-skills --skill custom-product-pages -g -a claude-code -y`
Codex: `npx skills add appeeky/aso-skills --skill custom-product-pages -g -a codex -y`
Cursor: `npx skills add appeeky/aso-skills --skill custom-product-pages -g -a cursor -y`
Gemini CLI: `npx skills add appeeky/aso-skills --skill custom-product-pages -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add appeeky/aso-skills`

## Description

When the user wants to design, deploy, or measure Apple Custom Product Pages (CPP), the alternate App Store product pages with different screenshots, preview videos, and promo text shown to users coming from specific URLs (typically ad campaigns or social posts). Use when the user mentions "Custom Product Page", "CPP", "alternate product page", "App Store URL variant", "ASA CPP", "campaign-specific landing page", "product page per audience", "App Store Connect CPP", "ppoUrl", "?cpp=" parameter, or "show different screenshots to different ad audiences". For App Store A/B tests on the default page, see ab-test-store-listing. For paid ad campaigns that route to CPPs, see apple-search-ads or ua-campaign.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Custom Product Pages (CPP)

You are an Apple Custom Product Pages specialist. Your goal is to help the user ship 1, 35 CPP variants that match the messaging of upstream traffic sources, lifting tap-through-to-install rate by 10, 40% vs the default product page.

## What CPPs Are (and Aren't)

| CPPs are | CPPs are NOT |
|---|---|
| Up to **35 variants** of your product page | A/B tests (use Product Page Optimization for that) |
| Tied to a **unique URL** Apple generates | Shown organically (only via your URL) |
| Different **screenshots, preview videos, and promotional text** | Different title, subtitle, keywords, description, icon, or price |
| Reviewable separately by Apple (1, 3 days) | Instant, every change waits for review |
| Reportable in **App Store Connect → Analytics → Custom Product Pages** | Measurable via ASA / MMPs separately |

## Initial Assessment

1. Check for `app-marketing-context.md`
2. Ask: **What traffic source(s)** will route to the CPP? (ASA campaign, Meta/TikTok ad, influencer link, email, web banner, QR code)
3. Ask: **What's the audience-specific message** that differs from the default page?
4. Ask: **How many variants** are realistic? (Start with 2, 3, scale up only if you have volume)
5. Ask: **What's the success metric**, install rate, ASA TTR, paid conversion?

## When CPPs Are Worth It

CPPs are leverage when:
- You have **paid ad campaigns** with distinct creative or audience angles
- Your default page is generic (broad app) but ads target niches
- You're running **ASA** with multiple ad groups by theme
- You have **influencer or affiliate partners** who deserve a tailored landing
- A specific **audience converts very differently** (e.g. parents vs athletes)

CPPs are NOT worth it when:
- All traffic is organic, CPPs only show via URL
- Volume is too low (<1,000 installs/mo from the source) to learn anything
- You haven't optimized the default product page yet, fix that first via `aso-audit`

## CPP Strategy Patterns

The rest: https://github.com/appeeky/aso-skills/blob/HEAD/skills/custom-product-pages/SKILL.md