Create and share workspaces and reports
Tealeaf comes with several starter workspaces of reports. One for web applications (called the "Overview" workspace) and one for native applications (called the "Mobile" workspace).
The reports in a starter workspace are populated by ready-to-use events.
The Mobile workspace is the default workspace for all first-time users.
Overview workspace for web applications
The following reports are included in the Overview starter workspace for web applications.
|Sessions||Tracks the session count by hour for the dates that you specify|
The term "bounce" means to leave.
The Bounce rate report gets populated when the One ScreenView Session Count (COUNT) event fires.
The One ScreenView Session Count (COUNT) event fires for sessions that contain only one screen view, which indicates the visitor entered the application, viewed a single page and then "bounced" (left the application), without viewing other pages.
High bounce rates might be an indicator that your site is failing to keep visitors engaged or interested.
|Session count this month||Tracks the overall session count. Each time a session ends the count increases by 1.|
|Session count by platform||Tracks the number of sessions by platform operating system (Windows, mac OS, Chrome OS) for the dates that you specify.|
|Average session size and length||
Tracks the session duration and size in seconds and megabytes by platform operating system, for the dates that you specify.
|Percentage of sessions with exceptions||Tracks the percentage of sessions where users encountered an exception error for the dates that you specify.|
|CDN total billable hits||
Tracks the number of billable hits flowing from the Akamai Content Delivery Network (CDN) to Tealeaf.
Billing is based on a million monthly interactions (MMI) metric. Tealeaf users can use the report to track Akamai data usage and modify their Akamai integration strategy as necessary.
|CDN SDK / Data||
If your organization is using the Akamai data connector, this report tracks the number of CDN hits that were received for the application.
The report allows you to determine the ratio or count of CDN hits versus SDK hits for each application.
Mobile workspace for native applications
The following reports are included in the Mobile starter workspace for native applications.
|Mobile web vs desktop||
Tracks session counts by platform (mobile web versus desktop web).
A session count by platform breaks down the number of sessions where visitors used a mobile browser versus the number of sessions where visitors used a desktop browser.
If the report shows a large disparity by platform, you might want to investigate further by viewing the visitor sessions.
|Average session duration||
Tracks the average duration of the session by platform (mobile web versus desktop web) for the dates that you specify.
Maybe sessions by one platform are noticeably shorter or longer in duration. If that is the case, you might want to investigate further.
|Screen-views per session||
Tacks the average number screen views per session by platform (mobile web versus desktop web) for the dates that you specify.
|Top mobile browsers||A list and session count of the most often used mobile browsers (Chrome, Firefox, Safari) for the dates that you specify.|
|Top mobile OS||A list and session count of the most often used mobile operating system (iOS and Android) for the dates that you specify.|
|Volume by device type||Tracks the total number of mobile sessions by device type for the dates that you specify.|
Tracks the number of orientation changes by device model (iPad, and iPhone) for the dates that you specify.
If you notice that orientation changes happen more frequently for one device over another, you might want to investigate further.
|Unresponsive gestures||Tracks the number of times the user interface does not respond to gestures that a visitor made during a session.|
|Native app crashes||Tracks the number of native mobile app crashes per day for the dates that you specify.|
|Native app device types||Tracks the session count by the device model used to access the native app.|
|App launches per region||Tracks the number of times that the mobile app gets launched, per region.|
To use the Performance workspace, it must be enabled by Acoustic from the company settings page.
If your organization already deploys events that gather performance-based data, enabling the Performance workspace can result in duplicate data in the Performance workspace reports. Consult with your Acoustic representative on how to use the Performance workspace and avoid duplicate data in your reports.
The following reports are included in the Performance workspace.
|Page render time||
Shows the average time in milliseconds it takes for pages in your application to display and be ready for visitors to interact with.
|DOM interactive time||
Shows average time in milliseconds it takes the DOM of the page to be ready. The DOM is considered ready when the HTLM for the page is loaded and parsed and the DOM is built. It is at this time the browser can begin dealing with page sub-resources.
Utilizes W3C performance data logged by the UIC
Report shows the slowest render time URLs.
|Page transition time||
Shows the average time in milliseconds between page loads for the pages in your application.
Report shows the slowest transitions between page URLs.
Requires advanced event with session attribute.
|API call round trip time||
Measures the round-trip time for various API calls configured in UI Capture.
Shows the duration in milliseconds from when the visitor’s browser sends a request to when it receives a response from your server.
Round trip time is a key performance metric for web applications and one of the main factors in measuring page load time and network latency.
Report shows the slowest round-trip time URLs.
|Slow static resource load time||
Report shows the slowest resources by URL.
|Average page response size||
Shows the average size of response data.
|Average page response speed||
Shows the average speed of response.