Chameleon uses your data to deliver the right Experiences to the right people at the right time. The more data you send, the more precisely you can target, personalize, and measure your in-app guidance.
This article gives you a map of how data works in Chameleon and points you to the detailed guide for each data type.
👇 Check out an interactive demo on how to send and leverage your data in Chameleon.
Availability & Usage
🔐 Startup: 5 Tracked Events
🔐 Growth: 20 Tracked Events
🔐 Enterprise: 50 Tracked Events
📍 Ready to power your Tours, Tooltips, Embeddables, Microsurveys, Launchers
⚙️ Manage from your Dashboard
What user data can I use in Chameleon?
There are three core data types in Chameleon. Each one plays a different role when you build and target Experiences.
Data type | What it is | Example |
User Properties | Attributes that describe an individual user |
|
Company Properties | Attributes shared by all users in the same account or organization |
|
Events | Actions a user takes in your product |
|
👉 For detailed information on each Data type, go to their specific articles:
Beyond these three core types, Chameleon also works with additional data:
Data type | What it is |
User Tags | Custom labels you apply to users from the Dashboard or via CSV uploads, useful for targeting groups that don't fit standard property filters |
Cohort data | Group membership synced from integrated tools like Mixpanel, Heap, Amplitude, HubSpot, and Salesforce |
Experience Events | Engagement data Chameleon collects automatically when users interact with your Experiences (e.g. "Tour started", "Microsurvey submitted") |
Webhooks data | Real-time updates sent to Chameleon from any external system that supports outgoing webhooks |
💡 Read about working with Tags in Chameleon, or read about creating custom integrations with Webhooks to learn more about these additional data types.
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.
Without data, you can build Experiences but you can't control who sees them or when. With the right data in place, you unlock four capabilities:
Audience targeting | Create Segments based on user attributes, company attributes, or in-product behavior to reach only the users who need a specific Experience |
Content personalization | Reference properties like |
Dynamic URLs | Open a unique URL from a button based on the current user's properties, so each user lands on the right page |
Success measurement | Use Events as Goals to track whether a Tour is driving the behavior you intended |
What user data should I send?
The only required property is the user ID; everything else is optional ✨. That said, we recommend sending at least these:
| You can leverage this to identify users in Chameleon. |
| Use this to know when individuals became users and target them based on product access. |
| Use this property to deliver the right upsell opportunities. |
| Target users based on their |
| Send in details about the state of your users to deliver specific guidance for different customer groups. |
| Leverage flag/feature properties to reach users with access to specific features. |
| Use these properties to deliver unique & personalized Experiences for users. |
💡 You can also send in enrichment data from a service like Clearbit.
Recommended events
Your events will be specific to your product and goals 👨🔬. Consider the actions you want to drive with Chameleon and how you'll measure the impact of your experiences.
Button clicks |
|
Activity events |
|
Specific actions |
|
💡 Send any product click or page view that enables better guidance delivery. The more behavioral data you have, the more precisely you can target your experiences.
ℹ️ Note that when sending data to Chameleon, null-valued properties will not be sent and, are removed as a matter of cleanup and consistency.
Sending User Data to Chameleon
👉 You can see the data collected by default by Chameleon here
There are three ways to send data. Each supports different data types and suits different teams.
Method | Best for | Supports |
Integrations (Twilio Segment, Freshpaint, or other connected tools) | Teams already using a CDP — data syncs automatically | User Properties, Company Properties, Events, Cohorts |
API (JavaScript or Backend) | Developers who want real-time, programmatic control | User Properties, Company Properties, Events |
CSV imports | One-time uploads, static lists, or non-technical teams | User Properties, Company Properties, Tags |
👉 Read about how to send data to Chameleon for a detailed comparison and help choosing the right method.
👉 Read about how to import data with CSV files for step-by-step instructions on uploading from the Dashboard.
🧑💻 Developers can help: ask your technical teammates to help you if you're not comfortable doing this alone. You only need to do this once, so gather the list of user data you want to use in your segmentation and ask your developers to send it all!
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 of 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
Filter through properties in your account
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.