One important aspect of Chameleon Tours is the Delivery Method. This is where you determine whether your Tours will show automatically to your users, or they will self-serve these Tours manually from a Launcher, hyperlink, etc.
The Delivery Method 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:
Automatic 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.Manual 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 are very different formats -- different lengths, different styles, different designs. Emails require heavy testing and analysis to be successful, whereas with articles it's sufficient to simply know if it resolved the user's questions.
Selecting a Delivery Method
For every Tour you create, you'll have to select a Delivery Method. This is really straightforward and is one of the logical steps you'll go through before publishing the Tour.
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.
Automatic Delivery
When a Tour has an Automatic Delivery Method, 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.).
Growth Plan customers will also have access to experimentation, allowing you to exclude a control group (randomly sampled from the target audience) from this Tour to accurately measure the effectiveness of this Tour vs. nothing. Feel free to get in touch with us if you'd like to benefit from this feature.
👉 Know more about experimentation in Chameleon
Manual Delivery
When a Tour has a Manual Delivery Method, it means that you can let a user choose to start this Tour at their convenience. You can do this using the following methods:
Launchers
You can include a Tour as part of one of your Launchers. For example, having a checklist for new users to guide their onboarding, having a "what's new?" center drive feature discovery, or deflecting tickets by addressing common support requests. Learn more about using Launchers.Tour Links
Each Manual Tour will have a unique URL you can share in an email, blog post, help article, etc. This can be a great way to bring your users into your product using an external context. Learn more about using Tour Links.API
You can also use our API to show a Tour. This will give you the freedom to include it anywhere in your application, and use triggers from there. Learn more about using our API to show a Tour.
Measuring success
The analytics for the different Delivery Methods will be slightly different but for both, we recommend setting a Conversion Goal 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
Below are described some of the best practices to have in mind when creating an Automatic or Manual Tour.
For Automatic 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 Manual 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 Manual 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.
👉 Read more best practices for your in-product experiences