When creating a new product tour, smart tips or a checklist it is crucial to set up the right targeting to ensure the content is shown in the right context to the right audience. Usetiful provides an easy targeting setup, enriched with advanced and specific options.
Page targeting can be set up within the Settings section of a new or existing tour/smart tips group or checklist.
A content (e.g. a tour) can be displayed on any page where the Usetiful code is embedded. Page targeting allows you to narrow down the availability to certain pages, users, devices, browsers and more.
If more than one condition is defined, you can select when the content shows up if all or any conditions are matched.
|When this condition is set, Usetiful checks whether the page URL address contains the text value. You can enter the full address (such as 'https://yourpage.com/path') or just a relative path (such as '/path/index.html').|
URL does not contain
|URL equals||Specify the URL where the tour must show. This field uses exact match logic, so please specify precise URL with https://www|
|URL regular expression||If you need the tour to display on multiple pages you can enter the argument as a regular expression.|
Examples of regular expressions can be found here.
|Referrer URL equals||Referrer URL is the previous page address the user visited, or in other words the page from where the user arrives at the current page|
|Referrer URL contains|
NEW Tour-relative conditions:
|Tour state is||This condition makes it possible to automatically start a tour if a different tour has not been started yet or has been closed.|
The following options are available:
- Closed: if at any point in the tour the user clicks the "Close" button or reaches the last step of the specific tour - the tour is considered as closed.
- Not started - if the specified tour has never been opened before.
Based on the conditions of a specific tour above, you can automatically start a different tour.
|Tag value||When this condition is set, the tour will show only if the given user has the expected tag. You can check whether the value is equal, not equal, contains or does not contain, is lower or higher for the specified tag. Find out more about how to segment users using tags here.|
|Language is||Checks for the preferred language of the visitor's browser. Read about this feature in more detail here.|
Refer to HTML ISO language codes directory here.
|Browser is||Allows starting the tour only if the page is opened in the selected browser (e.g. Chrome, Opera, etc). Select a browser from the list.|
|Page content-based conditions:|
The tour will display only on pages that contain a specific HTML element. This allows you to target tours to users that have permission to see specific features.
In a similar way, you can use the negative condition 'Element doesn't exist'.
|Element doesn't exist||Opposite of "Element exists" - target pages on which the specified element is not present.|
|Element text contains||In addition to the previous condition type, you can also check the text content of the select element. This is especially handy to detect different page languages or specific values displayed on a page.|
|Element attribute contains||With this condition, you can test the content of specific attributes on a given element.|
|Device type is||You can target your tours to mobile, tablet or desktop devices.|
|Operating system is||This option helps display the tour only if the visitor is using the specified OS. For example, a tour can be targeted only on users who are opening the page using Mac OS.|
Select a desired OS from the list.
|Local storage value is||Specify a key / value pair, which will ensure the tour is only displayed to users who have this local storage pair item in their browser. This is helpful to target tours based on users' previous interactions with your application or with other applications.|
Combining mentioned conditions in the Page targeting section is possible - if combined, your content will be displayed when ALL or ANY defined conditions match. See the following examples.
The first targeting definition ensures that the product tour will display on a page with 'domain.com' in the URL and when the page contains the element with selector '#element-1'.
The second example will target the tour to 2 different subdomains, so on both will the tour be available.
Combining conditions of ALL and ANY in the Page targeting section is possible - if combined, your content will be displayed when ALL and ANY defined conditions match. See the following example.
The targeting definition ensures that the tour will display when the operating system is Windows and the page contains the element with selector '#element-1', and on 2 different subdomains.