When the Reference session agent detects a value in the HTTP_USER_AGENT request variable, the value is evaluated through a several step process.
The value evaluation steps are:
| Order | File name | Description |
|---|---|---|
| 1 | special non-valid values | If the HTTP_USER_AGENT contains blank or white space values, special values are inserted into the appropriate attributes. |
| 2 | in-memory cache | Check for the value is made to the in-memory cache maintained by the session agent. |
| 3 | UserCap.csv |
User-defined values that override any values in the public standards (WURFL.csv and BrowsCap.csv) are specified in this file, which is checked before the public standards.
|
| 4 | WURFL.csv |
Public standard for mobile devices. This file must be downloaded and converted from its native XML for use by the session agent.
|
| 5 | mobile native application | For mobile native applications monitored by Tealeaf, user agent information is automatically submitted by the Tealeaf client framework that is monitoring the application. This information is used to populate the standard extended user agent parsing properties. |
| 6 | BrowsCap.csv |
Public standard for fixed and bot user agents. This file must be converted from its native format for use by the session agent.
Generics are automatically included in the converted version of |
| 7 | UserSupplement.csv |
If no match is found in any of the above files, the session agent checks the UserSupplement.csv, which can be used to add user agents that are not currently listed in the public standard and are appearing in your capture stream. |
Blank user agent values
If the value of HTTP_USER_AGENT is a value that cannot be detected, then these values are inserted into the relevant attributes:
| Detected Value | Attribute | Inserted Value |
|---|---|---|
| "" | BrowserType |
UserAgentBlank |
| whitespace | BrowserType |
UserAgentBlank |
HTTP_USER_AGENT not found in request |
BrowserType |
UserAgentNotFound |
| Detected Value | Attribute | Inserted Value |
|---|---|---|
| "" | TrafficType |
UserAgentHeaderIsBlank |
| whitespace | TrafficType |
UserAgentBlank |
HTTP_USER_AGENT not found in request |
TrafficType |
NoUserAgentHeaderFound |
To search for TrafficType values:
- Active sessions: Search the Text in Request for
TLT_TRAFFIC_TYPE=<Inserted Value>. - Completed sessions:
- Create an event to record the value of the
Traffic Typehit attribute. - Create a privacy rule to move the
TLT_TRAFFIC_TYPErequest variable and value to the[appdata]section.
- Create an event to record the value of the