Choose who sees an experience and when
Combine audience rules, triggers, platforms, and frequency controls.
Last updated 9 September 2026
On this page
Separate who from when
The audience describes the people eligible for an experience. The trigger describes the moment it should appear. A paying customer might match the audience all week but only receive a route-saving question when the route_saved event occurs.
Set up Target
Select the delivery platforms your experience supports. Web must be enabled for the app before it can be selected.
Choose Everybody or Send only to, then add criteria if you need a narrower audience.
Use All when every criterion must match, or Any when one matching criterion is enough.
Choose the trigger and configure its event, property filters, or occurrence options where relevant.
Set delay, campaign dates, and frequency limits to suit the experience.
Use the estimate correctly
The matching audience count is a current estimate, not a guaranteed send count. Consent, device support, timing, frequency limits, and actual trigger activity can still affect delivery. Anonymous and identified SDK identities can both participate.
Try a specific test case
Write down why one test user should qualify, then check each condition against that user’s available data. For example: the right platform, plan property, event name, and event properties. Trigger it in the connected product and inspect the result. If it does not appear, check eligibility before widening the audience.