Pages & screens
Control which URLs or app screens a tour loads on, with exact paths, prefixes and wildcards.
Each walkthrough loads on the pages (web) or screens (apps) that match its page path.
Web: page path patterns
Enter a path only — not the full URL. If you paste a full URL, the domain is stripped for you.
| Pattern | Matches | Doesn’t match |
|---|---|---|
/ | the homepage only | /pricing |
/dashboard | exactly /dashboard | /dashboard/settings |
/dashboard/* | /dashboard/, /dashboard/settings, /dashboard/a/b | /dashboard |
/blog* | /blog, /blog/post, /blogroll | /news |
* | every page on the site | — |
- Matching is on the URL path only. Query strings (
?tab=2) and hashes (#top) are ignored. - A trailing
*means “starts with”. A*anywhere else is treated literally. - Trailing slashes are removed when you save, so
/pricing/becomes/pricing. - Paths are case-sensitive.
* together with element conditions, so the tour only activates where its elements exist.Apps: screen identifiers
In app sites the field is called Screen. Enter the identifier you registered in code — e.g. home for a screen marked with .ttPage("home") — or * to show on every screen. Leaving it empty means *.
Click Capture from device to fill it in by navigating to the screen in your running app. See Visual Inspector.
When several tours match
Every active tour whose pattern matches is a candidate. Only one shows at a time: the oldest tour whose display conditions currently pass. See Running several tours on one page.