Segment makes it easy to send your data to Chameleon (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Chameleon in the format they understand. Learn more about how to use Chameleon with Segment.
Our Chameleon destination code is open-source on GitHub if you want to check it out.
When you enable the Segment direct destination on the Chameleon dashboard we will immediately start receiving your app’s user and event data collected by Segment.
This helps you target product tours to specific (segments of) users. You can read more about how to segmentations work in Chameleon’s docs
At a minimum we suggest sending us:
We recommend sending us properties that you would like to use to segment users into a handful of groups. Some examples of the properties you may wish to use to segment users include:
account role(admin vs user)
account value(paid vs free)
account status(converted vs retained)
Examples of other specific properties you may also wish to send us include:
credit(# of dollars in account)
respoitory_count(# of authorized items)
support_requests_count(# of touchpoints generated)
chats_count(# of times user reached out for help)
When we know more about your user, we can help you target them more effectively. For example, you could show different tutorials to the account admin and other team members.
You can send us your app’s events for two main reasons:
- Signal a
conversionfrom a product tour (a user successfully completing the action that they were prompted to take with the tour)
- Trigger a specific product tour (coming soon)
Product tours should lead to user actions and so offer the option of tagging each Chameleon product tour with a ‘conversion event’ that helps you track how successful your tour is. We collect data about each tour (users starting, completing, conversions) and send this back to your preferred analytics provider. Read more about the analytics Chameleon tracks.
For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Supported Sources and Connection Modes
To learn more about about Connection Modes and what dictates which we support, see here.
Segment lets you change these destination settings via your Segment dashboard without having to touch any code.