The experience building process starts with creating the content and design, then testing what you built to ensure that it looks like you intend, and it ends with promoting the experience to show live in your product.
Before setting an Experience to show live for your end-users, it is important to review what you built and make sure that the experience looks and behaves exactly as you expect. To help you utilize this, Userpilot provides you with two approaches:
- Preview Mode – Review the experience content and test how It looks & behaves while in the building process within the Userpilot builder.
- Test Mode – Interact with your experience as an end-user while it is live in your product.
Preview is a tool that is available while building your steps in the Userpilot builder and is utilized to test how an experience would look and behave for your end-users. To enter preview mode, click the ' Preview' button in the bottom bar.
Previewing an experience can be great for many things:
- You can quickly walk through the experience as an end-user would
- Check that the steps of the experience appear on the right page(s)
- Interact with form fields, redirects, buttons, etc.
- Check step interaction behaviors such as hover or click
- Helps in getting feedback from your teammates who have access to your Userpilot account and have the builder installed
Notes on Preview mode
- Preview mode only requires installing the Userpilot builder and it doesn't require installing the Userpilot script on your product.
- Preview mode doesn't check if the experience obeys the specified targeting and triggering settings - e.g. you can't test if the experience would only show up after the occurrence of a custom event.
After building your experience and previewing it to make sure it looks and behaves as expected, you might also want to test if the experience will be triggered properly in the correct situation for the correct segment. You can test it in a live environment in your product before deploying it for your end-users.
Testing the experience live as an end-user can be great for many things:
- Test the experience live as an end-user outside the Userpilot builder
- Ensure that the experience obeys the specified targeting settings - e.g. the experience shows only for new sign-ups
- Ensure that the experience obeys the specified triggering settings - e.g. the experience shows only once
- Review and check how multiple live experiences will interact in your product
- Reset the progress for the test user to review your experience endless times
- Share the experience permalink with your colleagues and re-iterate based on their feedback
Notes on Test mode
- In order for you to test experiences live using one of the options below, you'll need to publish the experience as well as to make sure that the Userpilot code snippet to be installed in your application and the test user to be identified (see more about the installation here).
- You can always reset the history for the test user to see experiences again (read more about it here).
1. Publishing the Experience in a testing or staging environment
If you're looking to publish the experience safely to your testing environment, you'll be able to control the domain it will trigger on. To do this, head over to the domain settings, choose "Specific Domains", and then enter your testing or staging environment.
This way when you publish the experience, it will only be available to the specified domains.
2. Publishing the Experience only to yourself and your colleagues
Setting the Audience to Only me (useful for testing) will limit the group of eligible users to see the experience only to be you and your colleagues. You can then navigate to a page where the experience would display on and test it. This is particularly useful to test multiple Experiences in the same run.
- We recommend choosing 'Show Every Time' as the triggering setting when choosing this option.
- The test user must have the Userpilot chrome extension builder installed
3. Publishing the Experience only to internal accounts
You can limit the eligible users to see the experience based on the user properties of the internal testers. This can be done from the Audience section where you can target your desired users based on their Unique User IDs, their emails, or even their names.
This way when you publish the experience, it will only be available to the specified audience.
4. Publishing the Experience only to people with the permalink or script
If you don't the experience to show automatically for users, you can set the triggering settings to be ' Trigger manually'. This means that the experience will only show if it is triggered programmatically using the provided script or based on a permalink.
Note: This option can be useful when you want to share the experience with your colleagues to get feedback.
Once you have fully tested the experience and made sure that all looks good, modify the experience targeting settings to include your desired page targeting and end-users. You can now promote the experience and publish it live to your production environment.