Sandbox / TestFlight / internal install exclusion before payback review
Analysis
By UA Ledger staff — 1 min read
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.
Draft prepared 20 September 2026. Local expansion-500 file; human editorial review pending. No CMS write.
Featured
Related posts
measurement
platforms
·1 min read
When to turn rewarded ads off for payers (and how to measure the loss)
measurement
platforms
·1 min read
When custom product pages need their own MMP campaign mapping
measurement
platforms
·1 min read
Season pass refund rate versus standard IAP refund rate
measurement
platforms
·1 min read
Pre-reg cohort quality vs post-launch paid cohort quality
More from the Measurement desk
measurement
platforms
·2 min read
AppLovin Ad Review drops user-level journeys for aggregate-only reporting
measurement
platforms
·2 min read
Apple adds an EU alternative ATT prompt from iOS 27.2 — mandatory in five markets
measurement
platforms
·1 min read
Pity-adjusted expected value versus player-facing banner claims
measurement
platforms
·1 min read