Value sets
- Also called Value set, Value set ranges
- Updated November 14, 2026
A value set is a list of at least four price ranges, such as $10–$15 and $15–$20, that Meta uses to group app purchases when a campaign is measured through Apple's SKAdNetwork. Meta uses the ranges "to group and measure conversions when optimizing for value." You need one to use maximize value of conversions on iOS app campaigns measured that way.
How does Meta define a value set?
Meta's About value sets page:
A 'value set' is a requirement in Events Manager for maximize value of conversions in campaigns that use SKAdNetwork. It is made up of at least 4 distinct purchase ranges, each defined by minimum and maximum purchase values.
The page's example ranges are "$10-$15, $15-$20, $20-$25 and $25-$30", and Meta says that "Adding additional value set ranges may help make your measurements more precise."
When do you need a value set?
Only for app purchase events in your SKAdNetwork configuration. Meta: "Value sets are available for app purchase events that you prioritize in your SKAdNetwork configuration. You don't need to enable value sets for events sent through Aggregated Event Measurement."
| Measurement | Value set needed for value optimization? |
|---|---|
| iOS 14.5+ campaigns using SKAdNetwork | Yes: turn on maximize value of conversions in the SKAdNetwork configuration and enable a value set |
| Aggregated Event Measurement | No |
How many value set ranges can you use?
At least four, and they eat into a fixed budget of events. Meta: "Each range counts toward your app's event limit. (You can configure a maximum of 63 events per app)."
The counting has a twist: "if you configure a purchase event with 5 value set ranges, it will be counted as 5 events and not 6." The ranges replace the purchase event in the count; they don't add to it.
What are the rules for custom value set ranges?
If you customize your SKAdNetwork app events in Events Manager, you enter the ranges yourself. Meta's requirements:
- "A minimum of 4 ranges per event, event bundle and currency must be provided to create a value set."
- "Each range of purchase values in a value set must be consecutive and can't overlap." Meta's example runs $5–$6, $6–$7, $7–$8 and $8–$9.
- The same range can repeat across different events or event bundles, since each belongs to a different value set.
- "Custom value set ranges are only available for app events in your SKAdNetwork configuration."
Every range takes one of the 63 priority slots, so a value set "will take up at least 4 of those 63 Priority ID slots."
Does a value set change ROAS reporting?
It can. Meta says that for iOS 14+ campaigns on SKAdNetwork, it "may be able to report ROAS for events that occur on all iOS 14 devices if value optimization is turned on. If value optimization is not turned on, Meta may not be able to report ROAS for users who may not have provided ATT permission." With a value set and value optimization on, ROAS covers more of your iOS buyers.
What it means for your ads
- If you run iOS app campaigns measured through SKAdNetwork and want to optimize for purchase value, set up a value set first. Without one, Meta can't optimize for value there.
- Draw the ranges around your real prices. Ranges where nobody buys waste slots out of 63.
- Leave room for other events. Four ranges are the minimum, and each one is a slot.
- For web and app events through Aggregated Event Measurement, skip it.
Common mistakes
- Building ranges with gaps or overlaps. Meta requires them to be consecutive.
- Mixing currencies in one set. The minimum of four applies per currency.
- Treating value sets as a revenue report. They're buckets for optimization and measurement, not order values.
Sources
- About value sets — Meta Business Help Center (accessed November 14, 2026)
Meta revises these pages without notice, so check the source before setting up ranges.
Terrads makes each placement's file at its own size, so a value-optimized campaign has creative for every frame it runs in.