Like desktop browser sessions, mobile user sessions can be replayed through Browser-Based Replay in the Portal.

Browser-Based Replay replays the visitor experience with your web application. Screen size is adjusted to account for the smaller displays. JavaScript™ capabilities are curtailed to match the capabilities of mobile device browsers. Other characteristics of the mobile browser are also applied to the replay view in BBR. If UI Capture is deployed, orientation changes, scroll events, and other user interface events are represented in replay.

Through mobile replay, Tealeaf users can identify problem areas in the web application's presentation to visitors to improve it and resolve disputes.

Identify mobile web sessions from mobile devices

Tealeaf uses user agent information to identify sessions that are experienced with a mobile browser. The user agent information is submitted in each request by the browser to a web server. This capability is enabled by default for fixed user agents, such as desktop browsers. For mobile devices, more configuration is required, and a standard that is known as WURFL is used.

How the user agent information is used

When a hit is processed through the Canister, the Windows™ pipeline scans the request for the user agent information. The user agent information is then matched up against a public standard of known mobile devices.

If a match for the user agent is found in the WURFL standard, more information about the device from WURFL is inserted into the request of each hit. This information includes the screen resolution and JavaScript capabilities of the mobile browser.

Example of [ExtendedUserAgent] section of a request

This information is inserted into the [ExtendedUserAgent] section of the request.

In this example, the TLT_TRAFFIC_TYPE=MOBILE name-value pair indicates that Tealeaf Reference session agent is successfully matched the TLT_BROWSER against the WURFL public standard for mobile user agents.

[ExtendedUserAgent]
TLT_BROWSER=Openwave Mobile Browser
TLT_BROWSER_VERSION=Openwave Mobile Browser6.2
TLT_BROWSER_PLATFORM=
TLT_TRAFFIC_TYPE=MOBILE
TLT_BROWSER_JAVASCRIPT=false
TLT_BROWSER_COOKIES=true
TLT_BRAND=LG
TLT_MODEL=LG MX510
TLT_SCREEN_HEIGHT=220
TLT_SCREEN_WIDTH=176
TLT_COLOR_DEPTH=65536
TLT_PICTURE_SUPPORT=true
TLT_VIDEO_SUPPORT=false
TLT_STREAMING_SUPPORT=false

Use the example code to search for mobile sessions

Using the [ExtendedUserAgent] section of the request, you can search for mobile sessions. To improve search performance, create and use event objects through the Event Manager to identify mobile visitors.

You can use the Traffic Type hit attribute and dimension to design a search for mobile device sessions:

1. Tealeaf provides a Traffic Type hit attribute to scan the request for the value of the TLT_TRAFFIC_TYPE variable name. For example, the value for this hit attribute for the hit is MOBILE.
2. The hit attribute is used to populate the dimension Traffic Type, which can be used as a criterion for an event search term. For example, you can search for specific events where the Traffic Type dimension value is MOBILE. Searches of this type return all sessions in which the event occurred when the Traffic Type dimension indicated that it was a mobile session.
3. To locate mobile sessions, you search for an event that occurs in every session, such as Hit Count, which is also associated with the Traffic Type dimension. Whenever that event fires, the value of the Traffic Type dimension is also recorded with the event data in the request.
4. The combination of event=Hit Count and dimension=Hit Count and dimension_value=MOBILE is then used to locate sessions that Tealeaf identified as being sourced from a mobile device.