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

Chameleon Team avatar
Written by Chameleon Team
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, add in Body

✚ Boosted by Additional Actions

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

  • Involves creating different Experiences (i.e. multiple Tours or Microsurveys) and having these start from a button Action; you can also direct users to specific Steps in the same Tour from buttons.

  • Targeting based on user data
    Involves creating different Experiences and different audience Segments and having the Experience show based on whether the targeting conditions match. You can also leverage Experience events and include for example only users who previously engaged with specific Tours, or gave specific answers in a Microsurvey.

  • Involves using content logic to show different content to users, in the same Experience, based on user data you have available.

✨ 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 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. This works great for "choose-your-own-adventure" use cases when the guidance you offer depends on users' preferences.

All you have to do is configure your button in any Step to trigger a specific follow-up Step (that is not necessarily next in sequence) or the next Experience that is relevant based on users' choices.

❢ Additional Actions

Leverage 'Additional Actions' from any Primary or Secondary button in the Builder to allow users to start other Experiences. 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 button navigation when building multiple flows with Additional Actions -- allow users to complete the initial Tour, so they won't see any follow-up Steps after the Additional Actions Tour launches for them.

❷ Navigation

πŸ“ Available for Tour Steps

When building a Tour with multiple Steps, select any Primary or Secondary button (on any Step) and you'll find the 'Navigation' option to direct users to a specific Step.

You'll see a preview of all the Steps in your Tour, and you can select any Step to allow users to jump to it after clicking the button.

If you also have a "Previous" option for users, this button will always take users to the last Step they've seen, and not the one you have built chronologically into your Tour.

So, for example, you can have 1 button that leads to the 2nd Step and another leading to the 5th in a Tour. On Step 5, you also have a "Previous" button. If users click this, they will go back to Step 1 (where they were before seeing Step 5), instead of seeing Step 4 (which are not familiar with).

When you don't want to take your user to the next Step 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.

When you want users to see different messages depending on their role, company, or other attributes, you can use content logic and user variables to achieve this.

All the data you send to Chameleon can be leveraged to personalize your Experiences based on different user profiles, journeys, or needs. Use content logic to show messages that are relevant to users and differ based on their status or interactions with your app.

πŸ‘‰ Learn more about personalizing Experiences in Chameleon.

πŸ“ 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 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.

Did this answer your question?