When WURFL is integrated, Tealeaf adds the WURFL data into a self-pruning cache of reference information that Tealeaf can be configured to reference.
As data passes through the Windows™ pipeline, the Tealeaf Reference session agent captures user agent strings and performs a lookup against the available public standards, including WURFL. When matches are found in WURFL, data is populated in the request and might later be evaluated by the Event Engine. This information is available for searching.
Without more information, Tealeaf provides the event objects to store captured mobile device data for search and reporting purposes.
Using dimensions, you can configure remappings of captured data values as identified through WURFL to values consistent with your enterprise practices. For example, you can create mappings to identify versions of browsers so that you can track browser type at any level of granularity.
Mobile web session traffic type
When the Tealeaf Reference session agent matches the provided user agent string against an entry in the WURFL standard, the mobile traffic type request name-value pair is defined:
The request variable
TLT_TRAFFIC_TYPE is used to populate the
Type dimension that is provided by Tealeaf. If sessions are initiated from a mobile web browser, this value is set to
You can use the
Traffic Type dimension to segment your reporting for sessions that are initiated from mobile web browsers. In the Report Builder, you add the
Type dimension and then filter the dimension to display only the
Mobile native application traffic Type
For sessions initiated from mobile native applications, the Tealeaf client frameworks submit user agent information, which is interpreted by the Tealeaf Reference session agent.
If the user agent information identifies the session as a mobile native application session, the traffic type value is populated in the request:
This value is recorded for the
Traffic Type dimension.