Before you can start creating flows, you’ll need to install Usertour.js in your web application. Once that’s done, you’re ready to create your first flow!
Make your flows look and feel just right for your application. With themes, you can customize colors, typography, and overall styling to match your brand.
Triggers let you create smart flows with “if this, then that” rules. Before showing each step, if a trigger is active, it’ll run its logic first. You can:
Add multiple triggers to a step
Create branching flows
Skip steps based on conditions
A trigger can have the following conditions:
User attribute - Execute the trigger’s action when a user possesses specific attributes, enabling personalized flow progression.
Current page is - Execute the trigger’s action when users navigate to a designated page, ensuring context-aware flow delivery.
Element is present/clicked/disabled - Execute the trigger’s action based on UI element states. Particularly useful for handling asynchronous content loading scenarios.
Text input value is - Execute the trigger’s action when users enter specific values in designated input fields, enabling precise form-based flow control.
User fills in input - Execute the trigger’s action upon any user input in specified fields, facilitating real-time flow progression.
Current time - Execute the trigger’s action at designated times, allowing for time-sensitive content delivery within specific time periods.
Best Practice: Add triggers to visible steps to prevent users from getting stuck.
Once you’ve set up your flow, you’ll need to know how to start it for your users. For the full details on starting flows, check out the Starting Flow/Checklist Guide.
Remember to install Usertour.js in your application to start flows for your users.
Users can end a flow anytime by clicking the X-button in the top-right corner of modals and tooltips. While you can disable this button in advanced settings, we recommend keeping it enabled. You can add Dismiss actions to buttons, tooltip target clicks, survey questions, and step triggers. When starting a new flow, the current one will automatically end. For other actions like page navigation, you’ll need to add a Dismiss action yourself.On the last step of a flow, we recommend adding a Dismiss action to give users a clear way to end the flow. If you use Start a flow to begin another flow, the current one will automatically end. This automatic ending doesn’t happen with other actions like Navigate to page - you’ll need to add a Dismiss action yourself.Make sure your flow is properly dismissed (or hidden using temporarily hide), as an undismissed flow will prevent other flows from starting.
Currently, flows have a 24-hour session lifecycle. This prevents flows from getting stuck undismissed and blocking other flows permanently. In the future, you’ll be able to configure this duration through the Usertour.js API.
Flow completion is different from dismissal. A flow is complete when users reach the completion step, which is automatically set as the last step. If you want the flow to complete only after a specific button click on the last step, add a hidden step after the button step with an unconditional trigger and Dismiss action.