Stack · Published 2025-02-13 · 2 min read
Custom Product Pages in the App Store
Or CPP for short.
The idea
In the App Store you can create several store listings. Each listing gets its own URL. The key part: Apple collects download and proceeds statistics broken down by CPP.
Why does that matter? Because it lets you track installs and revenue precisely. The user followed a URL, downloaded the app, made a purchase — and Apple told us all of it.
So install tracking on Apple's side is 100%.
Ad networks. Apple Search Ads: not especially important here, since Apple already tracks it perfectly well.
Google Ads
- UAC
Not supported. My guess is that Google sells Android and has no wish to actively push traffic to a competitor.
- Web2App
You simply put the CPP into the Final URL and track 100% of the traffic.
Meta
- Aggregated Event Management
Supported. Campaigns have a dedicated Custom Product Page field.
- Web2App
Also supported. You redirect to the Custom Store Page either directly or through an MMP redirect.
IMPORTANT: a CPP will not affect campaign performance in any way. Yes, it gets tracked on Apple's side, but the ad networks know nothing about it.
MMPs. It is important to understand that even though Apple sees everything, MMPs have no access to that data. Apple tracks 100% of the traffic, but only some percentage of it gets attributed inside the MMP.
- AppsFlyer
- Web2App Google Ads
Use the AppsFlyer Direct Link and put it into the tracking template.
- Web2App Meta
Redirect through OneLink.
- Adjust
- Web2App Google Ads
Put the CPP URL into the Final URL.
- Web2App Meta
You configure the redirect when you set up a new partner.
Conclusion
Since CPPs affect neither attribution nor the data in your MMP, using them day to day is not particularly convenient. But it is useful to reconcile Apple against your MMP and ad networks from time to time, to check the quality of your models and predictions.