Sandbox / TestFlight / internal install exclusion before payback review
QA traffic pollutes small soft-launch cohorts. Checklist using AppsFlyer test-device and Protect360 notes.
Soft-launch payback on a few thousand installs dies when QA and TestFlight traffic stay in the cohort.
Checklist
- Register test devices — Protect360 FAQ notes unregistered test installs can be treated under fraud algorithms; register devices first.
- Filter non-production installs — Exclude TestFlight / internal tracks from the payback extract in BI.
- Sandbox purchases out — Sandbox IAP must not enter cash ROAS.
- Validation rules — Where useful, validation rules can block untargeted version/geo patterns.
- Recompute — After exclusions, re-freeze the soft-launch cohort before any scale decision.
Facts vs limits
| Fact | Limit |
|---|---|
| Test-device registration is documented for Protect360 | Apple TestFlight product page not required for the MMP control |
| Validation rules are configurable | Exact internal CID lists are studio-specific |
CSV.
