By default, Experience Analytics indexes various request data so that Experience Analytics components and users can search for sessions using a range of criteria. The set of available fields is defined for the most common case. Any application-specific fields or data added using optional Experience Analytics components is not automatically available for search.
The following section provides a set of potential methods for making any request variable available for indexing and searching.
To make data available for indexing, it must be located in or moved to a section of the request where data is indexed.
[appdata]section of the request.
The purpose of indexing, however, is to make the data available for search. It is possible to also make request or response data available for search by creating events that capture and store the values as event data.
In the sections below, the different approaches are described, and examples are provided for making the data available for each approach.
Methods for making indexing available for search
Use the following methods to make request or response data available for indexing. You can also use these methods to move response data.
Move request data to
Using the Privacy session agent, you can move any request variable into the
Create an event to capture the request data
Through the Event Manager, you can create an event to capture and store the request data. From the Portal, you can then search for sessions using the event or values for the event.
Using privacy to insert Request or Response data for indexing
The Privacy session agent can be used to move request or response variables and values into the
[appdata] section of the request, where it is automatically made available for
RequestVariable contains RequestVariableValue
RequestVariable= the name of the request variable
RequestVariableValue= the value of the request variable
While the above method works, it is expensive in terms of Search Server processing. Experience Analytics recommends moving the data for indexing for searching for common request variables.
The CX UI Capture for AJAX solution captures items that may not generate transactions with the web server, such as user interface events and other properties, from the visitor's browser and submits them to Experience Analytics for capture. Using CX UI Capture for AJAX, you can capture a rich repository of data about visitors to your web application.
When CX UI Capture for AJAX is deployed, some Experience Analytics performance reports are populated with data captured from the visitor's browser. These reports are available through the Portal.
However, these reports are generated from internal events in the Canister. For maintaining performance, the Canister does not maintain events to reflect all of the possible data captured from the client. For example, exceptions detected in the user interface are detected by CX UI Capture for AJAX and submitted to Experience Analytics, but they are not available in the provided reports.
This information could be very valuable for assisting customers with problems with your web application and then providing that information to developers to resolve. If you were able to capture this information and store it in such a way that it is indexed for search, CSRs at your enterprise could search for these sessions, drill into them to locate the customer issues, and then provide the sessions to developers for further resolution.
Experience Analytics automatically provides this information in the
[env] section of the request. In that section, CX UI Capture for AJAX
inserts the following request variable containing an identifier for the number of client user
By default, Experience Analytics does not index this field, so you can use the Privacy
session agent to move this field into the
[appdata] section of the request.
[appdata]section of the request, you can copy and paste finished versions of the rule to create new, similar rules.
To configure privacy indexing:
- Verify that Privacy is enabled.
- Open the privacy configuration.
- Create a privacy action and rule.
- Test the privacy action and rule.
- Create any additional rules and actions.