Through the Portal, you can define search templates and session list templates.
- Search templates specify the set of fields and default properties that are available to users when the search template is selected.
- Session list templates are lists of attribute columns used on the session list grid for search results.
To define search templates, select Configure > Search Templates in the Portal menu.
You can specify the user groups that can access the selected template for searches.
A search template defines the scope of the criteria that can be used to search and are an effective means of limiting for users and groups the searchable fields that they can search.
By developing and deploying well-designed templates, the Experience Analytics administrator can focus searches on the terms of interest to specific groups, prevent access to sensitive fields, and limit the number of returned results for better search performance.
Search templates are available for selection in the session search and visitor search pages.
Search templates control the fields that are available for a user to use in a search, as well as the default attributes of the search such as date range and servers to search. On the Search Templates pane of the Search Template Configuration page, there is a list of defined templates, categorized by search type. The three search types correspond to a set of searchable sessions:
As the templates are incompatible across search types, each template has a list of search fields available to it.
After you create a search template, you should immediately set the permissions to enable viewing. Otherwise, it does not appear among your available search templates. To edit permissions, select the template and click Permissions.
Adding session attributes
A session attribute is a session-level storage container for data that can be populated by an event. Experience Analytics supports the use of up to 64 session attributes.
You can also add the session attribute as a column in the session list template.
Complete the following steps to add a session attribute to a search template.
- Create the session attribute, including populating it with values generated by an event.
- In the Search Templates page, select the template in which to create the session attribute search field.
- Click Search Fields. The Configured Search Fields dialog appears.
- Select the Target Group from the drop-down.
If your search template does not include an appropriate group, close the Configured Search Fields dialog and click Add Group.
- Before a search field is available for use in search templates, you must create it. Click
- In the Configure Search Field dialog, specify a title for the field, which appears in the search template and in the search configuration page.
- From the Keyword drop-down, select
- The Attribute selector is displayed in the Configure Search Field dialog. Click <Select an attribute.
- Select the session attribute in the displayed list. Click Select.
- Configure the other properties as needed.
- Click Save.
- The selected session attribute is added to the search template under the selected group.
- To save changes to the server, click Save.
Adding client user interface fields
Experience Analytics UI Capture enables the capture of user interface events that occur in the visitor's browser. When deployed as part of your web application, UI Capture tracks user interface events on the client and submits XML-based requests to the web server, which enables those events to be captured and processed by Experience Analytics.
When UI Capture is deployed and configured for your web application, the following values are
inserted as variables in the
[appdata] section of the request of last viewable page
before the UI event. These variables map to search keywords that you can add to your search
[appdata]section by the Tealeaf Reference session agent.
|Request Variable||Corresponding Search Keyword||Description|
||URL as reported from the client user interface|
||Name of the application as reported from the client user interface.|
The above values may differ from the standard reference values that are inserted into the request by the Tealeaf Reference session agent, as the client user interface may contain an entire application with unique URLs within a single HTML page.