How to get performance data
Chameleon automatically collects data on how effective your product tours are, and you can use this to determine which steps / tours to improve and measure iterations.
Here are three ways you can review your tour performance data outside of Chameleon:
- Exporting a CSV
- Automatically sending data to a product analytics tool we integrate with
- Via our API
To download the performance data for any tour as a CSV file you'll want to first navigate to the the Tour in the Editor and click on "See performance" button:
This will open up the Chameleon dashboard where you can view reporting for that Tour and for your other Tours and Chameleon products.
From this view you can download all the data via CSV or review performance over a set time period.
CSV data export
Clicking the "CSV" download icon will send an email with a link to download the CSV sheet. It may take a few minutes for this email to arrive in your inbox depending on how much data is contained (how many users have experienced the tour).
Each row in the CSV represents a unique action (event) a user has taken in your tour, within the select time-range. These events include:
- Tour started: when a user sees the first step of the tour
- Tour exited: when a user dismisses any step of the tour
- Tour completed: when a user completes / advances from the last step of the tour
- Step seen: when a user sees a step within the tour
Each row also contains user properties / attributes associated with the user that took this action. This includes default user properties collected by Chameleon, and custom user properties that your product is sending to Chameleon.
We highly recommend sending user properties to Chameleon to help you target your tours. Learn more about how to send user data to Chameleon.
If your tour contains 4 steps and in the time period selected has been started 6 times, completed twice and and dismissed 4 times, then you might see a table of data such as:
How to use the exported data
You can use the exported data to conduct a range of analysis, to answer questions such as:
- Which step are users exiting the tour the most?
- Which specific uses have seen a particular step?
- Which specific users have completed or dismissed the tour?
- Tour success by user property (such as language or a custom property)
- How long it took a particular user to complete a step
To do this, we recommend creating a Pivot table from all the data, and then selecting the most relevant data to plot and compare.
Pivot tables allow you to more easily group, filter and chart a large table of data. In the pivot table you can decide which columns from the original data to show on each axis and add further filters. You can create pivot tables in MS Excel or Google Sheets.
To make this easier, we have a downloadable template you can use as a basis of your analysis. Simply open this Google Sheet to make a copy, add your own data, and start using!
Below are the definitions of the columns you will see in your exported data. All data is accurate at the time that the event took place, for the live / activated / published tour:
- tour_id The unique and persistent ID for that tour. Learn how to expose this.
- tour_name The name of the tour
- tour_steps The total number of steps in the tour
- step_id The unique and persistent ID for the step [only for Step seen events]
- step_number The sequence number of the step within the tour [only for Step seen events]
- event_name The type of event (see above)
- timestamp When the event took place
- elapsed_time For tour events, the time since the beginning of the tour. For step events, the time the step was showing.
- Default user properties => // divider for the next set of columns (default user data). See more details about the default data Chameleon collects here.
- uid The unique ID for the user that caused the event, as sent by your product. This should match the ID you use to track users in your database or other analytics tools. It is sent as part of the Chameleon installation; learn more here.
- browser_width The width in pixels of the browser
- browser_name The name of the browser
- browser_language The default language code of the browser. For a list of language codes, see this.
- browser_timezone The timezone for the browser, relative to GMT / UTC. So Pacific Time would be -8.
- last_seen_at session_count The number of web sessions (separated by 90 mins of inactivity) detected by Chameleon for that user (count begins after Chameleon code snippet is installed).
- Custom properties => // divider for the next set of columns (custom user data). Learn more about how to send custom user data to Chameleon.
- active_at Example data: when the user was last active
- alexa_global_rank Example data: the Alexa rank of the user's company website. You can supplement your custom data with services such as Alexa and Clearbit.
- clear_employees Example data: the number of employees of the company the user is associated with. Chameleon can track company data alongside user data; learn more here.
- role Example data: the user's job title
- ... Other data that your product is sending to Chameleon.
- If a step has a dismiss option, which is configured to show the tour again later, it will not generate a Tour exited event.
- This data does not contain detailed Step Seen event data (with information on all the step configuration). However this data can be sent to your connected integrations. To enable this for your account, please message us.
Chameleon collects more data than currently available in the CSV. We will be updating this soon, but to see all the data currently collected (and logged to connected analytics integrations) please review our data schema Google Sheet here.
If you have any questions or issues please review how to best get help.