One of the most powerful things about Userpilot is that it gives your team a way to trigger the right onboarding experience for the right persona at the right stage of the user journey.
Userpilot helps you deliver personalized and highly customizable product experiences based on what attributes your users possess, what they've done, and where they are in the application. Showing the users experiences that are relevant to them is important in driving higher user adoption and product engagement.
Once you've built an experience and you're ready to define your targeting, you can utilize the experience Settings page to configure the options on how to target a user
In many cases, you might want to install the Userpilot code snippet on different environments. This can be very helpful when you want to test the experience locally or on a staging domain before deploying it to production.
You can control Userpilot Experiences on any domain or subdomain where you've installed your Userpilot snippet
All domains (Default): Displays the experience anywhere the Userpilot script is installed
Specific domains: Displays the experience if the domain exactly matches the input string
Use wildcards to match dynamic domains
In many cases, your domain might have dynamic parts that change from user to user. A common use of a wildcard domain is with applications that use a personalized subdomain for each user or account.
You can easily use the Asterix symbol as a wildcard (*) to replace the part that is dynamic/changing. For example, to show the experience on 'name.userpilot.com' where the part 'name' is dynamic. You can set the domain to be the following:
Userpilot provides a wide set of operators to utilize the page targeting settings of the experience. This limits the experience only to show up on the correct URL within your application based on where the user is located.
Any page (Default): Displays the experience on any location a user is in within your application
Specific page: Displays the experience on a particular page(s) within your application depending on the URL path
What is a URL path?
URLs consist of the following parts:
https://staging.userpilot.com/dashboard/mailbox?Id=b3665070 \___/ \_____/\____________/\________________/ \_________/ | | | | | Protocol Subdomain Domain Path Query
URL path comes after the top-level domain (TLD) ' .com' or '.io' or any similar and before the query that starts with
URL path matching
To target an experience to appear on a specific path, you have a set of options that you can use:
- Starts with — experience will show on paths that start with the sub-string
- Contains — experience will show on paths that contain the input sub-string
- Ends with — experience will show on paths that end with the sub-string
- Equals — experience will show on paths that exactly matches the input string
- Matches regex — experience will show on paths that match the input regular expression
Working with unique URLs
Some cases might involve showing experiences on pages with dynamically changing URLs. To trigger the experience on the correct page, you can use 'Matches Regex' and use the Asterix symbol as a wildcard (*) to replace the part that is dynamic/changing ( you can learn more about it here).
Based on user or company data and product usage data, you might want to target experiences to a specific cohort of your users - e.g. you might want to target an experience based on the specific role of the user or you might want to target it only to users who didn't invite a teammate.
This section defines how you can differentiate which users are eligible to see your experience.
All users (Default): Any identified user is eligible to see the experience
Only me (useful for testing): All users who have access to your Userpilot account and have the chrome extension builder installed.
Specific segment: Use a previously created Segment that targets a specific group of users. This can be useful when you have a saved criterion that you want to use multiple times in several experiences.
Users that match specific conditions: Define a subset of your users by using a set of rules to dictate which users are eligible to see the experience. This includes user and company data that you are passing through your snippet, auto-properties that Userpilot automatically collects, events and actions that your users achieve in your app, and many more.