A key component of personalizing and targeting in-product Experiences built with Chameleon is sending relevant user data. 

You can send user events (actions users take) or user properties (attributes about the state of the user). You can also send company properties to help target users based on the company (account or organization) they are part of. 

💡 Read the User Data Overview to learn what data you can leverage in Chameleon or see how you can send your users' data to Chameleon.


Quick access


Dashboard management

All the data you send to Chameleon will be available to you in the Data Management section in your Chameleon Dashboard.

Here, you switch between the different types of data and can do things like:

  • Review what data your team is already sending to Chameleon

  • Check how recent data has been sent

  • Rename and add descriptions to your properties and events (to help team members understand and leverage data)

  • Archive events or properties that aren't relevant (this will hide them within any lists when creating a target audience or setting a goal)

💡 Read more about managing user Tags or Experience Tags which you'll also do in the Dashboard.

Choose what user data to see

In the user properties tab, Admins can also choose how to identify and display users throughout Chameleon.

Here you can configure which type of properties to show when displaying your users in the Chameleon Dashboard. Want to view users by their first_name & UID? 🤔

Just select these properties from the 2 dropdown fields. You'll find there your imported properties and you can easily choose a combination that fits your needs.

🖼 Need more context? Check the "Gravatar" box underneath to get your users' profile pics into your dashboard.


Note: Checking this authorizes Chameleon to share end-user emails with Gravatar.


Editing user data

You can edit the name and description of any user property or event by clicking on the pencil icon (or the description directly in the table). Here, you can also choose to archive properties or events that are no longer relevant. This will hide them from your Dashboard.

The same goes for editing any events; you can edit or archive them as you see fit. In the events table, you'll also see the event type. In the example below, we have 2 imported events, meaning they were sent to Chameleon via the API or an integration.

💡 If you want to learn more about tracking page views or clicks read this article on how to track user events for Experience targeting.

🤝 Keep a system of naming and organizing your data, so anyone on the team can leverage it efficiently.

Deleting users

You can remove existing users in any Segment or from your All users list - simply select one (or several) and use the Actions menu to delete them. You can use Shift-select to delete multiple users. 😉

This will remove a user profile and all the associated data, including Experience interactions or Microsurvey responses.

deleting a user from the Dashboard gif

💡 You can also delete user data via our API.


Data formats

You will notice different data formats in the user data tables:

  • number = as straightforward as it gets; can be a whole number or a positive or negative whole number with a decimal point.

  • string = a collection of alphanumeric characters between double quotes.

  • timestamp = the current time of an event that is recorded.

  • boolean = these have two values - true and false.

This helps Chameleon understand the type of data contained in each property; and also sets what kind of operators are available when using this to target users. For example, a string  data type will have operators such as contains and does not contain; whereas, for a timestamp  type, you will see operators such as before date and after date.


Note: If the data you are sending is classified as the incorrect type then please send us a message, so we can help you fix it (will require a code update). 


Nested Objects and Arrays

Chameleon supports up to 2 levels of nesting for Objects and Arrays of any length. Arrays may contain any value types except the Array and Object types.

An Object: is a set of values inserted between {} (curly braces). The keys must be strings and should be unique; multiple value pairs are separated by a, (comma).

An Array: is an ordered collection of values that begins with [ (left bracket) and ends with ] (right bracket). The values of an array are separated by ,(comma).

💡 The following is an example user profile object. Notice that it includes a nested object with an array.

chmln.identify(UID, {
  metadata: {
    role: {
      id: '5a17',
      name: 'owner',
      display_names: ['Owner', 'Admin'],
    }
  },
  roles: ['owner', 'contributor', 'analyst', 'billing']
})

Limits and Errors

The value for each user property and each Array member is limited to 768 bytes. Any data received that exceeds this limit will be truncated at the 768th byte and you'll see a warning on the data management page for user data or for company data.


Learn more

Did this answer your question?