When custom product pages need their own MMP campaign mapping
AppsFlyer documents af_ios_store_cpp and store product page reporting; CPP traffic without mapping cannot be judged against creatives.
Custom product page traffic without campaign mapping cannot be judged. AppsFlyer documents redirects to Apple CPPs and Google CSLs via OneLink or single-platform links, including the af_ios_store_cpp parameter set to the App Store Connect CPP ID. Aggregated data is available by adding the store product page dimension; raw data records the parameter on clicks.
If UA assigns distinct CPPs per creative concept but MMP links omit af_ios_store_cpp (or the Play listing parameter), dashboards collapse those journeys into the default page and false “winners” appear.
Operator implication
- One CPP/CSL ID ↔ one MMP campaign or ad-set naming key.
- Add
af_ios_store_cpp(or Play listing redirect) before spend, not after. - QA clicks in raw data before reading CVR by page.
Note: AppsFlyer’s article still mentions historical Apple caps in places; confirm the live Apple 70 CPP ceiling on Apple’s own CPP page when auditing account limits. No advertiser account was inspected.
