Define the attributes and event objects to capture

Before you can search for attributes and event objects, you must configure the attributes and event objects you want to capture. You can capture important data from your mobile native applications.

Replaying mobile app sessions through JSON requires configuration of the Tealeaf Logging Framework.

Identify mobile app sessions with Mobile Device

Mobile app session data from mobile native applications has specific information in the HTTP header. The header information identifies the device, framework, and version of the capturing framework.

Header information

In session data, sessions that are generated from mobile native applications are identified by the following request variable, which is inserted into the HTTP header:

HTTP_X_TEALEAF=device (<framework>) Lib/<version>

Where:

• device = a hardcoded string
• <framework> = iOS or Android
• Lib/ = a hardcoded string
• <version> = the version number of the capturing framework

For JSON-based versions of UI Capture, the header value is UIC in the format:

HTTP_X_TEALEAF=device (<framework>) Lib/<version>

Where:

• device = a hardcoded string
• <framework> = iOS or Android
• Lib/ = a hardcoded string
• <version> = the version number of the capturing framework

For XML-based versions of UI Capture, the header is the following exactly:

HTTP_X_TEALEAF=ClientEvent

Mobile Device Type hit attribute

For all client framework sessions, the header information is detected by the Mobile Device hit attribute. This hit attribute detects the values for the <framework> field.

Mobile Device dimension

The values that detected by using the Mobile Device hit attribute are recorded to the Mobile Device dimension.

Associated events

The Mobile Device dimension is preconfigured to be included in the Traffic Type report group. This report group is associated with a number of events that are provided by Tealeaf. When those events are triggered, values for the Mobile Device dimension are recorded as soon as the installation or upgrade is completed.

• The Page Count event is used as an example event for locating sessions by using this dimension. This event occurs once per session at the end of the session, which provides the means of scanning all sessions for this dimension value.

  The Page Count event is evaluated at the end of the session. It cannot be used as a means of locating mobile native application sessions among your active sessions because the event not yet fired in active sessions.

• You can use the Mobile Device dimension to locate active sessions. To locate active sessions, associate the dimension or one of its report groups with an event that occurs on the first hit of the session, every hit, after every hit, or any step-based trigger.

  You can use the Report Builder to identify the events with which a dimension is associated.

• You can associate the Traffic Type report group with other dimensions or the Mobile Device dimension with other report groups to expand access to this segmenting information.