Metrics

The Conviva Metric Dictionary provides a comprehensive list of definitions for the VSI Video metrics. This dictionary should be your single source for Conviva VSI metric definitions.

To access metric definitions, login to Pulse or reach out to your Conviva representative for access.

Conviva Video Metrics

Out-of-Box VSI and DPI Dimensions

For a complete understanding of a metric value, it is important to consider not only the metric calculation, but also the interval of the data and how the metric impacts viewer experience. You can use this page to learn about Conviva's metric intervals and click a link to view a specific metric definition.

• Conviva Metric Intervals

• Metric Mutability for CDN and Resource Dimensions

Highlight Conventions:

Proper metric names are highlighted with italic and initial upper case. The components of the metric definitions and metric events are highlighted with italics.

Conviva Metric Intervals

VSI Video metrics support real-time data and data intervals for comprehensive analysis of Conviva's video analytics.

Real-Time Data

Conviva continuously calculates real-time data based on a continuous stream of heartbeats from devices used by active viewers. Each data point aggregates the previous 60 seconds of data collected. In our Pulse user interface, real-time data is refreshed every 20 seconds.

Remove Data Dip for Partial Data in the Last Time Series Data Bucket

For example, the date picker sets the range from 14 July at 1:30 pm to 14 July at 4:37 pm with a granularity of 5 minutes. The last time series data bucket spans from 4:35 pm to 4:37 pm, resulting in only 2 minutes of data, which would likely cause a dip in the time series due to partial data availability. Therefore, the partial data in that data bucket, which would cause an observable drop or dip in the last data bucket in the time series, is no longer shown.

Interval Data

Conviva computes Live, 1-minute, hourly, and other interval data, and aggregates data for longer intervals.

For Trends page granularity, see Time Granularity.

For aggregated data, a session is counted toward a metric in different intervals depending on the metric type.

For aggregated data, metric aggregation occurs in different intervals depending on the metric type.

Dashboard Interval Display

Most pages display computed 1-minute data intervals, along with the option to display data aggregated for 2-hour, 1-day, and 1-month intervals.

Session Timeout/Expiration

Sessions expire if no heartbeats are received for more than 120 seconds.

Session Expiration and Revived Session Handling

If a session does not receive a heartbeat for 120 seconds (2 minutes), Conviva generates a session expired event and treats the session as ended. Session expired events appear in the Viewer Timeline.

If the session revives after a 120 second lapse in heartbeats and restarts sending additional heartbeats, Conviva continues to monitor the session and considers the revived session a separate session, but with the same session ID.

The session start time distinguishes the sessions having the same session ID. Metrics and event durations are computed separately for the initial and revived sessions. These metric differences for a revived session (that is, a continuously-monitored session that follows a prior expired session with the same session ID) are noted in the metric dictionary definitions and include:

• Revived sessions don’t contribute to VST, because their startup behavior is often unusual.

• Revived sessions that fail to play don’t contribute to any metrics, including VSF and EBVS.

• Revived sessions that play successfully contribute to Attempts, Plays, and Ended Plays.

Geolocations

Conviva supports geographic locations for country and subdivision, based on the country and subdivision levels.

Metric Mutability for CDN and Resource Dimensions

When filtering by CDN and Resource dimensions, the displayed metric totals depend on the metric mutability type when more than one CDN/resource was used during the session.

As a result, the metric totals in Trends may not match the sum of each of the CDN/Resource metrics with different mutability types, such as Attempts with Ended Plays, Plays, Interval Playing Time.