All Collections
Creating Experiences
Building flows using multiple Experiences
Building flows using multiple Experiences

Learn how to branch your Experiences based on user responses and review user interactions across multiple flows

Pulkit Agrawal avatar
Written by Pulkit Agrawal
Updated over a week ago

We recommend that you keep your Tours short, contextual, and directed towards a particular goal for maximum impact. But sometimes, using one simple Tour won't be enough to help users get the most out of your product.

There might be a scenario where you'll need to personalize the actions that users should take based on their unique needs. This ensures your in-app guidance helps all users on their journeys and each user engages with unique and valuable guidance.

Availability & Usage

πŸ“ Available for Tours, Tooltips, Microsurveys, Launchers

βš™οΈ Configure from Buttons

✚ Boosted by Additional Actions

In Chameleon, you can easily connect multiple Experiences and guide users based on different responses, or interactions. There are 2 ways you can achieve this:

✨ In Launchers, you can configure different Tours to show to different users, by creating different Segments and picking the sub-audience for each one.

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. But here are some interesting use cases for Experience branching:

  • 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

Branching your Experiences based on users' responses is most useful when you don't have the data you need to take them through personalized paths.

All you have to do is configure your button in a Tour Step or a Microsurvey to trigger the next Experience. You'll leverage 'Additional Actions', available for both Primary and Secondary buttons in the Builder. Simply pick the Experience from the list, and users will launch it once they click your button.

✨ To ensure that your Tour will not start in other ways than your users pressing a button, you can set it to be a Walkthrough Tour.

Be mindful of the main button action that you'll pick when building multiple flows this way; you can allow users to navigate to the next Step or complete the initial Tour. Keep in mind they'll also see any follow-up Steps after engaging with the Tour you add as Additional Action.

πŸ“ Available for Tours, Tooltips, Microsurveys, Launchers

You can easily review how users can interact with your Experience and the actions they'll follow on each Step by using the 'Interactions map' in the Dashboard. You can access this feature on all Experiences from the 'Build' panel, by toggling on 'Show interactions'.

On the Interactions map, you can review:

  • all button Actions

  • the display rules added to each Step

  • where each Step Action leads to (including specific links or resources)

  • where and when users will exit each flow

  • how other Experiences (connected to that flow) look like

β„Ή If you have multiple Tour Variants, as is the case with A/B Testing, you'll see a different Interactions map for each Variant.

Use the Interactions map to easily understand the user flow and how each action contributes to the bigger goal of your Experience. This is also a great way to review the resources you're sharing with users and easily identify any gaps, or opportunities that you can address in your existing guidance.

With Microsurveys, you'll see the different actions for each of your 'Comments Steps'.

You can also preview your connected Experiences from the Interactions map, without having to open the Builder to check for styling, CTAs, or other details. Simply click the linked Experience 'eye icon' to preview it.

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.Β 

All this data can be used to target an Announcement Tour or other Chameleon Experiences to show to the right group of people. Simply create your audience Segments and leverage them when building your Experiences.

πŸ’‘ 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.

Did this answer your question?