With Chameleon, it's easy to deliver guidance to the right users. You can leverage your available user data and the properties that Chameleon collects when targeting your Experiences.
💡 To learn more about the user data you can send and leverage in Chameleon, read the User Data Overview.
Once Chameleon is installed it starts to collect data about your users. The first and subsequent times that
chmln.identify is called, Each user is identified in Chameleon based on their
user ID. Chameleon also adds a set of default properties to that user profile.
This is what we call the identify method and is an essential component of showing the right Experiences to the right users.
Aside from the
user ID, Chameleon collects these additional properties and adds them to each user that loads a page where Chameleon is installed:
The type of browser detected.
The latest browser window width. Can be useful to target certain platforms or devices.
Browser Language code
A parsed version of the
The device that a user is on between desktop and mobile.
First seen by Chameleon
The first time the user was identified (the time when the user record was added to the Chameleon backend.) 💡 This may not be the user's sign-up date if they were created in your system before you installed Chameleon.
Has Chameleon access
Whether the user can build Experiences on your Chameleon account.
Last time the user was identified by Chameleon.
Whether a (specific) Tour was last completed or was not by a user.
Last Tour result
Whether the last Tour completed was finished or ended early, before completion.
Last Tour time
Input a specific date to filter the last time a user engaged with a Tour.
Number of web sessions
The number of times a user was seen, not seen for 90 minutes, and then seen again (starting from 1). 💡 Show a "thank you" when a user comes back for their 10th time.
Testing ID (randomly assigned)
A special property primarily used for A/B testing. It's a number from 0 to 100 that never changes for a user. 💡 Use this number to show a Tour to 25% of your traffic.
Timezone offset (hours)
The standardized offset from UTC that the user was last seen in. For example, PST is -8 (or -7 during daylight savings).
Chameleon also collects data about the Experiences your users interact with. Events such as "Tour Started", "Survey Dismissed" etc. are collected, and also appended with the
User ID (to allow you to understand which user took these actions.) Certain default properties are appended to these events, including:
The main domain associated with your Chameleon account.
The target URL for click actions (such as clicking on a button or link) that contain a page redirect or link.
The URL of the page where the event occurred.
The text of the link or button that was clicked in the event.
💡To see which Chameleon events you can track, read the article on the analytics that Chameleon provides.
Chameleon does not collect other page or user data by default and complies with GDPR, CCPA, and other privacy regulations. Learn more about our practices from our Security & Privacy section.
All the data that Chammelon collects about your users is available as filters when creating a custom Segment. Find them under "Default properties" and refine your targeting to fit your users' behaviors and needs.
You can get creative with these filters and control who sees an Experience and how often. For example, you can:
Test how Experiences look before deploying to your users, by showing them just to your teammates with the "Has Chameleon access" filter.
Control how often users see your Experiences and ensure they are not overwhelmed, by using the "Last Tour time" filter with the appropriate period of time.