The eyezon widget embedded into your website is a part of the customer journey to purchase. By combining the data collected by our service with your sales funnel analytics, you can build end-to-end analytics and match customers' activity in the eyezon widget with their behavior on your website for a complete understanding of how our service contributes to your sales.

Setting up end-to-end analytics with eyezon

For end-to-end analytics to work, you need to connect customers' activity data collected in the eyezon widget with the data from your choice website traffic analytics system, such as Tableau, Excel, or Google Analytics. The clientID parameter from your website traffic analytics has to be sent into the eyezon widget by a script in real time. This script has to be developed on your side, integrated into your website, and work independently of the eyezon button and widget scripts.

After that, the data on tthe customer activity, combined with the clientID parameter is available for download from our dashboard as an Excel file. You can upload this data into your choice website traffic analytics system and build end-to-end analysis of the customer path to purchase.

Step-by-step manual

1. Create a script. User activity data from our widget can be combined with the data from your traffic analytics system by matching the clientId parameter. Please ask you your web developer team to create and deploy a script to send traffic data with clientId into the eyezon widget.
2. Setting the API. The data can be sent to the eyezon widget only if API settings are correct. Please find the detailed description of the API settings further below.
3. Exporting the data in .xls format. If API settings are correct, the aggregated data will be exported from eyezon in .xls format.
4. Combining the data. Data from the eyezon .xls file and data from the traffic analytics system need to be matched by clientId parameter in your analytics such as Tableau, Excel, or Google Analytics.

API settings

Setting API implies data exchange between your website or your traffic analytics system and the eyezon widget. Currently, there are two extended API parameters available: clientId and region.

• clientId is an ID generated by your CMS, online store management system or traffic analytics system such as Google Analytics, Adobe Analytics etc. It allows you to combine the customer journey data with the data reflecting their interaction with the eyezon widget.
• region is an ID that allows you to segment incoming requests by geography.

To send these parameters to the eyezon widget, please trigger the setAnalyticsParam API method upon each page load:

eyeZon('setAnalyticsParam', 'analyticsClientId', '123456'); 
eyeZon('setAnalyticsParam', 'analyticsRegion', 'Berlin'); 

// you can also extract '_ga' cookie to get clientId used by Google Analytics  
// or '_ym_uid' cookie to get clientId used by Yandex Metrics

After that, in the exportable eyezon .xls file, the Region and ClientId columns will be filled.

<aside> ⚠️ As data will start collecting only after the API has been set up, historical data will not become available.

</aside>

Types of eyezon data for end-to-end analytics