One important aspect of Chameleon Tours is the Tour Type. This sets whether your Tours will show automatically to your users, or they will self-serve these Tours manually from a Launcher, hyperlink, etc.


Note: This is the updated Delivery Method that we had before for Tours: Automatic Delivery is now Announcement Tour and Manual Delivery becomes Walkthrough Tour.


Which types can I choose from?

The Tour type dictates the philosophy and mindset of your Tours, and you should use both methods very distinctively. We like to think of these using a "push" and "pull" analogy:

  • Announcement Tours (the "push" method)
    Analogous to sending an email to a user, these are not directly solicited and are the product's attempt at encouraging the user towards an action that they will find useful or valuable. 

  • Walkthrough Tours (the "pull" method)
    Similar to a help article that a user seeks out and reads. A user has a clear intention and is motivated to invest effort in learning more to accomplish their objective. 

Emails and help articles have very different formats -- different lengths, different styles, and different designs. Emails require heavy testing and analysis to be successful, whereas with articles it's easier to know if it resolved the user's questions. 

💡 Consider your users' needs as well, and use the Tour Type that's more likely to act on both your goals and their challenges.


Selecting a Tour type

For every Tour you create, you'll have to select its type as the first step during configuration. This is really straightforward and is one of the logical steps you'll go through before publishing the Tour.

Tour type selection step in the Dashboard

Note: You will not be able to change the Delivery Method of a Tour after it has been activated. If you want to use another method, you should duplicate the Tour and apply a different method.


Announcement Tour type

When you choose to create an Announcement Tour, it will appear to the user if they fall into the target audience and all conditions for the first step are met (e.g. page URL, element requirement, user action, etc.).

This Tour type shines when you want to drive user awareness and product discovery.

🎯 With the Growth Plan you also have access to experimentation, allowing you to exclude a control group (randomly sampled from the target audience) from a Tour to accurately measure the effectiveness of a specific Tour vs. nothing. Feel free to get in touch with us if you'd like to benefit from this feature.

👉 Read this article to learn more about experimentation within Chameleon.

Walkthrough Tour type

When you pick a Walkthrough Tour, it means that you can let a user choose to start this Tour at their convenience. This Tour type does a great job at teaching users a workflow.

You can share Walkthrough Tours using the following methods:


Measuring success

The analytics for the different Tour types in Chameleon will be slightly different. But we recommend you set a Conversion Goal for both, so you can track how effective the Tour was in achieving your target. 

🎯 You can also use Microsurveys to measure a user's satisfaction on how effective your Tour was or how happy they are with the underlying product functionality. 


Best Practices

We put together a list of best practices to have in mind when creating Announcements or Walkthrough Chameleon Tours.

For Announcement Tours:

  • Think of these as in-product ads or experiments for features.

  • Keep them down to 1 or 2 Steps.

  • Focus on increasing a user's motivation to explore further.

  • Avoid being intrusive or blocking a user's workflow.

  • Give users the option to launch a more detailed Walkthrough Tour from a button if they are interested in a deep dive.

  • Target users based on who they are or what they've done to increase relevancy.

For Walkthrough Tours:

  • Break these into separate, short workflows (keep them close to 6 steps).

  • Prioritize based on where users are most confused or where help articles are least effective.

  • Link to more information via button actions as necessary.

  • Create different Launchers for different use cases and pages.

👉 Learn more about delivering in-product experiences from our Best Practices Academy.


Know more

Did this answer your question?