⚠️ This functionality is being deprecated in favor of sending event data directly via our API and using our native integrations to send user data. As a consequence, you may not see this functionality within your account.
Product tours are most effective when they are relevant to a user. You can increase the relevance of a tour by showing it to users based on what they have done in your product.
There are two ways of achieving this:
- Target a tour to certain users based on conditions that include events completed
- Show a step (as part of a tour) triggered by a user action on the page
This article references the first: how to save events within Chameleon to use within a user segment for targeting a tour.
Defined vs. Imported events
You can send event data to Chameleon (if you use Segment.com this will automatically be available) which you can use as part of a "Imported events" filter when creating a user segment.
This can include front-end events (e.g. user clicking a menu item) or back-end events (such as a user uploading a document).
However, in case that is difficult, you can also define events (page loads and clicks) right from within Chameleon, without requiring any coding. These events will then be available within the "Defined events" filter.
Below you can see these two different filter types:
How to define and track an event within Chameleon
To start tracking an event, simply "Add new Event..." from the dropdown when selecting a Defined event, within the Segmentation view.
There are two types of events you can define:
- Page load: will track every time a specific URL is loaded
- Element click: will track each time a particular element is clicked
You can define these and name them, and then use these for targeting tours.
NOTE: These will only be tracked after they have been defined. Therefore instances of users completing these events before they were defined will not be recorded. For a more accurate historical record of what users have done, please send event data to Chameleon via the API.