SKAN conversion-value schema checklist for hybrid IAP+IAA titles

Editorial collage hero: checklist-skan-cv-schema-hybrid-iap-iaa

Operator checklist for encoding IAP and ad revenue into SKAN 4 fine and coarse values without treating the schema as Apple revenue.

Hybrid IAP+IAA titles often leave ad revenue under-encoded in SKAN conversion values. Apple documents the bit budget and windows; the studio owns the schema. This checklist is an operator gate, not a recommended industry map.

What Apple actually returns

Receiving postbacks in multiple conversion windows states that SKAdNetwork 4 supports three windows after first launch: days 0–2, 3–7, and 8–35. Fine conversion-value (0–63) is available only on the first postback when privacy tiers allow it. Coarse values are the strings low, medium, and high. Postbacks may contain either fine or coarse conversion value, not both. Windows 2 and 3 carry coarse values only.

What an MMP schema tool adds

AppsFlyer SKAN Conversion Studio documents that Window 1 fine CV is limited to 64 values, while Windows 1–3 coarse CVs are low/medium/high. Revenue measurement can use overall revenue via af_skad_revenue (including ad revenue when relevant) or selected in-app revenue events. That is an MMP encoding option, not Apple exporting IAA or IAP cash.

Operator checklist

GatePass conditionFail / hold
Window map postedDocument which events update CV in W1 / W2 / W3Undated “SKAN map” slide only
Fine budget explicitBit or range allocation for IAP vs IAA vs engagement is written“Revenue” without IAP/IAA split
Coarse meaning writtenlow/medium/high defined for each windowCoarse left to vendor default without review
IAA path namedAd-revenue event path is in overall revenue or a dedicated streamIAA assumed “in ROAS” with no CV path
IAP path namedPurchase event and currency normalisation rules listedStore proceeds treated as CV units
Overlap ruleFinance and UA agree whether overall revenue double-counts IAP+IAASilent sum of IAP CV + IAA CV
Partner mappingNetwork postback event maps match the studio schemaSchema saved; partners unmapped
Null / tier planBid and reporting treat missing fine CV as unknown, not zero revenueNull CV = $0 in live bids

Facts versus limits

Fact (sourced)Limit
Three SKAN 4 windows; fine primarily on first postbackApple does not publish a hybrid-game CV recipe
Coarse values are low/medium/high stringsMeaning is advertiser-defined
MMP tools can encode overall revenue including ad revenueEncoded value ≠ finance net proceeds

Download the checklist CSV. Cross-read SKAN versus MMP revenue bridge.

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