> Site index: https://usehardal.com/llms.txt
> Every content route also serves markdown at <url>.md

# What Is a Conversion Value?

A SKAdNetwork conversion value is a fine or coarse code an iOS app sets after an install. Apple may return it later, and only when the privacy tier allows it.

Source: https://usehardal.com/glossary/conversion-value

---

A conversion value, in Apple's install attribution frameworks, is a small code the advertised app sets after an install to describe what happened next. SKAdNetwork (SKAN) and AdAttributionKit send that code on a delayed, signed postback. The postback does not include a user or device identifier, and it does not include a list of events.

The code is a summary you design. Apple decides whether a given postback is allowed to carry it.

## How do fine values, coarse values, and the lock window work?

SKAN 4, available from iOS 16.1, measures three conversion windows and can send up to three postbacks.

| Window | What it can report |
| --- | --- |
| Days 0 to 2 | A fine value from 0 to 63, or a coarse value |
| Days 3 to 7 | A coarse value only: low, medium, or high |
| Days 8 to 35 | A coarse value only: low, medium, or high |

The app updates the value by calling `SKAdNetwork.updatePostbackConversionValue` with a fine integer, a `coarseValue` of `.low`, `.medium`, or `.high`, and a `lockWindow` flag. The postback fields are `conversion-value`, `coarse-conversion-value`, and `postback-sequence-index` (`0`, `1`, or `2`).

`lockWindow: true` ends that window early. Apple then starts the postback timer. Delivery is still delayed. Apple documents a random delay of 24 to 48 hours after the first window, and 24 to 144 hours after the later windows. Locking does not remove the delay.

Crowd anonymity decides the detail. At lower tiers Apple can withhold the conversion value and shorten the `source-identifier`. Tier 0 does not include a conversion value, and only the first postback is sent. Fine values are a first-postback field. The [crowd anonymity](https://usehardal.com/glossary/crowd-anonymity) page covers the tiers.

AdAttributionKit is Apple's current framework for app ad campaigns. The matching call is `Postback.updateConversionValue` with a fine value, a `coarseConversionValue`, and `lockPostback`. When impressions from both frameworks qualify, Apple picks one winner. An app that supports both should update both.

## A concrete example

A subscription app maps the 64 fine values before launch, and gives every range a coarse twin.

- Fine `0` means the app opened and nothing else qualified. Coarse: `low`.
- Fine `3` means the person finished registration in the first window. Coarse: `medium`.
- Fine `20` means a purchase event fired in the first window. Coarse: `high`.

On first open the app calls `updatePostbackConversionValue(0, coarseValue: .low, lockWindow: false)`. After registration it updates to `3` and `.medium`. If a purchase happens on day 1, it updates to `20`, `.high`, and may set `lockWindow: true` so the first postback can be prepared without waiting for the end of day 2.

The postback that arrives later might contain only `coarse-conversion-value=high` and a two-digit `source-identifier`. The fine value `20` is absent because the tier did not allow it. Your report should keep the coarse result, not replace the missing fine value with `0`. Zero is a mapped state in this scheme, not a synonym for "field omitted."

## What are the limits?

Six bits cannot hold an open-ended price. Teams encode events or revenue bands, then interpret those bands in aggregate. A fine value is not a receipt and not a person-level path.

The second and third postbacks never carry a fine value. If the business question needs day-30 detail, the coarse labels have to mean something on their own.

Apple does not publish a fixed install count that unlocks a tier. Splitting campaigns into many source-identifier values can drop a campaign into a lower tier and strip the fine value. Null is a privacy result until the integration has been checked.

SKAN and AdAttributionKit attribute one winning impression. They do not describe the ads that came before it. A conversion value also says nothing about Android, web, or opted-in measurement you run separately.

## How Hardal handles it

The app still calls Apple's update API. Hardal does not set the crowd anonymity tier and does not fill in a fine value Apple withheld. Hardal keeps the postback you receive next to the first-party app events you send, so a coarse `high` can be read beside the purchases your own pipeline recorded for that cohort.

Map the values before you spend, and do not turn a missing `conversion-value` into a zero. The [SKAdNetwork guide](https://usehardal.com/skadnetwork-skan-guide) has the postback fields, windows, and tier table in one place.

**Related terms:** [SKAdNetwork](https://usehardal.com/glossary/skadnetwork), [Crowd anonymity](https://usehardal.com/glossary/crowd-anonymity), [App Tracking Transparency](https://usehardal.com/glossary/app-tracking-transparency), [Web-to-app](https://usehardal.com/glossary/web-to-app)
