The first and subsequent times that
chmln.identify is called, Chameleon adds a set of default properties to that user profile.
chmln.identify is a necessary part of installing Chameleon, and at minimum you must send User ID as part of this call. Without this, Chameleon will not load into the page.
Additional properties collected by default are then added to the User, and can be used for targeting Experience. These include the following:
The latest browser window width. Can be useful to target certain platforms or devices.
A parsed version of the
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).
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.
Last time the user was identified by Chameleon.
Number of web sessions
The number of times a user was seen, not seen for 90 minutes, and then seen again (starting from 1). 💡 Hint: 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. 💡 Hint: Use this number to show a tour to 25% of your traffic.
Chameleon also collects information when users interact with Chameleon Experiences. 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.
🎯 Chameleon does not collect other page or user data by default and complies with GDPR, CCPA, and other privacy regulations. Learn more about our Security practices here.