With Chameleon, delivering targeted guidance to the right users is easy. Chameleon automatically collects a set of default user properties that you can leverage when targeting your Experiences. This automatic data collection begins as soon as Chameleon is installed and continues throughout the user lifecycle.
👉 To learn more about the user data you can send and leverage in Chameleon, read the User Data Overview.
Data collection in Chameleon begins automatically once the Chameleon script is installed. Each time the chmln.identify method is called (both the first time and in subsequent sessions), Chameleon identifies the user based on their unique user ID and adds a set of default properties to their 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:
Browser | The type of browser detected (e.g., Chrome, Firefox, Safari). |
Browser width | The latest browser window width in pixels. This property can be useful to target certain platforms or devices based on screen size |
Browser Language code | A parsed version of the
💡 Pro tip: Use |
Device type | The device category that a user is on, either desktop or mobile. |
First seen by Chameleon | The first time the user was identified (the time when the user record was added to the Chameleon backend.)
💡 Important: 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 seen | Last time the user was identified by Chameleon, indicating their most recent session. |
Last Tour | Whether a (specific) Tour was last completed or was not by a user. |
Last Tour result | Whether the last Tour was completed or ended early before its 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). This counter helps you understand user engagement patterns.
💡 Use case example: Show a special "thank you" message 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 case example: 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). |
Experience Interaction Data
In addition to user properties, Chameleon collects data about how users interact with your Experiences. Events such as "Tour Started", "Tour Completed", "Survey Dismissed", and similar interactions are collected and appended with the User ID. This allows you to understand which specific users took these actions and analyze engagement patterns.
When using a button "Action" to fire a click on an element, or when placing in-line Embeddables, Chameleon also collects CSS selector information to better identify the specific element. Learn more about selecting elements in Chameleon.
If you use HelpBar, Chameleon collects information about the pages in your application to allow navigation. Certain default properties are appended to these events, including:
Domain | The main domain associated with your Chameleon account. |
Link_target | The target URL for click actions (such as clicking on a button or link) that contain a page redirect or link. |
Page_URL | The URL of the page where the event occurred. |
Text | The text of the link or button that was clicked in the event. |
Page_title | The title of the page that a user visited. |
URL_path | The URL of the page that a user visited. |
Page_h3 | The headings on the pages that a user visited. |
👉To see which Chameleon events you can track, read the article on the analytics that Chameleon provides.
Chameleon does not collect data from other pages or users by default and complies with GDPR, CCPA, and other relevant privacy regulations. Learn more about our practices from our Security & Privacy section.
When you create a custom Segment to target your Experiences, you'll find all the default properties that Chameleon collects under the "Default properties" section. You can use these filters to refine your targeting based on your users' behaviors, characteristics, and engagement patterns.
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.
Personalize Experiences by language or location by using the "Browser Language code" or "Timezone offset" properties to show localized content or time-appropriate messages