← All tools
Measurement utility · iOS attribution

SKAN conversion value schema builder.

Sixty-four values is not much. Spend them where they separate valuable users — then export the schema your MMP can load.

Choose how many of the six fine-value bits go to events, set the revenue scale, and name your events. The table updates as you go.

Your numbers

Revenue buckets——
Smallest step—Resolution at the low end
Coarse mapping—Low / medium / high

Encoding: fine value = event flags × buckets + revenue bucket. Event flags are a bitmask (event 1 = 1, event 2 = 2, event 3 = 4). Bucket 0 means no revenue yet.

Fine valueEventsRevenue ≥Revenue <Coarse
How it's calculated

The method, in plain terms.

  1. Fine values 0–63 = 6 bits
  2. Revenue buckets use the value range; optional event flags take the remaining bits
  3. Coarse values: low / medium / high thresholds on the same revenue scale
Worked example

Reserving 2 bits for events (tutorial complete, first ad watched) leaves 16 revenue buckets. With a $20 ceiling on a geometric scale, bucket edges start at a few cents and widen towards $20, putting resolution where most early revenue sits.

Defaults on this page are illustrative starting points, not benchmarks for your game. Replace them with your own numbers.

Terms on this page

SKAdNetwork · Conversion value · AdAttributionKit

Embed this calculator

Free to embed on your blog, wiki or course page with the credit link intact.

FAQ

Common questions.

What is a SKAdNetwork conversion value?

A number an iOS app sets to summarise a new user’s early behaviour for privacy-preserving attribution postbacks. Fine values run from 0 to 63 (six bits); coarse values are low, medium or high and apply to later postbacks or to campaigns below Apple’s privacy thresholds.

Should the schema encode revenue or events?

Revenue when early revenue predicts value well — usually for IAP-heavy or ad-monetized games with meaningful day-0/1 revenue. Events when early revenue is sparse but a behaviour (tutorial complete, level 10, first ad watched) predicts retention and payment. Many schemas combine both: a few bits for events, the rest for revenue buckets.

Why geometric revenue buckets?

Early revenue is concentrated in small amounts with a long tail. Geometric buckets put more resolution where most users sit and still separate the high spenders, instead of wasting half the buckets on ranges almost nobody reaches.

Does this work for AdAttributionKit?

AdAttributionKit uses the same conversion-value concepts (fine and coarse values, postback windows), so the same schema design applies. Confirm current window and threshold details in Apple’s documentation and with your MMP before deploying.

How do I use the output?

Copy the CSV and use it as the specification for your MMP’s conversion value configuration or your own SDK logic. Validate against a sample of real day-0/1 user data to check bucket occupancy before going live.

Calculator by The Game Scientist ↗