Every tour and checklist has a Targeting tab. It answers two separate questions: who is allowed to see this, and where on your site it is allowed to run. Both have to pass before anything shows.
When it runs
How it starts sets whether the tour begins on its own once the targeting matches.
Starts at and Ends at are optional dates. Use them for anything tied to a launch or an event, so you do not have to remember to pause it by hand.
Frequency
Frequency decides how often one person can see the same tour.
Once per user — they see it a single time, finished or not.
Until completed — it comes back on later visits until they reach the end.
Every time it matches — it runs whenever the conditions are true.
Use Until completed for onboarding, where you actually want people to finish. Use Once per user for announcing something, where a second showing is just noise.
This setting is also the most common reason a tour "stops working" during testing: once you have seen a Once per user tour, it will not come back for you. Test in a private window.
Priority
If more than one tour could start for the same visitor on the same page, priority decides which one wins. Only one runs. If you have several tours live at once, set this deliberately rather than leaving it to chance.
Who sees it: User Segmentation
With no rules, every visitor the page rules match will see the tour. Click Add Segment to narrow it.
The rule builder matches on All or Any of the conditions you add. Each condition is a field, an operator and a value. You can group conditions together with Add Group when you need something like "on a paid plan, and either an admin or an owner".
The field list includes what we know about every visitor — User ID, User Name, User Email, First Seen, Last Seen, Country, State, Language, OS and Widget — plus every custom attribute you send us yourself when you identify the user in the widget. If you pass a plan name, a role or a signup date, you can target on them here.
That last part is worth planning for. The quality of your targeting is limited by what you send; if you are not passing plan or role today, you cannot segment on them today.
Load Segment reuses a segment you have already defined instead of rebuilding it, which is the better habit once you have more than a couple of tours.
Where it runs: Page Rules
With no rules, a tour can start on any page of your site. Click Add Rule to restrict it.
Each rule reads as a sentence. First choose Show when or Never show when — the second is for carving out exceptions, like running everywhere except your billing pages.
Then choose what to match on:
the path — everything after your domain, such as
/settings/billing. This is usually what you want.the full URL — the whole address including the domain and any query string.
Then the operator: matches any page, is exactly, starts with, ends with, contains, or matches the regex.
starts with is the one to reach for most of the time. A rule of "the path starts with /settings" covers every page in your settings area without listing them. Use is exactly when you really mean one page and nothing beneath it.
Finish your rules, or they are dropped
A rule you have started but not filled in is not saved. The panel warns you with a message like 1 rule still needs fixing — invalid rules are dropped, not saved, as in the screenshot above.
So an incomplete rule does not quietly block your tour; it disappears, and your tour ends up less restricted than you intended. Either finish the rule or delete it with the cross at the end of the row before you save.
How the two fit together
Segmentation and page rules are combined, not alternatives. A visitor sees the tour only if they match the segment and they are on a page the rules allow.
If a tour is not appearing, check them in that order: are you the right user, are you on the right page, and have you already used up your frequency.