User data includes user and group properties or specific product events that help you tailor your audience and Experience content to fit specific user journeys. Chameleon supports different types of data that you can leverage and sync back to your stack.


Availability & Usage

📍 Ready to power your Tours, Tooltips, Microsurveys, Launchers


Quick access


What user data can I use in Chameleon?

There are different types of user data you can send to Chameleon. You can send in user properties, company properties, and user events.

User properties

User properties are attributes that describe your users and are unique to them. These attributes persist over time, and some examples are name, email address, sign-up date, role, or browser type. Chameleon captures some properties (non-identifying) by default, but you'll likely send specific ones from your product.

💡 If you install Chameleon via a CDP such as Twilio Segment or Freshpaint, user properties are sent directly to Chameleon; you can also send them manually via our JS API.

Company properties

Company properties are similar to user properties but attached to a company (group) of the user ("nested"). These are attributes that describe a property attached to a group of users instead of being linked to an individual. Some examples we see often include plan, account name, company name, company size, or industry.

This comes in handy when you want to target many users with the same renewal date, users coming from larger marketing events, or specific-sized companies.

💡 Chameleon supports Group calls via Twilio Segment or Freshpaint; if you are sending company properties manually via the JS API, one of the user properties sent must be the company or group, as per below:

chmln.identify(USER.ID_IN_DB, {     // Unique ID of each user in your database, must be a string (e.g. "23443" or "590b80e5f433ea81b96c9bf6")
email: USER.EMAIL, // Put quotes around text strings (e.g. "jim@example.com")

company: { // For B2B products, send company / account information here
uid: COMPANY.ID_IN_DB, // Unique ID of the company / account in your database (e.g. 9832 or "590b80e5f433ea81b96c9bf7")
created: COMPANY.SIGN_UP_DATE, // To enable targeting all users based on this company property
name: COMPANY.NAME, // Send any data that appears within URLs, such as subdomains (e.g. "airbnb")
trial_ends: COMPANY.TRIAL_ENDS, // Send data about key milestones (e.g. "2017-08-01T03:21:10Z")
version: COMPANY.VERSION, // If your software varies by version then this will help show the correct guidance (e.g. "1.56")
plan: COMPANY.PLAN, // Send null when no value exists (e.g. "Gold", "Advanced")
...
spend: COMPANY.CLV // Send other properties that will help in targeting users (e.g. sales rep, source, stage)
},
});

User events

Events represent the actions your users take in your product and can be anything you set up to track, like clicking specific buttons, inviting other team members, making payments, or visiting certain pages of your app. Events are attached to each user and you can leverage these to target and trigger Experiences.

Chameleon supports real-time updates for events, so as soon as an event occurs, the audience Segment that depends on it will see the Experience in your product.

👉 However, note that Chameleon does not currently support "Event properties" so only the occurrence/count of the event can be used for targeting.

💡 If you install Chameleon via a CDP such as Twilio Segment or Freshpaint, user events are automatically synced to Chameleon. But you can send events via other integrations as well, or our JS API.

Other data types

Aside from these, there are other data types you can access and work with in Chameleon:

  • Chameleon activity/events

Chameleon will automatically track and collect events associated with users interacting with Chameleon Experiences. This will include events such as Tour completed, Launcher opened, Step completed, Microsurvey submitted, and so on.

💡 Read this article to get the full list of events, and learn more about the analytics you can access with Chameleon.

Much of this data will also be available to you for targeting Experiences; simply look for it when creating a Segment:

  • Chameleon user Tags

You can add Tags to your users manually from the Dashboard or via CSV uploads. This is more effective and performs best when you want to target a specific group of users rather than adding a long list of emails to the "within list" filter.


Note: User Tags are different from Experience Tags, which are here to help you organize your Experiences.


To manage individual user Tags, click on any user in the Dashboard and then use the slideout to access the Tags.

💡 Check out this section on managing your user Tags for more, or this section, on tagging with CSV uploads to learn how to Tag multiple users or companies.

👀 Currently, users can only be tagged individually or via CSV upload, but we're working to make bulk tagging from the Dashboard happen soon.

  • Cohorts

This refers to the data coming from integrations (e.g. member of 'new_users' from Mixpanel). Chameleon can connect to a host of other tools, and receive data about whether a user is a member of a cohort/list as defined in that tool. This includes the following:

Technically these are received as user properties but can be used distinctly when defining a Segment.

  • Webhooks data

Webhooks are a simple way to send data to Chameleon from another tool or system (that is able to send webhooks, or supports outgoing webhooks). This will directly update user, company properties, or user events.

💡 Learn more by reading this article on creating custom integrations with Webhooks.

Check out how you can send enriched data from your tool stack to Chameleon, with Hightouch or Census Webhooks.


Why should I send user data to Chameleon?

Chameleon's powerful capabilities include targeting highly-contextual Experiences to your users based on who they are or what actions they take in your product.

For example, you may want to target your trial users, and you will need to know the "sign-up date", or active product managers for which you will need to know their "account created date" and "role"; you can send these to Chameleon and ensure they will get the experience they deserve.

By tracking specific events in your product, such as when a user engages with specific features or when he does not complete critical actions, you can engage them to help them succeed. Create a Tour to guide blocked users, make help docs accessible, or connect with them as they try to accomplish tasks in your product.

💡 Read this article on how to send data to Chameleon to pick the method that works for you.

Leveraging user data in Chameleon

Any user data that Chameleon collects or you send to Chameleon will be available to create contextual, personal, and relevant Experiences. You'll be able to put your user data to work, in the following ways:

  • Defining the audience for an Experience (by creating a Segment with filters that rely on the user data you have available)

  • Personalizing content within Experiences (e.g. referencing a user's name or their account manager within the message of your Experience)

  • For specific URLs/links (e.g. opening a unique URL from a button)

  • Tracking the success of your Tours by leveraging custom events as the 'Goal'.


What user data should I send?

You can send in any information that enables you to create unique and helpful Experiences for your users. Below is a list of required and recommended ideas for user data that you can send and use in Chameleon.

🔲 Necessary properties

  • The user ID is the only thing that you must ensure you pass to Chameleon to be able to deliver Experiences to the right users.

🔲 Recommended properties for targeting & personalization

email address

You can leverage this to identify users in Chameleon.

account created date

Use this to know when individuals became users and target them based on product access.

plan type

Use this property to deliver the right upsell opportunities.

role

Target users based on their role to reach the audience most fit to engage with specific features.

activated, at risk

Send in details about the state of your users to deliver specific guidance for different customer groups.

beta access

Leverage flag/feature properties to reach users with access to specific features.

first name, last name, company name

Use these properties to deliver unique & personalized Experiences for users.

💡 You can also send in enrichment data from a service like Clearbit.

🔲 Recommended events

In the case of user events, they will be specific to your product and your goals. Consider the actions that you want to drive with Chameleon and how you will measure the impact of your Experiences within your product. Here are some examples of events that you can send:

Button clicks

Report a problem, Complete profile

Activity events

visited homepage, sign-up/ registered

Specific actions

Invite, Upgrade

Send in any product click or page view that enables you to deliver better guidance.


How do I manage my user data in Chameleon?

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)

👉 See how to manage your imported data in Chameleon for the steps to do these.

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


Learn More

Did this answer your question?