Tealeaf provides the following dimension objects.

Note: Before data is captured for these dimensions, they must be associated with a report group and the report group must be associated with an event.

Connection type dimension

For each request made to the web application, Tealeaf monitors the connection speed between the web server and the client requesting the content. By dividing the size of the response by the time it took to deliver, Tealeaf calculates a value for the connection speed.

This value is then bucketed into one of the following designations, the value for which is assigned as the dimension value for the hit:

• Dialup
• ISDN
• DSL
• T1

When data is collected for this dimension, the associated event data can be broken out by the type of connection, which may be useful in diagnosing networking issues and generating usage statistics that are based on your visitors' Internet connections.

Content type dimension

For customers who licensed Tealeaf products that are based on the licensed page model, this dimension can be used to identify activities on licensed pages. For licensed pages, this dimension value is set to PAGE. When used in your reports, you can identify activities that occur on pages that are counted toward your licensed limit as well as monitor activities on the non-counted pages.

Request canceled dimension

If the request is canceled by client or by server, this dimension value is set to True. Since transfer of data is interrupted, the resulting hit can be malformed or incomplete. This dimension is a useful means of eliminating spurious data from your report.

Traffic type dimension

When extended user agent parsing is enabled, the Traffic Type dimension is populated with a general categorization of the type of traffic sending requests to your web application.

Note: Traffic originating from mobile web browsers is identified by the value MOBILE for this dimension. This value is inserted only if CX Mobile has been licensed and enabled, and the related WURFL public standard has been made available for Tealeaf use.

• The Traffic Type dimension is populated from data extracted from the user agent string inserted into the header. Using the string, extended user agent parsing performs a lookup against a public standard to identify the type of user agent, type of traffic, and other useful data.

  Extended user agent parsing is a feature of the Tealeaf Reference session agent included in the pipeline.

  Note: This dimension must be associated with a report group and the report group associated with an event before data is captured for it.

• The Traffic Type dimension may also be populated when values detected in the HTTP_X_TEALEAF header indicate that the session is sourced from a mobile native application. In such cases, the Traffic Type dimension value is set to MOBILE_APP.

Mobile device dimension

For sessions generated from mobile native applications that are monitored by Tealeaf, the Mobile Device dimension is provided and populated with information identifying the type of mobile device from which the session originated.

Note: The Logging Frameworks, which capture user and application data from mobile native applications, are components of the CX Mobile license. If you did not license and deploy one of the Logging Frameworks, this dimension contains no data.

Sessions that are generated from one of the client frameworks 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> = UIC, iOS, or Android
• Lib/ = a hardcoded string
• <version> = the version number of the capturing framework

The header is scanned using the Mobile Device Type hit attribute, which is the source of the Mobile Device event. This event records the captured value to the Mobile Device dimension.