Use a survey's Targeting tab to choose when it launches and who is eligible. Begin with a test survey and a synthetic user so you can verify the rules before publishing to customers.

Choose the launch condition

Open the survey editor and select Targeting. Under When should this survey launch?, choose manual launch or Auto start - When user triggers an event.

For an automatic launch, use Add event to select or create the event used by your application. With multiple selected events, Any launches when one selected event occurs; All makes the survey eligible when a selected event occurs and every selected event is present in the available user history. It does not require a particular order. Choose the rule that matches your intended journey.

For a code event, create the matching action first and use its exact key after SDK initialization:

await userorbit.track("purchase_completed");
JavaScript

Here purchase_completed is an example key, not a built-in event. The event should run after the application's purchase succeeds. Do not assume arbitrary fields passed to track() become Analytics properties. See event tracking.

Set frequency and delay

The editor offers Show once and Show every time. Automatic survey delivery still excludes a survey already completed or dismissed by that user, including when Show every time is selected. Do not use that setting as a promise to resurvey someone after completion or dismissal. Verify the repeat behavior with synthetic users in your installed version.

Use Add a delay before showing the survey if it should wait after the trigger. During testing, allow the configured delay to elapse.

Choose the audience

Use All users, a saved segment, or the available specific-user conditions to define the intended audience. If a condition depends on a user attribute, verify that the application sends the attribute with the expected value before the launch event occurs.

Use the available audience and eligibility controls for your survey's rules. Preview the questions and design, save the configuration, and publish when ready. An editor preview alone does not prove that a real user meets the delivery conditions.

Verify inclusion and exclusion

Test with one synthetic user who matches the audience and another who does not. Trigger the selected event in the actual application, wait for any delay and confirm the intended result. Repeat with the same user, including after completion and dismissal, to check the delivery behavior. If using multiple events, verify the selected Any/All behavior too.

Troubleshoot a survey that does not appear

Check What to verify
Installation and workspace The SDK initializes using the intended workspace/widget configuration.
Publishing state The survey intended for live delivery is published.
Launch condition The survey is configured for the way you are trying to launch it. A manual launch setting is different from an automatic event trigger.
Event The matching code action exists, the exact key is used, and the event actually occurs after initialization.
Audience The current user has the required attributes or segment membership.
Previous completion or dismissal Automatic delivery excludes a survey already completed or dismissed by the user. Test with another synthetic user; changing frequency alone does not remove that exclusion.
Delay and delivery eligibility Wait for the configured delay and check the additional eligibility rules configured for this survey.
Browser errors Inspect the first failing SDK request and Console error using SDK troubleshooting.

When asking for help, include the survey ID, workspace, test time, expected trigger, sanitized audience conditions and the result for your test users. Do not include customer response contents or private credentials.

Was this helpful?