custom-product-pages

---
name: custom-product-pages
description: Generates Custom Product Page metadata templates with screenshot strategies, keyword targeting, and audience-specific messaging for up to 35 page variants. Use when creating targeted App Store pages for different audiences, ad campaigns, or traffic sources.
license: MIT
---

# Custom Product Pages Generator

Generate metadata templates for Custom Product Pages (CPPs) — targeted App Store product page variants optimized for specific audiences, ad campaigns, or traffic sources.

## When This Skill Activates

Use this skill when the user:
- Asks to create "custom product pages" or "targeted App Store pages"
- Mentions "different App Store pages for different audiences"
- Wants to create pages for specific ad campaigns (Apple Search Ads, social media)
- Asks about A/B testing product page messaging
- Has multiple user personas and wants tailored messaging

## Minimum Eligibility

**CPPs only make sense when you have enough traffic to meaningfully split across pages.**

| Monthly Impressions | Recommendation |
|--------------------|----|
| **Under 2,000** | Don't create CPPs. Focus on optimizing your single default page. You won't have enough traffic per page to know if it's working. |
| **2,000-10,000** | Create 1 CPP max for your most distinct audience segment or highest-spend ad campaign. Monitor for 4+ weeks. |
| **10,000-50,000** | Create 2-3 CPPs. Enough traffic to compare performance across pages. |
| **50,000+** | Full CPP strategy. Multiple pages per segment, ad campaign-specific pages, seasonal variants. |

**Exception:** If you're running paid Apple Search Ads campaigns, CPPs are valuable even at lower organic volume because ad traffic is directed specifically to your CPP — you're not splitting organic impressions.

## How Custom Product Pages Work

- You can create up to **35 custom product pages** per app — prioritize a few distinctive pages over filling all 35
- Each page gets a unique URL: your default App Store link plus a product-page-ID parameter; devices below iOS 15 (or a disabled page) fall back to the default page
- You can customize: **screenshots**, **app previews**, and **promotional text**
- The app icon, name, subtitle, and description remain the same across all pages
- Each page is fully localizable, independently of the default page
- Available on iOS 15+ and macOS 12+; the App Store Connect API automates page creation at scale

### Review & Compliance

- CPP metadata goes through App Review (Guideline 2.3 — accurate metadata), though submission is binary-independent — no new build needed
- ❌ No pricing, offers, or sales language in page metadata ("50% off", "free trial") — prices vary by region and change without the page changing
- Partner/ad-network tracking against CPP traffic requires App Tracking Transparency consent
- Today-tab Apple Search Ads campaigns require a CPP with **≥4 portrait or ≥5 landscape assets** plus a separate creative review

### Search Keyword Assignment (WWDC25)

You can assign keywords to a custom product page, per language, so App Store searches on that keyword land on the matching CPP instead of the default page:

- Assignment alone needs no App Review — the page was already approved
- Make keyword selections unique per page — don't point multiple pages at the same term
- Read per-CPP search traffic in App Analytics to see which assignments pull weight

### CPP vs Product Page Optimization (PPO)
| Feature | Custom Product Pages | Product Page Optimization |
|---------|---------------------|--------------------------|
| Purpose | Targeted pages for specific audiences | A/B test default page |
| Count | Up to 35 pages | Up to 3 treatments |
| Elements | Screenshots, previews, promo text | Icon, screenshots, previews |
| URL | Unique URL per page | Same URL, random distribution |
| Use with ads | Yes (assign to ad groups) | No |

## Configuration Questions

Ask user via AskUserQuestion:

1. **How many custom pages?**
   - 1 page (single audience variant)
   - 2-3 pages (A/B campaign testing)
   - 4+ pages (multi-audience strategy)

2. **What are your distinct audiences?**
   - Different user roles (e.g., students vs. professionals)
   - Different use cases (e.g., personal vs. business)
   - Different traffic sources (e.g., Instagram vs. Google)
   - Different geographies/languages

3. **What will you customize?**
   - Screenshots only
   - Screenshots + app previews
   - Screenshots + promotional text
   - All three

4. **Traffic sources for each page?**
   - Apple Search Ads
   - Social media (Instagram, TikTok, etc.)
   - Website/blog
   - Email campaigns
   - Influencer partnerships
   - Organic/direct link

## Generation Process

### Step 1: Audience Analysis

For each audience segment:
- Define the primary value proposition
- Identify pain points this audience has
- Determine which features matter most
- Choose the emotional angle (productivity, creativity, fun, savings)

### Step 2: Generate Page Metadata

For each custom page:
1. **Page name** (internal reference)
2. **Promotional text** (170 characters, customizable per page)
3. **Screenshot strategy** (which features to highlight, in what order)
4. **App preview strategy** (optional, what to show in video)
5. **URL** (generated by App Store Connect, but plan the naming)

### Step 3: Screenshot Sequencing

Design the screenshot order for each page to match the audience's priorities:
- **Screenshot 1**: The hook — the single most compelling feature for this audience
- **Screenshot 2-3**: Core value proof — features that solve their specific problem
- **Screenshot 4-5**: Depth and trust — breadth of features, social proof

At minimum, customize the **first two screenshots** — they're the most visible (per Apple's Tech Talk). And align each page's creative with the exact ad creative sending the traffic: the page should feel like a continuation of the ad, not a reset.

### Step 4: Produce Strategy Document

## Output Format

```markdown
# Custom Product Pages Strategy: [App Name]

## Audience Segments

| Segment | Description | Traffic Source | Page URL |
|---------|-------------|---------------|----------|
| [Name] | [Who they are] | [Where they come from] | [CPP URL] |

---

## Page 1: [Audience Name]

### Audience Profile
- **Who**: [Description]
- **Pain point**: [What frustrates them]
- **Value prop**: [What you solve for them]
- **Traffic source**: [Where this page is linked]

### Promotional Text (170 chars)
> [Customized promotional text targeting this audience]

### Screenshot Strategy
| Position | Feature | Caption | Why This Audience Cares |
|----------|---------|---------|------------------------|
| 1 | [Feature] | [Caption text] | [Relevance to audience] |
| 2 | [Feature] | [Caption text] | [Relevance to audience] |
| 3 | [Feature] | [Caption text] | [Relevance to audience] |
| 4 | [Feature] | [Caption text] | [Relevance to audience] |
| 5 | [Feature] | [Caption text] | [Relevance to audience] |

### App Preview (if applicable)
- **Opening shot**: [What to show first]
- **Key demo**: [Core feature for this audience]
- **Closing CTA**: [Call to action]

### Keyword Alignment
Keywords this audience is likely searching for:
- [keyword 1]
- [keyword 2]
- [keyword 3]

---

## Page 2: [Audience Name]
[Same format as Page 1]

---

## Implementation Checklist

- [ ] Create custom pages in App Store Connect
- [ ] Upload audience-specific screenshots for each page
- [ ] Write promotional text for each page
- [ ] Get unique URLs for each page
- [ ] Configure Apple Search Ads to use specific pages (if applicable)
- [ ] Set up UTM tracking for non-ASA traffic sources
- [ ] Monitor conversion rates per page
- [ ] A/B test within pages after initial launch
```

## Strategy Templates by Use Case

### Multi-Persona App
Example: Productivity app for students, freelancers, and teams

| Page | Audience | Screenshot Focus | Promo Text Angle |
|------|----------|-----------------|-----------------|
| Default | General | Overview of all features | Broad appeal |
| CPP 1 | Students | Note-taking, study tools, price | "The study companion that..." |
| CPP 2 | Freelancers | Time tracking, invoicing, clients | "Manage your freelance..." |
| CPP 3 | Teams | Collaboration, sharing, admin | "Team productivity that..." |

### Campaign-Specific Pages
Example: Fitness app running ads on multiple channels

| Page | Channel | Visual Style | Messaging |
|------|---------|-------------|-----------|
| Default | Organic | Clean, professional | Feature-focused |
| CPP 1 | Instagram | Lifestyle, aspirational | Transformation stories |
| CPP 2 | Google Search | Results-oriented | Data and progress tracking |
| CPP 3 | Podcast | Social proof | "As heard on [podcast]" |

### Feature-Specific Pages
Example: Photo editing app with multiple use cases

| Page | Feature | Target Search Terms |
|------|---------|-------------------|
| Default | All features | "photo editor" |
| CPP 1 | Portrait mode | "portrait editor", "selfie" |
| CPP 2 | Filters | "photo filters", "instagram" |
| CPP 3 | Collage maker | "photo collage", "grid" |

## Measurement & Optimization

### Key Metrics per Page

App Analytics reports each CPP separately: page views, downloads, conversion rate, average proceeds per paying user, retention, and sessions — segmentable by territory and source.

- **Conversion rate**: the headline number per page
- **Retention per page**: monitor alongside CVR — a page can convert well yet attract the wrong audience; retention confirms audience quality
- **Average proceeds per paying user**: whether the page's audience monetizes

❌ **NEVER compare custom pages head-to-head** — each page sees a different audience, so raw CVR gaps are audience differences, not creative quality. For apples-to-apples creative testing, run PPO on a single page instead.

### Proven Results (Apple-cited)

| Developer | Tactic | Result |
|-----------|--------|--------|
| FunPlus | Audience-matched pages per campaign | +33% conversion, −14% cost per install |
| CBS Sports | Seasonal March Madness pages | +20% conversion |
| Baidu / Otto | Pairing ASA ad variations with matching CPPs | +10–12% install rate |

### Optimization Cadence
1. **Week 1-2**: Launch all pages, gather baseline data
2. **Week 3-4**: Identify best and worst performing pages
3. **Month 2**: Iterate screenshots on underperforming pages
4. **Month 3**: Test new promotional text variations
5. **Ongoing**: Refresh screenshots quarterly, adjust for seasonal relevance

## References

- Related: `generators/product-page-optimization` — A/B test the default page
- Related: `app-store/screenshot-planner` — Screenshot design and sequencing
- Related: `app-store/keyword-optimizer` — Keyword strategy per audience
- Related: `app-store/marketing-strategy` — Overall promotional strategy