When the events are enabled, instances of event data can be counted, or the data values can be broken out for reporting.
Through the Portal, you can create analysis of events. Through the Portal, select Analyze > Report Builder. The list of available menu options are displayed.
Report | Description |
---|---|
Average Session Size and Length by Platform | Shows the average session size in MB per mobile session count and the average mobile session length in seconds per session count. Data is filtered by platform. |
Exceptions by Day and Platform | Shows the number of exceptions for a mobile application. the data is filtered by day and by platform. The report also provides an hourly average of exceptions. |
Exceptions by ScreenView | Shows the exceptions for a mobile application. Data is filtered by ScreenView. |
Percentage of Sessions with Exceptions | Shows the percentage of mobile application sessions that had exceptions. |
Resizes by ScreenView | Shows the number of mobile sessions that logged resize gestures. Data is filtered by ScreenView. |
Session Count by Date | Shows the number of mobile sessions that are logged by date. |
Session Count by Day and Carrier | Shows the number of mobile sessions logged by date. Data is filtered by mobile carrier. |
Session Count by Hour | Shows the number of mobile sessions that are counted by hour. The report also provides an average of session counts for the previous four days of the week as the current report. |
Session Count by OS Version | Shows the number of mobile sessions counted. Data is filtered by OS version. |
Session Count by Platform | Shows the number of mobile sessions per hour for the current day. Data is filtered by platform. |
Unresponsive Gesture Struggles by ScreenView | Shows the number of unresponsive mobile gesture struggles. Data is filtered by ScreenView. |
Unresponsive Gesture Struggles by Day and Platform | Shows the number of mobile gesture struggles. Data is filtered by day and platform. |
Reports for mobile web
You can generate reports about mobile devices by filtering data based on the type of device. This information applies to sessions initiated through mobile web browsers to your web application.
For example, suppose that you are able to identify mobile users by device type. Through Tealeaf reporting, you discover that mobile users are predominantly creating one-page sessions, meaning that they view a single page on your website before leave. Which pages are viewed the most by mobile visitors in one-page sessions: login, status update, or other?
- If mobile visitors are hitting only the login page, perhaps there are functional problems with the page that are preventing mobile users from accessing the site.
- If visitors are hitting a status update page, then content to that page can be tailored for maximal effect for mobile users with more links to useful pages deeper in the site.
Based on the reference data for mobile devices and the events that are created to monitor them, you can create event-based reports to identify mobile activities. In the Report Builder, you can create reports that are filtered by the Traffic Type
dimension, which can be used to identify sessions that are initiated from a mobile browsing device.
These reports can then be integrated as components in custom dashboards.
Traffic Type Dimension Value | Description |
---|---|
MOBILE |
Session was initiated from a mobile web browser and was captured by CX UI Capture for AJAX. |
MOBILE_APP |
Session was initiated from a mobile native application and was captured by a client framework. |
Reports for mobile apps
The Tealeaf mobile app logging frameworks enable the capture of a large array of device properties and user interface events into Tealeaf, where these values can be made available for reporting.
Using data that is sourced from Tealeaf logging frameworks, you can create event objects, such as hit attributes, dimensions, and events, to capture this data for reporting purposes. When the objects are created, you can use them in the same reports that are described at the end of section. You can also use them in reports that are already created.
Prerequisites
Tealeaf CX Mobile for Mobile App uses one or more Tealeaf logging frameworks, which must be deployed and configured with the mobile native applications deployed to your visitors. You must download and deploy these frameworks before you can report on mobile applications.
Transmission method
Step-based eventing: The logging frameworks submit messages in a unified JSON format. These messages are inserted into the request, from which you can create attributes and events.
Event objects
Tealeaf provides a set of step attributes and events to support the tracking of user interface events that are captured through a client framework. These objects can be used as the basis for building other event objects for tracking the specifics of your client application.
Report data
To track mobile native application events and data, you create attributes, events, and dimensions. You use the attributes, events, and dimensions to build reports, or you can use objects in reports that you already created in the Report Builder.
Dimensions and events
For tracking purposes, dimensions, such as the Mobile Device
dimension, must be associated with events before dimensional data can be recorded for the events. By default, this dimension is associated with some Standard Events. Before you track event activities by mobile device type, this dimension must be associated with those events first, and event instances must be detected and recorded.
Track variations
For events captured from mobile native applications, you might want to track variations in reported values. For example, you want to identify changes in reported hit counts for the mobile native applications, which might signal disinterest with the application.
Through the Event Manager, you can create Top Movers to track variations in reported values for specific events or dimensions. These Top Movers can be configured to be calculated on hourly or daily intervals.
When Top Movers are created and capturing data, you can create and review reports on Top Movers through the Portal. These easy-to-use reports provide a basic mechanism for tracking variations in captured values on key metrics that are related to application health. You can display multiple Top Movers of your mobile native application data to monitor basic changes in customer interactions with it.
Drill-down search for data
From either Top Mover or Report Builder reports, you can drill into the report to explore individual sessions.
- From the Top Mover report, use links in the data table to open the Report Builder with a report on the underlying event or dimension that is displayed by using the appropriate date range.
- From the Report Builder report, use the links in the data table to open a session list. It contains the sessions that are supporting the data reported in the link you clicked.
From the session list, you can explore individual sessions, including locating the exact hit where the event or dimension was recorded.
Portal search
You can also search sessions that are containing individual events or event + dimension combinations through the Portal.