Even though we generally recommend that you keep your Tours short, contextual, and directed towards a particular goal, sometimes using only one Tour will not do the job.

There might be a scenario where to keep your Tours effective and contextual, you'll need to personalize and branch them so that your users follow a journey that is unique and valuable.

Quick access

There are two main methods you can use to personalize your Chameleon Experiences:

Branching your Experiences based on a user's response is most useful when you don't have the data you need to take your user through a specific personalized path.

It allows you to collect the necessary data by having your user press a button in a Tour Step or a Microsurvey, which will trigger the next Experience. To trigger a Chameleon Experience from a button, you will need to leverage button actions, available for each Primary and Secondary button, in the Builder.

Note: To ensure that your Tour will not start automatically in other circumstances other than your users pressing a button, set it to be a Walkthrough Tour.

When you don't want to take your user to the next Step of your Experience flow immediately after a button click, then you can trigger an Experience automatically based on user data.Β 

This can include data Chameleon collects (e.g. Microsurvey response, completed Tour, etc.), data sent from any connected integrations, or data you send to Chameleon via the API.Β 

Any of this data can then be used to target an Announcement Tour or other Chameleon Experience to show to the right group of people.

πŸ’‘ If you have multiple Tours that need to be shown to your users, you may also want to set the order in which they appear. One way you can do this is by filtering your target audience to ensure that a particular Tour has been started/completed before the users are added to this Segment.

πŸ‘‰ Read this article to learn how to show your Experiences in the right order.

All cases are different, and how deeply you can adapt an Experience flow will only be defined by the depth of your own use case. Nevertheless, below are listed some interesting use cases for Experience flows:

  • Collect user persona/objective with a Microsurvey, and show different onboarding flows accordingly

  • Ask about satisfaction levels with a Microsurvey and show a Tour prompt to leave a review or schedule a call depending on whether a user is happy or not

  • Ask if a user needs more help with a Microsurvey and show a Launcher with detailed How-To guides if a user does

  • Ask a user if they want to opt-in to helpful tips and then show Tours accordingly

You can also update the data in your database from the user response using a simple JS code snippet. Learn how.

Konw more

Did this answer your question?