SKAN conversion values for an IAP-heavy F2P schema
Analysis
By UA Ledger staff — 1 min read

Checklist mapping IAP-heavy F2P events into SKAN 4 conversion windows using Apple’s multiple-conversion-windows documentation.
Apple’s multiple conversion windows documentation defines windows 0–2, 3–7 and 8–35 days from first launch, with optional lockWindow, fine values primarily for the first postback and coarse values for later windows. SKAdNetwork describes conversion-value updates as the advertised app’s responsibility.
Operator checklist
- Map IAP events to windows: tutorial/first purchase → window 1; repeat purchase → window 2/3.
- Reserve fine values (0–63) for early revenue/quality bits; plan coarse low/medium/high for later windows.
- Decide lock policy explicitly (faster postback vs waiting for end-of-window).
- Do not crowd every signal into day 0 without recording what you sacrificed.
- Align MMP schema to Apple windows, not invent windows.
- Crowd anonymity: Accept null/coarse outcomes; do not invent fine values Apple withheld.
- Re-read StoreKit docs when schema changes.
Limits
Schema design is studio choice; Apple does not mandate an IAP bit layout.
Research checked 20 September 2026. Local draft; human editorial review pending. No CMS write performed.
Featured
Related posts
measurement
·2 min read
When to freeze a cohort for payback review (and when not to)
measurement
media buying
·1 min read
Using predicted LTV in bids: disclosure checklist for the UA team
measurement
media buying
·1 min read
Blended ROAS targets that hide channel failure in F2P portfolios
measurement
·1 min read
Web-shop purchaser quality vs store IAP purchaser quality
More from the Measurement desk
measurement
·2 min read
Airbridge adds Amazon Ads as an app measurement channel
measurement
·1 min read
Web-shop attributed revenue in MMP vs payment-provider settlements
measurement
media buying
·2 min read
Web-shop LTV with VAT-inclusive prices versus store net proceeds (labelled synthetic)
measurement
media buying
·1 min read