SKAN for F2P: conversion value encode checklist for IAP milestones
Operator checklist for encoding F2P IAP milestones into SKAN conversion values across Apple’s documented windows and coarse/fine fields.
F2P milestones still get squeezed into coarse SKAN buckets. Apple’s SKAdNetwork overview and multiple conversion windows docs describe three windows (days 0–2, 3–7, 8–35), fine conversion values on eligible first postbacks, and coarse values (low / medium / high). Postback parameters may be omitted when privacy thresholds are not met (postback parameters).
Operator checklist
| Step | Pass criterion | Fail / hold |
|---|---|---|
| 1. Milestone list | IAP events ordered by economic meaning (tutorial complete, first purchase, cumulative revenue bands) | CV bits assigned to vanity events only |
| 2. Window map | Each milestone declared for window 1, 2 and/or 3 | One schema pasted into all windows |
| 3. Fine vs coarse | Fine 0–63 plan for window 1; coarse plan for later windows / lower tiers | Fine expected on postback 2/3 |
| 4. Lock policy | Explicit rule for `lockWindow` vs waiting for window end | Accidental early lock cutting revenue updates |
| 5. Null / missing CV | Dashboard treats absent conversion-value as unknown, not zero revenue | Nulls averaged as $0 |
| 6. MMP schema sync | MMP CV mapping export matches the engineering encode table | Two conflicting spreadsheets |
| 7. Observation vs inference | Schema dated with iOS / SKAN version tested | Undated “SKAN 4 best practice” slide |
Facts versus limits
| Field | Evidence |
|---|---|
| Three conversion windows | Apple multiple-windows doc |
| Fine vs coarse behaviour | Apple SKAdNetwork / postback parameter docs |
| Recommended revenue bit map | Not prescribed by Apple here — studio-specific |
Download the checklist CSV.
