A tour can guide users through a workflow that spans pages. The Userorbit SDK must load on every page where the tour should run.
A tour can guide users through a workflow that spans pages. The Userorbit SDK must load on every page where the tour should run.
Plan the steps
Identify the starting page, each destination and the element that should be visible at each step. Keep navigation actions explicit.
In the visual builder, configure each step and its relevant page or target settings. Use the available button or navigation behavior to move to the next page.
Video is content within a supported step format; there is no separate Video Pointer step type.
Test page changes
Start from the first page as a demo user. Follow the same controls a real user will use and check that the next step appears on the destination page.
If a tooltip fails after navigation, confirm that its element exists and is visible, its target rule matches, and the SDK loads on that page. Test a direct page load as well as navigation inside a single-page application.
Review frequency
Use the tour's supported frequency settings: Show once, Show every time or Show N times. Do not configure an unsupported until-completed frequency or assume colon-style URL placeholders are recognized.