ECO 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. ECO 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: ECO 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.
-
Metric Builder provides templates for guided metric creation, cloning existing metrics, and building metrics based on specified settings.
An ECO 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, ECO 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 ECO Sensor supports events, such as page_view and network_request.
Selecting a metric widget in ECO 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
ECO 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.
| Conviva App Sensors | ||||||||
|---|---|---|---|---|---|---|---|---|
|
Android |
iOS |
JS SDK |
C SDK |
Rust |
Roku |
|||
| Min App SDK | 0.5.2 | 0.2.10 | 0.3.17 | 2.184.0.1 | 1.0.4 | 0.2.3 | ||
| AutoCollected Event | Event Source | Min Video SDK | 4.0.30 | 4.0.32 | 4.5.13 | No | No | No |
| network_request | After receiving the network request response | Autocollected, displays in ECO, Device Modeling Dashboard |
Autocollected, displays in ECO, Device Modeling Dashboard |
Autocollected, displays in ECO, Device Modeling Dashboard |
Report manually | Report manually | Report manually | |
|
screen_view |
On screen interaction, either first launch or re-launch | Autocollected, displays in ECO, Device Modeling Dashboard |
Autocollected, displays in ECO, Device Modeling Dashboard |
Not available | Report manually | Report manually | Report manually | |
|
application_error |
On error in application | Autocollected, displays in ECO, Device Modeling Dashboard |
Autocollected, displays in ECO, Device Modeling Dashboard |
Autocollected, displays in ECO, Device Modeling Dashboard |
Not available | Report manually | Report manually | |
|
button_click |
On button click callback | Autocollected, displays in ECO, Device Modeling Dashboard |
Autocollected, displays in ECO, Device Modeling Dashboard |
Autocollected, displays in ECO, Device Modeling Dashboard |
Not available | Report manually | Report manually | |
|
application_background |
When application moves to the background | Autocollected | Autocollected | Not available | Not available | Report manually | Report manually | |
|
application_foreground |
When application moves to the foreground | Autocollected | Autocollected | Not available | Not available | Report manually | Report manually | |
|
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 | |
|
deep_link_received |
On application open using the UTM URL. | Autocollected | Autocollected | Not available | Not available | Report manually | Report manually | |
|
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 | |
|
anr_stop |
When SDK gets response after triggering anr_start, anr_end is dispatched. | Autocollected | Report manually | Not available | Not available | Not available | Report manually | |
|
link_click |
On link click callback | Report manually | Report manually | Autocollected | Not available | Not available | Report manually | |
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.
|
|||
Conviva Video Events
Conviva video events (conviva_video_events) are also available using abbreviations as tag keys.
|
For This Element or Activity |
Use this ECO 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 ECO Metrics and Metadata| Category | Metrics | ||
| App Audience and Engagement |
|||
Out-of-Box ECO 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 Http Method Network Request Response Code Network Request Url Host Network Request Url Path |
Network Request Url Port Network Request Url Query Network Request Url Scheme |
|
| Events | Event Category | Event Name | |
| Errors | Error Message | Stack Trace | |
| Global Tags | Dimensions that are based on global tags. | ||
| Event Tags | Dimensions that are based on event tags. | ||
ECO Metrics