Acoustic™ Tealeaf cxConnect for Web Analytics enables easy integration of Tealeaf session data with third-party web analytics applications to reveal trends and anomalies while leveraging your enterprise's investments.
When Tealeaf data is integrated into these suites, your web analysts can review existing funnel reports and drill down into Tealeaf sessions for further investigation. In this manner, the rich data set provides aggregated insight and the support details down to the individual field.
From any of the web analytics products listed below, you can define a session segment based upon search criteria you provide. This query is submitted to the Tealeaf CX server via the Segment Builder Service, and cxConnect for Web Analytics automatically generates a session segment containing the matching set of sessions.
From this segment, you can replay individual sessions or perform further analysis on the segment.
Integration with Tealeaf
This section describes the methods for integrating third-party applications with the Acoustic Tealeaf CX platform using Acoustic Tealeaf cxConnect for Data Analysis.
| Method | cxConnect for Data Analysis | Description |
|---|---|---|
| Replay Link | Voice of Customer | Allows replay of a single session. |
| Data Insertion | Voice of Customer | Allows external data (events) to be inserted into a session through a customizable image request. |
| Segment File | Web Analytics | Allows creation of a session segment from a list of supplied session identifiers. |
cxConnect integration through data insertion
The data insertion method of integration is used to associate website content and customer experience data, delivered by third-party and/or internal systems, with Tealeaf captured sessions, where the information to integrate is not included in the HTTP stream that is captured by Tealeaf.
The data association is accomplished by making a request, which includes the data to be associated as query string parameters, for an image file located on the web infrastructure that is automatically captured by Tealeaf.
tl_img.html.For performance and data optimization reasons, by default the Tealeaf system filters all requests for common binary formats, such as .gif, and drops them from the captured data stream. To bypass this filter, the .html extension is used for the image file, ensuring that the request and all included data pass through the Tealeaf system.
The URL for the image request is as follows:
http://<HostPathToImage>/tl_img.html?Source=<Source>&Event=<Event>&SidName=
<SidName>&SidValue=<SidValue>&Custom1=<Custom1>&Custom2=<Custom2>
| Parameter | Required? | Type | Description |
|---|---|---|---|
HostPathToImage |
Y | [string] | Path to the tl_img.html file on the target web infrastructure. |
Source |
N | [string] | Used to identify the third-party or internal system that is generating the request. |
Event |
N | [string] | Used to identify the type of event of the request (for example, start and complete). |
SidName |
N | [string] | Used to identify the name of the cookie that is used for sessionization in the Tealeaf system.
Note: If session cookie name/value pairs are not automatically associated with the request. If they are overwritten, then the
SidName parameter is required to associate the request with its originating session. Otherwise, the image request will become a one-hit session in Tealeaf and might be dropped. |
SidValue |
N | [string] | Used to identify the value of the cookie that is used for sessionization in the Tealeaf system.
Note: If session cookie name/value pairs are not automatically associated with the request or if they are overwritten, then the
SidValue parameter is required to associate the request with its originating session. Otherwise, the image request becomes a one-hit session in Tealeaf and might be dropped. |
cxConnect integration through segment files
The segment file integration method is used to automate the creation of a Tealeaf session segment that corresponds to a segment defined in a third-party system.
The integration and automation is accomplished by supplying a file containing a list of values that identify unique customer sessions to the configured Segment Builder. Once created by the Segment Builder, the session segment is available for review and analysis in the Portal.