Sample values to create hit attributes for mobile web browsers

Sessions that are sourced from mobile web browsers are captured by Tealeaf with the UI Capture client framework. Tealeaf provides objects to detect and capture data from mobile web browser sessions.

Values for a hit attribute to detect sessions sourced from UI Capture

To detect mobile native sessions that were captured from UI Capture, you need to detect for the UIC value in the HTTP_X_TEALEAF request variable.

Below, you can see the values that you need to assign for the Start Tag and End Tag for this hit attribute:

• Start Tag:

  
  \r\nHTTP_X_TEALEAF=device (UIC)
  

• End Tag: Leave this blank.

This condition identifies that the hit was sourced from UI Capture.

You should create an event specifically to detect for the presence of this value in the CUI Hit attribute. If this value changes in the future, you can update all of your event configurations by updating the detecting event.

Values for a Mobile Web Hit event

UI Capture can be used to track client activities for fixed browser and mobile web applications. Mobile web applications are applications that are served to mobile clients that are experienced through a web browser on the client device. You might find it useful for reporting purposes to create a hit attribute and event to detect UI Capture sessions that were served from a mobile client browser.

When you create your event, you must add a condition that identifies the hit as being sourced from a recognized mobile device and submitted through UI Capture.

The Traffic Type attribute is used to detect the type of traffic, whether it is sourced from a fixed browser, mobile browser, or some form of bot traffic. When the value of this attribute is MOBILE, the hit is sourced from a mobile web browser, which also means that the session was captured by UI Capture.

When the attribute is added, your conditions for your event should look like:

Traffic type:  First Value  Equals MOBILE

The value of the hit attribute must be MOBILE exactly. Case-sensitive matching is not required.

The event must be configured to be triggered on a hit trigger (not a session trigger) and all event conditions must be met for the event to fire.

This event is now configured to fire if the hit was received from UI Capture from a mobile web browser session.

Use this event as a condition to create other events, making sure that in most cases, for proper function of the event, the hit conditions are configured so that all of the conditions are met.

Sample values to use to create hit attributes for any client framework

Hit attributes are defined in the Event Manager, which is available through the Portal.

CUI Hit attribute

The CUI Hit hit attribute checks for the presence of the HTTP_X_TEALEAF request variable and, if found, gathers the value. This request variable indicates that it was submitted from one of the client frameworks. The CUI Hit has these characteristics:

1. Name: CUI Hit
2. Description: Hit count, as reported from client user interface. Requires Tealeaf UI Capture.
3. Active: Selected
4. Search in: Request
5. Use: Start Tag/End Tag
6. Start Tag:

   
   \r\n\HTTP_X_TEALEAF=
   

7. End Tag:

   
   \r\n\
   

8. Case sensitive: Selected
9. Encoding: UTF-8
10. Change Case: No change

If the CUI Hit request variable is present, then the value of the request variable is stored as the hit attribute value.

The CUI Hit hit attribute is configured to:

• Search in the request
• Search using a start tag and an end tag.
  • Start Tag:

    
    \r\n\HTTP_X_TEALEAF=
    

  • End Tag:

    
    \r\n\
    

In the Start and End tags, the string \r\n is used to reference a return/newline that signals the ending of one line and the beginning of a new one in captured data. When the request is scanned and the \r\nHTTP_X_TEALEAF= string is detected, all values between that string and the end tag string (\r\n, which indicates the end of the line) are gathered as the value for the hit attribute CUI Hit.

Whenever CUI Hit is used for other event objects evaluated on the same hit, the value captured by the hit attribute is value that is used.

When the next hit arrives in the Event Engine, the hit attribute is retested, and potentially a new value is stored in CUI Hit for reference.

Differences from Mobile Device hit attribute

You might notice that the Mobile Device hit attribute is also scanning the HTTP_X_TEALEAF request variable.

• The Mobile Device hit attribute is interested in only the values between the two parentheses in the request value.
• The CUI Hit hit attribute gathers all values until the end of the line. Therefore, it gathers a much wider data set and can be used as a test of whether the hit was sourced from any Tealeaf client framework.

Sample values to create events to detect messages from mobile native application sessions

Based on the event objects provided and that you created, you can detect for sessions that were sourced from one of the mobile client frameworks or from a specific client framework.

Example event to detect messages from any mobile client framework

If you are creating events to monitor data from any mobile client framework, use the Mobile Device Type hit attribute as an event condition. Set the operator to be Hit Attribute Found

In this example, the event conditions are defined to detect for the presence of the Mobile Device Type and a user-defined attribute, Mobile Alert Message. When both attributes exist, the event fires when a mobile alert message is sourced from one of the logging frameworks for mobile devices.

Example event to detect a specific mobile client framework

You can also create events to track activities from a specific client framework.

For example, suppose you want to monitor mobile alert messages from your iOS application, independently of those of a deployed Android application. In this case, you define your event conditions to detect for the presence of a specific value for the Mobile Device Type:

You may want to create an event that detects for the specific value for the Mobile Device Type hit attribute and records that value. You might name that event something like Mobile Session - ios.

Sample values used to detect mobile web sessions

Some sessions that are initiated by mobile devices might not be captured by the android or iOS frameworks. Depending on your web application, it might be possible for visitors to interact with your web application using a mobile web browser. Sessions that are initiated in this manner are not detected and processed through the Logging Frameworks.

These types of interactions apply to CX Mobile for Mobile Web.

Capture and detection of sessions that are sourced from mobile web browsers requires UI Capture.

Sessions from mobile web browsers that are captured from the UI Capture solution are detected by extended user agent parsing, which generates the data to report them as MOBILE sessions in the Traffic Type hit attribute, which is the source for the Traffic Type dimension.

This event might already be created.