Target a checklist to the right users

Use a checklist's Targeting settings to choose who can receive it and how it starts.

Choose the audience

Select the relevant audience option and configure its conditions. Use attributes and events that your application actually sends to Userorbit.

Choose the start behavior

Choose a manual start or Auto start – When user triggers an event. For automatic starts, configure the matching event conditions.

Choose Show once or Show every time according to the intended workflow.

Set delivery priority

Higher-priority checklists win within the embedded delivery group. Zero is neutral. Priority does not override audience or trigger requirements.

Test eligibility

Use a demo user with known attributes. Trigger the expected event and confirm that the checklist appears. Test a user who should not qualify as well.

If it does not appear, check publication, SDK initialization, identity, audience conditions, trigger events and frequency.

Do not depend on an undocumented Preview as user button or debug panel. Confirm the behavior in the application and inspect the tracking data you send.

For more detailed audience rules, see Combine targeting conditions for in-app experiences.