AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Custom Product Pages

skill-eronred-aso-skills-custom-product-pages · by Eronred

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-speci…

No reviews yet
0 installs
4 views
0.0% view→install

Install

$ agentstack add skill-eronred-aso-skills-custom-product-pages

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-eronred-aso-skills-custom-product-pages)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Custom Product Pages? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

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 (

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: Preview video: Hypothesis: Success metric: install rate ≥ baseline + X%

Variant 2: ...

REVIEW + LAUNCH PLAN:

  • Submit to App Store Connect (1-3 day review)
  • Wire URL into campaign
  • Minimum 14 days of data before judging
  • Monitor in App Store Connect → Analytics → Custom Product Pages

KILL CRITERIA:


## CPP + ASA: The Unlock

The biggest CPP use case is **ASA Custom Product Pages**. In Apple Search Ads:

1. Create your CPP in App Store Connect first
2. In ASA → Ad Group → Creative Sets, **assign the CPP URL** to the ad group
3. Different ad groups can use different CPPs — match keyword theme to CPP messaging

Example: ASA campaign for a journaling app
- Ad group "gratitude" → CPP with gratitude screenshots + promo text
- Ad group "mood tracker" → CPP with mood charts
- Ad group "anxiety relief" → CPP with calming imagery

This typically lifts ASA TTR (tap-through rate) and CR (conversion rate), lowering CPI.

## CPP + Social Ads

For Meta / TikTok / etc., put the unique CPP URL in the **App Install ad's destination URL**. Different ad sets get different CPPs.

Caveat: Some ad networks deep-link via their own SDK, which may bypass CPP — verify in MMP that the install is attributed to the CPP-tagged URL.

## Measurement

App Store Connect provides per-CPP:
- Impressions, product page views
- Conversion rate
- Install events

Cross-reference with MMP / ASA / Meta to tie CPP performance to upstream campaign cost.

**Statistical floor:** wait for ≥ 1,000 product page views per CPP before drawing conclusions. With low volume, signal is noise.

## Common Mistakes

- Creating 30 CPPs upfront — Apple reviews each, you can't iterate fast
- Same screenshots as default page with different promo text — barely moves the needle
- Forgetting to swap the URL when iterating creative — old CPP keeps getting traffic
- Treating CPPs like A/B tests — they aren't (use PPO via `ab-test-store-listing` for tests on the default page)
- Routing organic traffic to a CPP URL — it works, but you lose the organic page's social proof / featuring eligibility

## Cross-Skill Handoffs

- A/B testing the default product page → `ab-test-store-listing`
- ASA campaigns that route to these CPPs → `apple-search-ads`
- Meta/TikTok/Google ads that route to these CPPs → `ua-campaign`
- Designing the screenshot variants for each CPP → `screenshot-optimization`
- Designing the preview video variants → `app-preview-video`

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [Eronred](https://github.com/Eronred)
- **Source:** [Eronred/aso-skills](https://github.com/Eronred/aso-skills)
- **License:** MIT
- **Homepage:** https://appeeky.com/

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.