Through WURFL reference data, Experience Analytics can be configured to identify mobile visitors. You can configure Experience Analytics to detect mobile visitors and to generate events to detect them.
Note: The CX Mobile module is a separately licensed module of the Experience Analytics CX platform. For more information, contact your Experience Analytics representative.
Enable extended user agent detection
To identify mobile visitors through WURFL reference data, you must enable User Agent Detection.
Import CX Mobile Dashboard
The CX Mobile module includes a suite of events for mobile visitors. These events can be imported with the Mobile Traffic Dashboard, which must be imported into your Experience Analytics solution.
How mobile visitors are detected
When extended user agent detection is enabled, the data relevant to mobile devices is captured and inserted into the
[ExtendedUserAgent] section of request by the Tealeaf Reference session agent.
The Tealeaf Reference session agent must be enabled in your processing pipeline.
Information inserted into the request
When the Tealeaf Reference session agent detects a mobile session, the WURFL standard is checked and any available information is inserted into the request.
This code is an example of the
[ExtendedUserAgent] section of request:
How self-reporting mobile web browsers are identified
Self-reporting mobile browsers are identified in the Canister based on the value of the extended user agent variable.
TLT_TRAFFIC_TYPE=MOBILE value is set to
MOBILE, the user agent is a mobile device. This value is used to populate the provided session attribute
Browser Traffic Type, which contains the value
MOBILE for these self-reporting mobile browsers.
This session attribute can then be referenced in your event definitions.
Identify mobile web applications by
Traffic Type dimension
With the Android and iOS logging frameworks, you can use the
Traffic Type dimension to identify sessions that were captured.
You must have licenses to use the
Traffic Type dimension to identify sessions.
These client frameworks submit user agent information for capture by Experience Analytics. The Tealeaf Reference session agent interprets the user agent information and populates the
[ExtendedUserAgent] section, including the
When this value is set to
MOBILE_APP, the user agent is a mobile native application.
This value is displayed in the
Traffic Type dimension.
Define mobile browser-based session events with the Event Manager
Through the Event Manager, you can define events that apply only to mobile browser-based sessions.
By including this condition in your event definition, the event is triggered only for mobile browser sessions.
For example, implement eventing, if the condition is set to test for the Browser Traffic Type session agent that is equal to MOBILE. This event tests for all conditions to be true for the event to fire. You can add other conditions to the event to create events that apply to mobile-only sessions.
For each event that you create for mobile browsers, you must add the session agent as a test condition to restrict the test to only mobile-sourced sessions.
Use the Traffic Type dimension to identify sessions from self-reporting browsers
You can use the provided
Traffic Type dimension to filter your reports to display only information from sessions that are sourced from self-reporting mobile browsers.
Traffic Type dimension is added to the report, you can filter the dimension to display one of the following values to report on events and ratios for mobile web or mobile native application sessions.
|Traffic Type Dimension Value||Description|
Session was initiated from a mobile web browser and was captured by UI Capture.
Session was initiated from a mobile native application and was captured by a client framework.
Traffic Type dimension is sourced from the same information on the request as the
Browser Traffic Type session attribute.
Dimension value lists
You can enable logging on dimensions to collect lists of data. You can modify the data set and reuse it in dimension reports.
To support the set of lists, you can enable logging on the dimensions you create to gather data. This data can then be downloaded through the Event Manager to your local system, where you can normalize the data and add or remove values. This list of values can then be reloaded into the dimension as a whitelist.