SKAN conversion values for an IAP-heavy F2P schema

Editorial collage hero: checklist-skan-conversion-for-iap-f2p

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

  1. Map IAP events to windows: tutorial/first purchase → window 1; repeat purchase → window 2/3.
  2. Reserve fine values (0–63) for early revenue/quality bits; plan coarse low/medium/high for later windows.
  3. Decide lock policy explicitly (faster postback vs waiting for end-of-window).
  4. Do not crowd every signal into day 0 without recording what you sacrificed.
  5. Align MMP schema to Apple windows, not invent windows.
  6. Crowd anonymity: Accept null/coarse outcomes; do not invent fine values Apple withheld.
  7. Re-read StoreKit docs when schema changes.

Limits

Schema design is studio choice; Apple does not mandate an IAP bit layout.

Download the evidence table.

Related posts

Airbridge adds Amazon Ads as an app measurement channel

measurement

·

3 min read

Airbridge adds Amazon Ads as an app measurement channel

When to freeze a cohort for payback review (and when not to)

measurement

·

2 min read

When to freeze a cohort for payback review (and when not to)

Using predicted LTV in bids: disclosure checklist for the UA team

measurement

media buying

·

1 min read

Using predicted LTV in bids: disclosure checklist for the UA team