# Custom product pages Human Guide ## What This Is For Provides Apple Custom Product Pages specialist. It gives the agent a clearer input/output frame for custom product pages: what context to ask for, what decisions to make, and what usable artifact to return. Use this as a human-readable version of the Custom product pages agent skill. It is meant for marketers, operators, founders, and other non-coders who want the workflow without reading agent-specific implementation instructions. ## When To Use This - Use this when you need a repeatable process for custom product pages. - Use this when the task needs judgment, examples, constraints, or a clear output format rather than a one-off prompt. - Use this when you want to hand an AI assistant enough context to produce a usable marketing artifact. ## When Not To Use This - Do not use this when you only need a quick factual answer. - Do not use this when the work depends on private data you cannot share with the assistant. - Do not use this as a replacement for legal, compliance, financial, or medical review. ## What You Need Before Starting - The goal or business outcome you want. - The audience, customer segment, or market context. - Any source material the assistant should respect, such as notes, briefs, examples, URLs, or brand guidance. - Constraints such as tone, length, channel, deadline, region, or approval requirements. - A clear definition of what a good final answer should look like. ## Step-By-Step Workflow 1. State the job clearly: "Use the Custom product pages guide to help me with..." 2. Add context: audience, goal, offer, channel, source material, and constraints. 3. Ask the assistant to identify missing inputs before producing the final output. 4. Have the assistant follow the skill-specific guidance below. 5. Review the result against the final checklist and ask for revisions where needed. ## Skill-Specific Guidance - Check for `app-marketing-context.md` - Ask: **What traffic source(s)** will route to the CPP? (ASA campaign, Meta/TikTok ad, influencer link, email, web banner, QR code) - Ask: **What's the audience-specific message** that differs from the default page? - Ask: **How many variants** are realistic? (Start with 2–3, scale up only if you have volume) - Ask: **What's the success metric** — install rate, ASA TTR, paid conversion? - 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) - All traffic is organic — CPPs only show via URL - Volume is too low (<1,000 installs/mo from the source) to learn anything ## Decision Points And Nuance The original skill emphasizes: What CPPs Are (and Aren't), Initial Assessment, When CPPs Are Worth It, CPP Strategy Patterns, Anatomy of a CPP, Output Template, CPP + ASA: The Unlock, CPP + Social Ads, Measurement, Common Mistakes. Use these questions to steer the work: - What is the intended audience or buyer? - What source material must be preserved? - What should the assistant optimize for: clarity, persuasion, accuracy, speed, creativity, or conversion? - What examples represent the desired quality bar? - What should the assistant avoid? ## Common Mistakes - Don't multiply axes. Pick ONE axis and ship 2–4 CPPs along it. - | **Up to 10 screenshots** per device size | Different from default; must follow same Apple guidelines | ## Copy-And-Paste Prompt ```text Use the Custom product pages human guide. My goal: [Describe the business outcome] Audience: [Describe who this is for] Context and source material: [Paste notes, examples, links, or existing copy] Constraints: [Tone, length, channel, timeline, must-include items, must-avoid items] Before producing the final output, ask me for any missing information that would materially improve the result. ``` ## Final Checklist - [ ] The output matches the original goal. - [ ] The audience and context are reflected in the answer. - [ ] Important constraints and source material were preserved. - [ ] The assistant made the relevant decisions explicit. - [ ] The final artifact is ready to use, review, or hand to the next person. ## Source This guide was generated from the eronred/aso-skills skill entry for `custom-product-pages`. ## Source Skill Notes These notes preserve the nuance from the original skill. Use them as supporting reference when the workflow above feels too generic. # 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 | Pattern | Variant axis | Example | |---|---|---| | **Audience-led** | Persona | "for runners" CPP vs "for cyclists" CPP for a fitness app | | **Use-case-led** | Job-to-be-done | "for meditation" vs "for sleep" CPP for a wellness app | | **Feature-led** | Headline feature | "AI photo editor" vs "video editor" CPP for a multi-tool app | | **Channel-led** | Source matching | TikTok-style vertical-video-heavy CPP vs polished Meta CPP | | **Funnel-stage-led** | Cold vs warm | Brand-led for cold, social-proof-led for retargeting | | **Geo / language** | Market | Japan-specific CPP with local idiom (when full localization not feasible) | Don't multiply axes. Pick ONE axis and ship 2–4 CPPs along it. ## Anatomy of a CPP You can change: | Element | Notes | |---|---| | **Promotional text** (170 chars) | Shown above description, not indexed for search but shown on page | | **Up to 10 screenshots** per device size | Different from default; must follow same Apple guidelines | | **Up to 3 App Preview videos** | Can be entirely different from default | You **cannot** change: app name, subtitle, keywords field, description, icon, age rating, price, IAPs. ## Output Template When the user asks for a CPP plan: ``` CPP STRATEGY — DEFAULT PAGE BASELINE: Tap-through to install: X% (If unknown, run aso-audit first) VARIANTS TO BUILD: Variant 1: Source: URL slug: Headline angle: "" Promo text (170): "" Screenshot strategy: