With Chameleon's Segment integration, you can easily sync data between Chameleon and all of your other Segment-connected tools. You can learn more about Segment by visiting our integration page

The Segment integration includes three components:

  • Installation -- add the Chameleon code snippet to your pages via Segment

  • Data Destination -- send Chameleon data to Segment (and all other connected tools)

  • Data Source -- get Segment data (e.g. user and company attributes and events) into Chameleon (for targeting Experiences)

💡 You can also install Chameleon using Segment. Here's how.


You can choose to integrate Chameleon with Segment immediately when implementing Chameleon or later, at any moment of your Chameleon journey.

Regardless of the moment, the setup process is similar and very simple. In case you're looking to configure Segment both as a Data Source and Destination, you'll just have to go through two steps:

Configuring Segment as a Data Source

To enable Segment to send data to Chameleon, you'll have to configure Chameleon as a destination in Segment. To do this, you'll have to Add a new destination from your Segment Dashboard and search the catalog for Chameleon.

Upon selecting Chameleon from the list, you'll be able to configure your Chameleon destination. To do so, you'll need to copy the unique token that's available at the Chameleon Dashboard's Segment integration page and paste it into the API Key field in Segment.

Note: Here you will also be able to configure other advanced settings, such as Filters, which allow you to have more control over your data by giving you the power to block certain events and properties from reaching the Chameleon Destination.

Once you're ready to start sending data from Segment to Chameleon, simply enable the destination by toggling it on.

You can find all the details about adding new destinations to Segment by visiting their documentation.

Configuring Segment as a Data Destination

From the Segment Integration page on the Chameleon Dashboard, Segment can also be configured only as a data destination.

Having this option active, Chameleon event data will automatically be sent to your Segment workspace every time Segment is detected on the page where the event takes place.

Note: We discourage using this method, as the full potential of integrating Segment will not be explored.


Once you have enabled Segment, you do not actively need to manage or sync data. Data will be updated in real-time.

Segment as a Data Source

Once you've enabled Chameleon via Segment, you'll have the power of leveraging any of your Segment data for targeting Chameleon Experiences and tracking conversion events. 

You will see this data appear automatically when creating a target segment for an Experience, within the list of available filters. You will see the options of Imported properties and Imported events.

For properties, you will be able to use both individual user and company (group) properties to create your Target Audience. 

Note: If your user is part of multiple groups, only the latest group will be used by Chameleon.

You can also leverage user actions within your product to target Experiences. To do so, select Imported events within the first filter dropdown and then select the relevant user action and parameters for this target audience. 

👉 Get savvy about creating custom audiences to target your Experiences

Segment as a Data Destination

The following events will be sent by Chameleon to Segment and then onwards to any other tools you have connected as destinations within Segment:

  • Chameleon Started Tour / Microsurvey

  • Chameleon Completed Tour / Microsurvey

  • Chameleon Step Seen -- by request, to avoid flooding you with events.

Event properties sent as part of these events include the Experience name, URL and others (e.g. Step number) where relevant.

For full details of all Chameleon data sent to Segment, use our schema Google Sheet:

You will be able to see these events appear within your Segment dashboard, in both the Debugger view and the Schema view.

Know more...

Did this answer your question?