DPI provides a robust set of metrics to enable application performance monitoring and user behavior analysis across your web and native applications. Metric values appear as time series and distributions in metric widgets, and alongside dimensional values in the dimension drill-down tables. Selecting different metric widgets changes the metrics in the dimension tables. All metrics are calculated during the selected time interval. Use DPI metrics for a holistic view of web and mobile app health, performance, and real-user experience, unifying performance analysis with user journey optimization.
DPI supports several metric types:
-
Metrics associated with user flows: helps in the identification of crucial moments in user journeys to optimize applications and improve the user experience. For example, consider the metrics corresponding to the flow from searching for a video to successfully playing it.
-
Custom metrics associated with initial and follow up events: DPI enables three types of custom metrics.
-
Duration Metric: Measures the time interval between two events, such as the duration between the login screen event and the login success event.
-
Conversion Metric: Measures the count or conversion rates of events from one stage to another, such as the count of sessions with successful login after opening the login screen.
-
Event Aggregation Metric: Measures the number of events, or calculates the value of event attributes, such as the average duration of network requests.
-
DPI also provides bad pattern metrics such as ANR -> Exit and Crash -> Exit to quantify sequences of events that indicate poor user experiences, including repeated errors, failed interactions, and app restarts. Unlike isolated incident tracking, these metrics capture the compounded impact of problematic event chains, offering a more holistic and actionable view of user frustration.
A DPI session starts when any system or user-defined event is received and ends after 90 seconds of inactivity.
Metrics can span a specific interval or a complete session.
-
Session Metrics: Metrics based on data from events that occur throughout sessions that end within the selected time interval, for example App Video Bounce Rate metric from sessions that ended yesterday. If a session starts before the selected time interval but ends within it, the data for that session is still considered for the calculation of the session metrics.
-
Interval Metrics: Metrics based on data from events that occur within a specific interval during sessions, for example, Total Events, the cumulative count of mapped events occurring within a specific interval during sessions.
In addition to the metrics designed by Conviva to optimize your analysis, DPI supports a custom metric builder so you can create customized metrics based on your specific requirements. For more details, see Metric Builder.
Secondary Metric
As primary metrics, Conviva uses a proprietary combination of native and web applications events to provide a rich set of application performance and experience metrics. The Conviva DPI Sensor supports events, such as page_view and network_request.
Selecting a metric widget in DPI also displays a secondary metric that provides a context or related data to help you more completely understand the primary metric. Secondary metrics enhance the interpretation and analysis of primary metrics.
Secondary metrics display in the dimension panel after clicking a metric widget in the metric panel, for example Ended Session Count displays as a secondary metric for App Video Bounce Rate.
Out-of-Box Events
Check the auto-ingested events and minimum player versions for details about auto-collected event support.
Out-of-Box Events
DPI provides a robust set of metrics to enable application performance monitoring and user behavior analysis across your web and native applications. Metric values appear as time series and distributions in metric widgets, and alongside dimensional values in the dimension drill-down tables.
| Event | Event Source | ||||||||
|
Android |
iOS |
JS SDK |
C SDK |
Roku |
Rust |
React Native |
Flutter |
||
| Network request | After receiving the network request response. | Autocollected, displays in DPI, Device Modeling Dashboard |
Autocollected, displays in DPI, Device Modeling Dashboard |
Autocollected, displays in DPI, Device Modeling Dashboard |
Report manually | Report manually | Report manually | Autocollected | Not available |
| Keep alive | Page ping or periodic heartbeat are triggered at 40 seconds of interval. | Autocollected | Autocollected | Autocollected | Autocollected | Autocollected | Autocollected | Autocollected | Autocollected |
|
Screen or Page view |
Autocollected, On screen interaction, either first launch or re-launch. Also, includes Jetpack compose and fragments for Android and Swift user interface for iOS. |
Autocollected, displays in DPI, Device Modeling Dashboard |
Autocollected, displays in DPI, Device Modeling Dashboard |
Not available | Report manually | Report manually | Report manually | Autocollected | Report manually |
| App or Page Load Time | Time for the app to become active after launch | Autocollected | Autocollected | Autocollected | Not available | Report manually | Report manually | Not available | Not available |
|
Application error |
On error in application | Autocollected, displays in DPI, Device Modeling Dashboard |
Autocollected, displays in DPI, Device Modeling Dashboard |
Autocollected, displays in DPI, Device Modeling Dashboard |
Not available | Report manually | Report manually | Autocollected | Autocollected |
|
Button click |
On button click callback | Autocollected, displays in DPI, Device Modeling Dashboard |
Autocollected, displays in DPI, Device Modeling Dashboard |
Autocollected, displays in DPI, Device Modeling Dashboard |
Not available | Report manually | Report manually | Autocollected | Report manually |
|
Link click |
On link click callback | Report manually | Report manually | Autocollected | Not available | Report manually | Not available | Autocollected | Report manually |
|
Application background |
When application moves to the background | Autocollected | Autocollected | Not available | Not available | Report manually | Report manually | Autocollected | Autocollected |
|
Application foreground |
When application moves to the foreground | Autocollected | Autocollected | Not available | Not available | Report manually | Report manually | Autocollected | Autocollected |
|
Application install |
When application is launched for the first time after install (not exactly installed time) | Autocollected | Autocollected | Not available | Not available | Report manually | Report manually | Autocollected | Autocollected |
|
Deep link received |
On application open using the UTM URL. | Autocollected | Autocollected | Not available | Not available | Report manually | Report manually | Autocollected in Android; Report manually in iOS | Autocollected in Android and JS; Report manually in iOS |
|
ANR start |
When timer starts for the response from the main thread. If more than 4 seconds, event is triggered. | Autocollected | Report manually | Not available | Not available | Report manually | Report manually | Autocollected in Android; Not available in iOS | Autocollected in Android; Not available in iOS and JS |
|
ANR stop |
When SDK gets response after triggering anr_start, anr_end is dispatched. | Autocollected | Report manually | Not available | Not available | Report manually | Not available | Autocollected in Android; Not available in iOS | Autocollected in Android; Not available in iOS and JS |
| Largest Contentful Paint | Largest Contentful Paint | Not available | Not available | Autocollected | Not available | Not available | Not available | Not available | Not available |
| Custom events | Customer-defined events | Report manually | Report manually | Report manually | Report manually | Report manually | Report manually | Report manually | Report manually |
| Custom tags | Customer-defined tags in each event to carry the contextual information. | Report manually | Report manually | Report manually | Not available | Report manually | Report manually | Report manually | Report manually |
| Application version | Application version, including the build version | Autocollected | Autocollected | Report manually | Not available | Autocollected | Report manually | Autocollected | Autocollected |
| Viewer ID | Set viewer/user ID | Report manually | Report manually | Report manually | Report manually | Report manually | Report manually | Report manually | Report manually |
| Traceparent Header | Traceparent header generation | Autocollected | Not available | Autocollected | Not available | Not available | Report manually | Autocollected in Android; Not available in iOS | Autocollected in Android and JS; Not available in iOS |
| Window loaded event | Web App page view | Not available | Not available | Autocollected | Not available | Not available | Not available | Autocollected in JS; Not available in Android and iOS | Autocollected in JS; Not available in Android and iOS |
| Conviva App background before page view | Conviva App background before page view | Not available | Not available | Autocollected | Not available | Not available | Not available | Autocollected in JS; Not available in Android and iOS | Autocollected in JS; Not available in Android and iOS |
With these Video and DPI SDK versions, Conviva automatically sends video events to the DPI SDK:
| Platform | Min App SDK | Min Video SDK |
|---|---|---|
| Android | 0.5.2 | 4.0.30 |
| iOS | 0.2.10 | 4.0.31 |
| JS SDK | 0.3.17 | 4.5.13 |
| C SDK | 2.184.0.1 | No |
| Roku | 0.2.3 | No |
| Rust | 1.0.4 | No |
| React Native | 0.2.0 | No |
| Flutter | 0.3.9 | No |
Predefined Mapping Event
DPI offers a comprehensive set of predefined mapped events that enable you to create custom metrics and perform application performance monitoring and user behavior analysis on the Trends dashboard.
In the Scope column:
-
Trends and Activation: The events can be used on the Trends dashboard and all pages in Activation.
-
Activation: The events can be used on all pages within Activation.
-
Metric Builder: The events can be used on the Metric Builder page of Activation.
|
Predefined Mapped Event |
Raw Event Name |
Mapping Rules |
Scope |
|---|---|---|---|
| conviva_screen_view | conviva_screen_view | Mapped directly | Trends and Activation |
| conviva_page_view | conviva_page_view | Mapped directly | Trends and Activation |
| conviva_application_error | conviva_application_error | Mapped directly | Trends and Activation |
| conviva_network_request | conviva_network_request | Mapped directly | Trends and Activation |
| conviva_window_loaded | conviva_window_loaded | Mapped directly | Trends and Activation |
| conviva_app_backgrnd_before_page_view | conviva_app_backgrnd_before_page_view | Mapped directly | Trends and Activation |
| conviva_application_foreground | conviva_application_foreground | Mapped directly | Trends and Activation |
| conviva_application_background | conviva_application_background | Mapped directly | Trends and Activation |
| conviva_application_startup | conviva_screen_view | event_name = 'conviva_screen_view' and os_type in ('android') AND unstruct_event_com_snowplowanalytics_mobile_screen_view_1_0_0.previous_name = 'Unknown' OR event_name = 'conviva_screen_view' and os_type in ('ios', 'tvos') AND unstruct_event_com_snowplowanalytics_mobile_screen_view_1_0_0.previous_id is null | Activation |
| - | conviva_session_start | find event that triggerd a new session based on the session definition, and duplicate this event as the session start event | Metric Builder |
| - | conviva_session_end | find the session end time based on the session definition, and create a dummy event on this time point | Metric Builder |
| conviva_video_play | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.video.play | Activation |
| conviva_video_attempt | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.video.attempt | Activation |
| conviva_ad_break_start | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.ad.ad_break_start | Activation |
| conviva_ad_break_end | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.ad.ad_break_end | Activation |
| conviva_video_sdk_init | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.sdk.init | Activation |
| conviva_video_set_content_info | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.video.set_content_info | Activation |
| conviva_video_bitrate_switch | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.video.bitrate_switch | Activation |
| conviva_video_buffering | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.video.buffering | Activation |
| conviva_video_pause | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.video.pause | Activation |
| conviva_video_end | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.video.end | Activation |
| conviva_sdk_custom_event | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.sdk.custom_event | Activation |
| conviva_video_custom_event | conviva_video_events | event_name = 'conviva_video_events' AND unstruct_event_com_conviva_conviva_video_events.name = c3.video.custom_event | Activation |
| conviva_defined_error | conviva_application_error and conviva_network_request | event_name = 'conviva_network_request' AND responseStatusCode in range 500-510 OR event_name = 'conviva_application_error' AND platform = 'mob' | Metric Builder |
| app crash | conviva_application_error | event_name = 'conviva_application_error' AND platform = 'mob' | Trends and Activation |
| 5XX server error | conviva_network_request | event_name = 'conviva_network_request' AND responseStatusCode in range 500-510 | Trends and Activation |
| conviva_<element>_click | conviva_<element>_click |
Mapped directly. Note: <element> can be any UI element (such as button, link, radio_button, checkbox, and div). |
Trends and Activation |
Custom Events
| Event Type | Semantic Mapping | Metric Building | Metric in App |
|---|---|---|---|
|
Custom Events |
|
Use mapped events to build metrics. |
Metrics based on the mapped events appear in App pages. |
|
Video Seek Events: For example, to track and analyze user behaviors when seeking videos, map the custom events seek_forward, seek_backward, seek_bar_dragged_forwards, and seek_bar_dragged_backwards to an event User seek action.
|
|||
|
App Login Events: For example, to track the user login behavior and analyze the login success rate, map the event button_click with the tag key button_click_element_text and the tag value Log in to an event Login Button Click.
|
|||
Video Events
Conviva video events (conviva_video_events) are also available using abbreviations as tag keys.
|
For This Element or Activity |
Use this DPI Event Type |
Tag Keys |
Tag Value |
Platform |
Example Metrics |
|---|---|---|---|---|---|
|
Video events |
conviva_video_events |
an: asset name. avgbr: average bitrate in kbps. br: bitrate in kbps. cen: custom event name. ced: custom event data. cl: content length in seconds. clid: client ID assigned by Conviva to the physical device. err: error message. ft: isFatal, a boolean value indicating whether the error is fatal. fw: framework name in which the media player runs. fwv: framework version. iid: instance ID. When several players run on the same device, each player should have a unique instance ID. lv: isLive, a boolean value indicating whether the content currently playing is Live. mn: module name mv: module version name: device name newsc: new state change oldsc: old state change pn: player name sid: session id identifying the current session, unique on this client. sst: session start time as UNIX epoch time in milliseconds. st: session time from the session start in milliseconds. |
c3.sdk.init for Video SDK init c3.video.attempt for attempt event c3.video.end for session end event c3.video.play for play event c3.video.pause for pause event c3.video.error for error event (c3.isFatal as true/false) c3.video.buffering for buffering start event c3.video.bitrate_switch for bitrate switch event c3.video.set_content_info for metadata change c3.sdk.custom_event, c3.video.custom_event for custom event c3.ad.ad_break_start for ad start c3.ad.ad_break_end for ad end CWSStateChangeEvent for audio, subtitle, and closed captions change events |
JavaScript Android iOS Roku (coming soon, api required) |
Video Attempts Video Plays Video Start Failure Error Video Playback Failure Error |
Out-of-Box Metrics and Metadata
Quickly get started analyzing your user experiences with out-of-box metrics and metadata.
Out-of-Box DPI Metrics and Metadata| Category | Metrics | ||
| Audience and Engagement |
App Active Time (Formerly Active Time) App Sessions (Ended) (Formerly Ended Session Count) |
User Active Time (Ended) (Beta) User Active Time (Interval) (Beta) |
|
| QoE and KPI Metrics |
Mins with High App Startup Time (Beta) Mins with High Page Load Time (Beta) |
||
| Web User Experience | Avg DNS Lookup Time | ||
| Mobile User Experience |
Mins with ANR -> Restart (Beta) |
||
| Service Performance |
Mins with 0 Network Response Code (Beta) |
||
Out-of-Box DPI Dimensions
|
Category |
Metadata |
||
|---|---|---|---|
| App |
App Name Application Build Application Version |
Bundle Info Platform Sensor Version |
|
|
Device |
Browser Name Browser Version Device Hardware Type Device Manufacturer Device Marketing Name |
Device Model Device Name Device Operating System Device Operating System Family Device Operating System Version |
|
| GEO & ISP |
Cities Connection Countries |
ISPs States Zipcode |
|
| Page (Web) |
Edited Page Title First Launch Page Host Page Path Page Query |
Page Referrer Page Title Page Url Referrer Host |
|
| Screen (Mobile) |
Edited Screen Title Previous Screen Title |
Screen Title | |
| Network Request |
Network Request Endpoint Network Request Http Method Network Request Response Code |
Network Request Url Host Network Request Url Path |
|
| Events | Event Category | Event Name | |
| Errors | ANR Reason | Error Message | Stack Trace |
| Global Tags | Dimensions that are based on global tags. | ||
| Event Tags | Dimensions that are based on event tags. | ||
DPI Metrics
| Metric | Definition | Secondary Metrics | Supported Sensors |
|---|---|---|---|
| Metrics for Analyzing Only Native Applications Performance
Note: Native applications are applications installed on mobile devices or TVs. |
|||
| App Crashes |
The proportion of sessions with application crashes in a native application. This calculation divides the number of sessions containing native application crashes by the total native app session count. Note: Enabling the # mode displays the metric in number format, representing the total count of unique occurrences of the application_error event within a mobile app during the specified time interval. |
Sessions |
|
| Avg Screen Load Time |
The average duration, measured in seconds, to completely load a screen in a mobile app. The metric is calculated by dividing the total time in seconds for loading screens on a mobile app, starting from the initiation of loading screens to the completion of loading in the mobile screen, by the number of loaded screens.
Distribution: App Start Up Complete vs Avg Screen Load Time Distribution: a distribution by preset buckets, where each bucket displays the total screen loads count in a specified range for corresponding average screen load time. This distribution helps you understand screen load time and app performance, enabling you to optimize both the app and screen. |
Screen Loads |
|
| Avg App Startup Time |
The average duration, measured in seconds, for an app to start. The duration of app startup time is calculated by the Conviva sensor. The average duration of app startup time is calculated by dividing the total launch time in seconds for an app by the number of app startups.
Distribution: App Start Up Complete vs Mobile App Startup Time Distribution: a distribution by preset buckets, where each bucket displays the app start up complete count in a specified range for corresponding average duration for an app to start. This distribution helps you to identify performance issues and optimize the performance of apps. |
App Startup Count |
|
| App Startup Count |
The number of the event app launch during the specified time interval. |
N/A |
|
| ANR Count |
The total count of conviva_anr events during the specified time interval. |
N/A |
|
| Screen Loads |
The number of conviva_screen_view events with screen load time greater than 0 seconds and less than or equal to 60 seconds.
|
N/A |
|
| Mins with ANR -> Restart (Beta) |
The percentage of impacted minutes in app sessions with a conviva_anr (Application Not Responding) event followed by an app restart in less than 30 seconds. The metric is calculated as the count of impacted minutes in app sessions where a conviva_anr event occurred and the user restarted the app in less than 30 seconds, divided by the count of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total count of impacted minutes in app sessions with a conviva_anr event followed by an app restart in less than 30 seconds. |
Active Devices(Mobile) Note: This metric is filtered to include only devices with native applications installed. |
|
| Mins with Crash -> Restart (Beta) |
The percentage of impacted minutes in app sessions with application crashes followed by an app restart in less than 30 seconds. The metric is calculated as the count of impacted minutes in app sessions where an application crash occurred and the user restarted the app in less than 30 seconds, divided by the count of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total count of impacted minutes in app sessions with application crashes followed by an app restart in less than 30 seconds. |
Active Devices(Mobile) Note: This metric is filtered to include only devices with native applications installed. |
|
|
The percentage of sessions that become inactive within 30 seconds after the app fails to respond. This metric measures the count with which users end their sessions immediately after the app fails to respond, reflecting the impact on user experience. Note: Enabling the # mode displays the metric in numeric format. This indicates the total number of users who exit the session after the app fails to respond within 30 seconds. |
ANR -> Exit Init |
|
|
| Crash -> Exit |
The percentage of sessions that become inactive within 30 seconds after an app crash. This metric measures the count with which users end their sessions immediately following a crash, reflecting the extent to which the crash impacts the user experience. Note: Enabling the # mode displays the metric in numeric format. This indicates the total number of users who exit the session after the app crashes and fails to respond within 30 seconds of the crash. |
Crash -> Exit Init |
|
| ANR -> Restart (Beta) |
The percentage of the conviva_anr (Application Not Responding) event followed by an app restart in less than 30 seconds. The metric is calculated as the number of conviva_anr (Application Not Responding) events where the user restarted the app in less than 30 seconds, divided by ANR to App Startup Init. Note: Enabling the # mode displays the metric in number format, representing the total count of ANR events followed by an app restart in less than 30 seconds. |
ANR -> Startup Init |
|
| Crash -> Restart(Beta) |
The percentage of app crashes followed by an app restart in less than 30 seconds. The metric is calculated as the number of app crashes where the user restarted the app in less than 30 seconds, divided by Crash to App Startup Init. Note: Enabling the # mode displays the metric in number format, representing the total count of app crashes followed by an app restart in less than 30 seconds. |
Crash -> Startup Init |
|
| Metrics for Analyzing Only Web Applications Performance | |||
| Web Errors |
The proportion of sessions with application errors in a web application. This calculation divides the number of sessions containing web application errors by the total web app session count. Note: Enabling the # mode displays the metric in number format, representing the total count of unique occurrences of the application_error event within a web page during the specified time interval. |
App Sessions |
|
| Avg Minutes Per Page |
The average duration, measured in minutes, that users spend on each web page. The metric is calculated by dividing the total duration of time users spend on each web page by the number of pages.
Distribution: Page Load Complete Count vs Avg Minutes Per Page Distribution: a distribution by preset buckets, where each bucket displays the total page load complete count in a specified range for corresponding average minutes per page. This distribution helps you understand audience engagement with web pages and optimize them accordingly. |
Page Load Count |
|
| Hot App Launches |
The count of hot app launches during the selected interval. Hot app launches occur when an app is brought to the foreground on an application without the need to reload the entire app, as the app was already loaded. |
N/A |
|
| Page Loads |
The number of document loading activities that occurred during the selected interval. |
N/A |
|
| Page Views |
The total number of times a webpage fully loads and becomes ready for use during the specified time interval. |
N/A |
|
| Avg Page Load Time |
The average duration, in seconds, for a web application to completely load and parse the basic framework of an HTML document. This metric is calculated by dividing the total duration, in seconds, for a web application to fully load and parse the basic framework of an HTML document by the number of document loading activities. Distribution: Page Load Count vs Avg Page Load Time Distribution: a distribution by preset buckets, where each bucket displays the total document load count in a specified range of corresponding document load time. This distribution helps you understand the load performance of web applications, enabling performance optimizations. |
Page Loads |
|
| Avg DNS Lookup Time |
The average duration, in seconds, for a web application to resolve a domain name to the corresponding IP address. This metric is calculated by dividing the total duration, in seconds, that a web application takes to resolve a domain name to its corresponding IP address by the number of DNS lookup attempts made. Distribution: DNS Lookup Count vs Avg DNS Lookup Time Distribution: a distribution by preset buckets, where each bucket displays the total DNS lookup count in a specified range for corresponding DNS lookup time. This distribution helps you understand DNS lookup performance, enabling you to optimize the web application. |
Page Loads |
|
| Avg Document Response Time |
The average duration, in seconds, that the application takes to fetch HTML documents, excluding scripts and stylesheets. The metric is calculated by dividing the total duration, in seconds, that a web application takes to fetch an HTML document by the number of document responses. Distribution: Document Response Count vs Avg Document Response Time Distribution: a distribution by preset buckets, where each bucket displays the total document response count in a specified range for corresponding document response time. This distribution helps you understand document response performance, enabling you to optimize the web application. |
Page Loads |
|
| Avg Largest Contentful Paint Time |
The average duration, in seconds, for the largest content element within the viewport of a webpage to become visible to the user. The metric is calculated by dividing the total duration, in seconds, from the time loading begins to the time the largest element within the viewport becomes visible to users, by the number of loading activities. Distribution: Largest Contentful Paint Count vs Avg Largest Contentful Paint Time Distribution: a distribution by preset buckets, where each bucket displays the total largest contentful paint count in a specified range for corresponding largest contentful paint time. This distribution helps you understand loading time for largest contentful paint time and web performance, enabling you to optimize the web application. Note: The calculation of this metric depends on proper implementation of the trackPageView() API. This API should be called during any navigation events in the app. . |
Page Views |
|
| Avg Perceived Page Load Time |
The average duration, in seconds, from the moment an application starts to load the webpage to the moment when the full page, including dynamically loaded content, is drawn on the screen. This metric is calculated by dividing the total duration, in seconds, from the moment an application starts to load the webpage to the moment when the full page, including dynamically loaded content, is drawn on the screen by the number of loading activities. Distribution: Perceived Page Load Count vs Avg Perceived Page Load Time Distribution: a distribution by preset buckets, where each bucket displays the total page load count in a specified range for corresponding page load time. This distribution helps you understand the loading performance for an application starts to load the webpage to the moment when the full page, including dynamically loaded content, is drawn on the screen. Note: The calculation of this metric depends on proper implementation of the trackPageView() API. This API should be called during any navigation events in the app. . |
Page Views |
|
| Exits Before Page View |
The proportion of exits that occur before the full page is drawn on the screen. This calculation divides the number of exits that occur before the full page is drawn on the screen by the sum of the exits count and the count of complete loadings. Note: Enabling the # mode displays the metric in number format, representing the number of exits that occur before the full page is drawn on the screen during the selected interval. |
N/A |
|
| Metrics for Analyzing Web and Native Applications Performance
Note: If you integrate both your web and native applications with the Conviva sensor, these metrics are calculated using data from both types of applications. |
|||
| Active Devices |
The total number of devices that generated at least one event during the specified time interval. |
N/A |
|
| Active Users |
The total number of unique users who generated at least one event during the specified time interval. Note: When exporting Actvie Users data, each row lists the unique user ID within that time interval, while the total count reflects the number of unique user IDs within the entire query time range. In cases with repeat users, the sum of unqiue users within the intervals will be larger than the total unique user IDs. |
N/A |
|
| Network Request Count |
The total number of the network_request event during the specified time interval. |
N/A |
|
| Video Bounce Rate |
The percentage of sessions that did not include the video attempt event in an app. The metric is calculated as the count of sessions without the video attempt event in an app, divided by the count of ended sessions in the app. If the Ended Session Count metric is zero, the App Video Bounce Rate metric is set to 100% by default. Note: Need to install the Video SDK to use the metric. |
Ended Session Count |
|
|
(Formerly known as Sessions) |
The total count of sessions that occurred during the specified time interval. Note: This metrics will be deprecated soon. |
N/A |
|
| Avg Network Request Duration |
The average duration, measured in seconds, for web servers to handle network requests, including the time taken to receive, process, and respond. This metric is calculated by dividing the total duration of the entire process for web servers to handle network requests by the total number of the network_request event.
Distribution: Total Request Count vs Avg Network Request Duration Distribution: a distribution by preset buckets, where each bucket displays the total request count in a specified range for the corresponding average network request duration. This distribution helps you to identify performance issues and optimize the performance of web applications. Note: Network request is a type of web request that allows web pages to update content dynamically without requiring a full page refresh. |
Network Request Count |
|
| App Sessions (Ended) (Formerly known as Ended Session Count) |
The total number of sessions that ended during the specified time interval. Note: This metric will be deprecated soon. |
N/A |
|
| Time To First Attempt |
The average duration, measured in seconds, within a session before the first video attempt. This metric is calculated by dividing the total interval time from the “session start” event to the first video attempt event as a type of conviva_video_events by the number of sessions during which the viewer clicked play or the video auto-played generating a video attempt event.
Distribution: First Attempt Count vs Time To First Attempt Distribution: a distribution by preset buckets, where each bucket displays the count of first attempt in a specified range for corresponding average duration within a session before the first video attempt. This distribution helps you understand user engagement with videos in your app and optimize their accessibility and visibility. Note: Need to install the Video SDK to use the metric. |
App Sessions |
|
| Total Events |
The count of mapped events, including both Conviva mapped events and custom mapped events. Note: A list of mapped events can be viewed in Actviation tabs for Semantic Mapper and Management. |
N/A |
|
| User Active Time (Ended) (Beta) |
The total session lifetime active user time, in hours, of the sessions that ended during the current interval, not including the timeout window. See User Sessions. |
N/A |
|
| User Active Time (Interval) (Beta) |
The total active user session time, in hours, during the current interval, not including the timeout window. See User Sessions. |
N/A |
|
| User Sessions (Ended) (Beta) |
The number of user sessions that ended during the current interval. See User Sessions. |
N/A |
|
| User Sessions (Interval) (Beta) |
The number of user sessions that were active during the current interval, not including the timeout window. See User Sessions. |
N/A |
|
| Events per Time |
The average event count per active user hour. The metric is calculated by dividing the total number of events by the total amount of hours users spend actively engaged in a native application or a web application. Note: This metric was renamed from Total Events per User Active Hour. |
N/A |
|
|
The total time user spends in app within a single session. Note: This metric will be deprecated soon. |
N/A |
|
|
| Mins with 0 Network Response Code (Beta) |
The percentage of impacted minutes in app sessions with network request failures with a response code of 0 (response code = 0). The metric is calculated as the count of impacted minutes in app sessions with network request failures with a response code of 0, divided by the count of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total count of impacted minutes in app sessions with network request failures with a response code of 0. |
Minutes of Active Time |
|
| Mins with 4xx Network Response Code (Beta) |
The percentage of impacted minutes in app sessions with network request failures with a response code between 400 and 499 (response code = 4xx). The metric is calculated as the count of impacted minutes in app sessions with network request failures with a response code between 400 and 499, divided by the count of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total count of impacted minutes in app sessions with network request failures with a response code between 400 and 499. |
Minutes of Active Time |
|
| Mins with 5xx Network Response Code (Beta) |
The percentage of impacted minutes in app sessions with network request failures with a response code between 500 and 599 (response code = 5xx). The metric is calculated as the count of impacted minutes in app sessions with network request failures with a response code between 500 and 599, divided by the count of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total count of impacted minutes in app sessions with network request failures with a response code between 500 and 599. |
Minutes of Active Time |
|
| Mins with High Network Response Duration(Beta) |
The percentage of minutes in app sessions during which at least one successful network_request event has a response time longer than 2 seconds. A high value indicates repeated slow network performance within the app. The metric is calculated as the count of impacted minutes in app sessions during which at least one successful network_request event has a response time longer than 2 seconds, divided by the count of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total count of impacted minutes in app sessions during which at least one successful network_request event has a response time longer than 2 seconds. |
Active Devices |
|
| Network Request Failure |
The proportion of total count of failed network requests. This calculation divides the total count of failed network requests by the number of network requests. Note: Enabling the # mode displays the metric in number format, representing the total number of failed network requests during the specified time interval. DPI considers a network request as failed when the response code meets any of the conditions (OR conditions):
Note: Customer defined response codes are user-configurable and do not affect the default interpretation of 2xx (Successful responses) or 3xx (Redirection messages) unless explicitly defined.
Note: If DPI sensor cannot collect a network request response code, DPI considers the network request as null and counts it towards the total number of successful network requests. |
Active Device |
|
User Sessions
A DPI User Session refers to a series of interactions initiated based on user behavior, or custom and mapped events that trigger user session initiation.
User sessions:
-
Begin with a user event, including custom and mapped events that trigger user sessions.
-
Continue as long as any event is received before the 5-minute timeout window.
-
End when no events, including any network requests, page pings, and heartbeats, are received within the 5-minute timeout window.
Note: Sessions without user actions that consist of only network requests, page pings, and heartbeats for auto-collected events are excluded.
| Metric | Definition | Secondary Metrics | Supported Sensors |
|---|---|---|---|
| QoE and KPI Metrics | |||
| Quality of Experience Index (Beta) |
The percentage of non-impacted minutes. A minute is considered as non-impacted minute when the minute meets all of the conditions:
The percentage metric is calculated by dividing the number of non-impacted minutes by the number of active minutes. |
Active Devices |
|
| Mins Impacted (Beta) |
The percentage of impacted minutes. A minute is considered impacted if the minute meets either of the conditions:
Note: Enabling the # mode displays the metric in number format, representing the total number of impacted minutes. |
Active Devices |
|
| Mins with ANR (Beta) |
The percentage of impacted minutes in app sessions during which the conviva_anr (Application Not Responding) event occurred. The metric is calculated as the number of impacted minutes in app sessions during which the conviva_anr (Application Not Responding) event occurred, divided by the number of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total number of impacted minutes in app sessions during which the conviva_anr (Application Not Responding) event occurred. |
Active Devices |
|
| Mins with Bad Events (Beta) |
The percentage of minutes with bad events during the user's interval time. The metric is calculated as the number of minutes with bad events during the user's interval time, divided by the number of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total number of minutes with application crashes. |
Active Devices |
|
| Mins with Crash (Beta) |
The percentage of minutes with application crashes (over threshold) during the user's interval time. The metric is calculated as the number of minutes with application crashes (over threshold) during the user's interval time, divided by the number of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total number of minutes with application crashes. |
Active Devices |
|
| Mins with High App Startup Time (Beta) |
The percentage of minutes with app startup duration over the threshold during the user's interval time. The metric is calculated as the number of minutes with app startup duration over the threshold during the user's interval time, divided by the number of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total number of minutes with app startup duration over the threshold . |
Active Devices |
|
| Mins with High Page Load Time (Beta) |
The percentage of minutes with page load duration over the threshold during the user's interval time. The metric is calculated as the number of minutes with page load duration over the threshold during the user's interval time, divided by the number of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total number of minutes with page load duration over the threshold. |
Active Devices |
|
| Mins with High Screen Load Time (Beta) |
The percentage of minutes with screen load duration over the threshold during the user's interval time. The metric is calculated as the number of minutes with screen load duration over the threshold during the user's interval time, divided by the number of active minutes. Note: Enabling the # mode displays the metric in number format, representing the total number of minutes with screen load duration over the threshold. |
Active Devices |
|
Flow Metrics
| Metric | Definition |
|---|---|
|
Flow Name Init (Use the first initial event)
|
The number of first initial events within the Flow completion window, maximum 1 hour. Count the First initial event if multiple initial events happen (user configured). |
|
Flow Name Init (Use the last initial event)
|
The number of first initial events within the Flow completion window, maximum 1 hour. Count the Last initial event if multiple initial events happen (user configured). |
|
Flow Name Complete # %
|
Complete #: The number of first initial events followed by a complete event within the Flow completion window, maximum 1 hour. Complete %: Complete # / Init |
|
Flow Name Avg Duration
|
The average time from the first initial even to the complete event within the Flow completion window, maximum 1 hour. |
|
Flow Name Success # %
|
Success #: The number of completed event pairs (first initial event followed by a complete event within the configured flow success window) Success %: Success # / Init |
|
Flow Name Error # %
|
Error #: The number of errors encountered after the first initial event within the Flow completion window, maximum 1 hour. Error %: The number of Flows with errors divided by the total number of Flows (represented by Init). |
|
Flow Name Critical Error # %
|
Critical Error #: The number of errors encountered without Flow complete within the Flow completion window, maximum 1 hour. Critical Error %: The number of Flows with critical errors divided by the total number of Flows (represented by Init). |
|
Flow Name Non-Critical Error # %
|
Non-Critical Error #: The number of errors encountered despite complete within the Flow completion window, maximum 1 hour. Non-Critical Error %: The number of Flows with Non-Critical errors divided by the total number of Flows (represented by Init). |
|
Flow Name Network Request Avg Duration
|
The average network request response time after the first initial event within the Flow completion window, maximum 1 hour. |
|
Flow Name Network Request Failure # %
|
Network Request Failure #: The number of network request failures on or after the first initial event within the Flow completion window, maximum 1 hour. Network Request Failure %: Network Request Failure # / Network Request Count |
|
Flow Name Network Request Count
|
The number of network requests on or after the first initial event within the Flow completion window, maximum 1 hour. |
