Check publication, targeting and the page where the tour should appear before changing the tour.
Check publication, targeting and the page where the tour should appear before changing the tour.
Check publication and schedule
Open the tour and confirm it is published. If it has a start or end date, check that the current time is within that period.
Check the SDK and workspace
Confirm the Userorbit SDK loads on the page and uses the workspace that contains the tour. Check the browser console and network panel for blocked requests or initialization errors.
If a Content Security Policy blocks a request, use the blocked URL and the SDK installation documentation to identify the required change. Do not broadly allow unrelated domains.
Check targeting and frequency
Review the tour's audience and start conditions. For an event-triggered tour, confirm your application sends the configured event for the test user.
Review the frequency: Show once, Show every time or Show N times. Check the repeat-after-dismissal option where available. Do not assume there is a recurring interval or a reset-history button.
If several experiences are eligible together, review delivery priority. Higher priority wins; zero is neutral.
Check the target page and element
Open the page where the step should appear. Confirm that the tooltip's target element exists and is visible. If the application changed, select the element again or update the targeting rule in the visual builder.
For a tour that crosses pages, check the destination and confirm the SDK also loads there.
Gather details for support
If the tour still does not appear, collect the tour ID, page URL, time of the test, test-user identity, relevant targeting settings, and browser console or network errors. Remove secrets and private user data before sharing screenshots.