User properties are attributes about users, such as their name, email address, role etc. This data can be helpful to allow you to target Chameleon Experiences to the right user, and also personalize the content of these Experiences.

As an example, you may want to create a new user onboarding Tour that only shows to users created in the last 7 days, and includes their first name in the body text.

Your product and database likely already collects these, and we recommend sending some of these key properties to Chameleon. Once you do, then these properties will be available to you within the Chameleon dashboard to use when creating target audiences.

Create and manage your Segments here. Learn more about Segmentation here.

How to send user properties

Chameleon collects some basic (non-personally identifiable) user properties by default, such as browser. You can see the list of these here.

You can send your own custom user properties to Chameleon via 3 methods:

  • Our front-end (JS) or back-end (REST) API. Read about the JS API here and the REST API here.

  • Webhooks sent from your system or another tool. Learn more here.

  • when using that to install Chameleon. Learn more here.

You can see examples of how to do this via your Chameleon installation page.

You can also send group or nested properties, such as Company properties. This can be helpful when many users are attached to a single group (for B2B products) and certain properties are associated with that group (e.g. plan) instead of on an individual user basis.

Note: Chameleon seamlessly supports and correctly formats group calls so no additional work is needed when installing via Segment.

Managing User Properties

All the data you send to Chameleon can be seen and managed on the Data Management section in your Chameleon Dashboard.

Here you can do things like:

  • Review what data your team is sending already

  • Check how recently data has been sent

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

  • Archive events or properties (to hide them within any lists when creating a target audience or setting a goal)

Learn More

Did this answer your question?