MMP SKAN schema / postback field changes that affect F2P CV maps
Field renames and SKAN 4 columns break CV pipelines. Dated field card from AppsFlyer SKAN docs and Apple windows.
F2P conversion-value pipelines break quietly when MMP SKAN field names or decode CSV columns change under a live map.
What changed (documented)
AppsFlyer’s SKAN 4 bulletin lists report fields added for SKAN 4, including skad_postback_sequence_index (0/1/2), skad_coarse_conversion_value, skad_source_identifier, and skad_source_domain, and states you cannot revert after upgrading. SKAN CV decode specifies the decode CSV columns (conversion_value, coarse_conversion_value, event_name, revenue bounds, postback_sequence_index) and notes advertisers may change mappings. Apple’s multiple conversion windows doc restricts fine conversion-value to the first postback when the tier allows it.
Operator action
| Action | Why |
|---|---|
| Version-control the decode CSV | Maps change without a historic schema API |
| Join on sequence index | Window 2/3 are coarse-only |
| Diff field dictionaries after MMP releases | Renames break warehouse jobs |
| Re-read Apple tier rules after CV rewrite | Null fine CV is expected on low tiers |
Facts vs limits
| Fact | Limit |
|---|---|
| Named SKAN 4 fields are documented | Adjust/Singular field names may differ — re-check before multi-MMP |
| Map changes are allowed anytime | This is not a dated public postmortem of one studio’s rewrite |
CSV.
