The common requirement when implementing product tours is to target one to a specific user group - for example:
- Welcome tour to logged-in users
- Feature adoption tour to users with a specific role
- Product tour to users with specific language selection
In general, there are two approaches to ensure targeting to a specific user group - user tagging-based and screen-based.
User tagging approach
This approach expects you to share user tags (such as "newuser", "admin", "french", depending on your context) when calling the Usetiful script from your page. The product tours can then be targeted towards specific user tag.
For example:
- Tour "Welcome to new users" to be shown only if a user contains tag "newuser"
- Tour "English walkthrough" to be shown only if a user contains tag "english"
- Tour "Training for admins" to be shown only if a user contains tag "admin"
For all these examples, set condition "User tag is" with given tag value.
Single user can have multiple tags, allowing for targeting according to multiple aspects at the same time.
Find out more how to segment users using user tags here.
Screen-based approach
The simplest solution is often the best. This approach is available in Usetiful Free and Usetiful Plus.
The screen-based approach targets tours based on screen conditions, such as "Element exists" or "Element text contains". No personal information about users is transferred to Usetiful, therefore it is GDPR-friendly.
- Welcome tour to logged-in users
We target an element that is shown to logged-in users only. This is usually the "profile" element or "Log out" button.
Profile element from Atlassian JIRA
Using the condition "Element exist" (i.e. Profile element exist) or "Element text contains" (i.e. button contains text "Log out") in the tour targeting we can ensure the tour is shown to relevant users only.
- Tour to users with a specific role
The first question to ask is - why do we want to target users with a specific role?
If it is because a feature we want to introduce is available to the specific role only, we can simply target the tour to availability of that feature. For example, if only "admin" role sees feature "Settings", we can target the tour (using condition "Element exist" or "Element text contains") on a Settings button.
If the reason to target users with a specific role is deeper, for example, caused by the internal logic of your application, it is possible to target the user group directly. Sometimes this is available on-screen, next to the profile element.
- Target specific language
There are two usual ways to target a specific language - either target URL (when language is included) or target language selector.
The language selector can be targeted with condition "Element text contains" or "Element value contains".
Example of the language selector
If your page includes the language version in the URL, you can simply target the tour using the condition "URL contains" (for example, URL contains "us-en").