<b>Your SKAdNetwork conversion-value schema is probably leaking money</b>

<b>Your SKAdNetwork conversion-value schema is probably leaking money</b>
Most teams map all 64 conversion values to revenue buckets and call it done. That wastes the single most rationed signal Apple gives you.

The better pattern: split the 6-bit space. Reserve coarse-grained engagement (session count, tutorial complete) in the low bits, revenue tiers in the high bits. You decode both from one integer.

✓ Engagement bits survive the privacy threshold more often than revenue bits
✓ Lets you optimize for early funnel when D0 purchases are too sparse
✗ Requires a custom postback decoder — no MMP does this split cleanly out of the box
✗ Burns your measurement window planning on encoding logic

The trap: chasing fine revenue granularity when 70% of your sources never cross the threshold to report a non-null value anyway.

<b>Verdict:</b> use bit-splitting if installs/source/day is low; skip it if you run mega-sources with reliable threshold-crossing.
<b>Best for:</b> UA managers on fragmented iOS source mixes.