Skip to main content
It works the same way across Tours, Callouts, and Messages — one shared mechanism, which is also why Targeting appears as a single tab in the nav rather than a per-content-type setting. Two independent layers apply together (a user must pass both)

Segments

A user must belong to at least one segment in the list to see the content (segments within the list use OR logic — any one match is enough). Leave it empty and the content shows to everyone. Segments are evaluated server-side, against both static membership (a manually assigned list of users) and dynamic membership (rule-based, auto-updating as users match or stop matching).
When a a piece of content does not have a segment set you will the following: “No segment targeting — shown to all users.”

Platform and Version

Content can also be scoped to specific platforms (iOS / Android / React Native) and to a minimum/maximum app version range — useful for rolling something out only to users who’ve updated, or excluding a platform entirely if something’s not ready there yet.
Platform/version scoping is confirmed in the schema but I haven’t seen it in either Audience tab screenshot — it may live under the “General” or another tab I haven’t checked yet.