Session agents can be added through the Pipeline Editor in TMS. This session agent is added to the default pipeline on each Canister. The session agent must be present in any pipeline that processes session hits.
The configuration options are changed with the TealeafCaptureSocket.cfg file that is stored on the server. These settings are also available through the Pipeline Editor, which is the recommended method for configuring session agents.
Client-side capture references
The Reference session agent adds TLT_CUI_URL and TLT_CUI_APPLICATION_NAME values to the request buffer to track the URLs and application names from which events captured from the client user interface are generated.
These values are generated when the Tealeaf CX UI Capture for AJAX is licensed and deployed in your environment to capture user interface events occurring in the visitor's browser. For more information, contact your Tealeaf representative.
These values are generated like normal reference values, but they might not match the values in the normal members. The normal members represent the parent page from which the AJAX client-side events were started. Because the child event might post to any page, its value might not match the parent page.
TLT_CUI_URLis rendered as the normalized value for the client-side URL.- If the session agent is configured for overloading the application field,
TLT_CUI_APPLICATION_NAMEmight be used in a different way.
The Reference session agent also adds TLT_CUI_URL_ID and TLT_CUI_APPLICATION_NAME_ID values to the request buffer, which allows coupling of data from AJAX requests and the parent pages from which they are started. They follow the same scheme as the regular TLT IDs. All of their information comes from the same reference files, and they can be manipulated and augmented in the same way.