A/B Tests are a great way to accurately measure the impact that Chameleon is having and compare different versions of a product tour.
Chameleon makes it very easy to run a Control Group (Chameleon vs. nothing) or A/B Test (two different Chameleon Tours). We recommend starting with a Control Group test and iterating until your Tour is effective, before testing Tour variations.
Control Group testing
There are two ways to deliver Chameleon Tours and testing here is relevant for Automatic Tours only.
Setting a Control Group
Once you have selected the Automatic option, you will be able to turn on Control Group testing and set the proportion of users that should be part of the control group -- as in the image below, where a random 20% of the target audience users will not see this Chameleon Tour.
Whenever a user within the Target Audience is liable to see this Tour, an event will be logged. This event -- "Chameleon Experiment entered" -- will be available within all your connected analytics integrations.
Note: Within Mixpanel, the event name will be "Experiment Started" to better match with Mixpanel's experimentation analysis framework.
For this event the following properties will also be logged:
The "Group" property values are either:
Control (Out) -- user is part of the control group and will not see the Tour
Test (In) -- user is part of the test group and can see the Tour
Other events (e.g. "Tour started") will also be logged as normal once a user starts interacting with the Chameleon experience. You will see all these within your analytics platform (e.g. Amplitude, Heap, Mixpanel, Google Analytics) and can use this to further analyze conversion or relative impact of your Chameleon experiment*.
* It is within our plans to deliver reporting within the Chameleon Dashboard to measure experiment success and goal conversion, let us know what you'd like to see here.
A/B and multivariate testing
Chameleon also lets you manually show an Experience to a random proportion of your Target Audience, so that you can show two different Tours to different groups or group multiple tests to the same random sample.
Manually defining a Test Group
To create a Test Group, simply add an extra "sampling filter" filter to your Target Audience that selects a random sample of users of the desired size. This means you can still target users based on other conditions, such as user properties, events, data sources, etc.
To add the sampling filter:
Select 'Default properties' as the type of filter
Select 'Percentage' in the next dropdown
Use 'more than' or 'less than' to define the range of users
Set the boundary number for this 'Percentage value'
What is "Percentage" corresponding to?
Every user identified by Chameleon is automatically assigned a random percent property with a value between 0 and 100. This value is persistent so that it can be used for targeting users and, more specifically, for experimentation purposes.
In the above example, users that have a "Percentage value" between 50 and 100 would be targeted. This would constitute 50% of the users within the group defined by the other segment filters.
To target 10% of users, you could use either:
Percentage more than 90
Percentage less than 10
You could also use multiple filters to target another 10% group (e.g. Percentage more than 10, and Percentage less than 20).
You can use the same filter configuration in another Target Audience (by re-creating the filter) to target the same user group. This means you can run multiple A/B tests to the same user group.
How to A/B Test different variations of a Tour
To test two variations of a Tour:
Create the control variation of the Tour, including the Target Audience, using the sampling filter above
Duplicate the control Tour, update the Tour name (using the variant name/label), and then re-create the Target Audience. This time use the opposite sampling filter, so that you're targeting the alternative user group
Set both Tours live
Analyzing the results
You will be able to use the Tour name to segregate the data, as each Chameleon event contains additional attributes, such as Tour name, User ID, URL, etc.