Concurrent Plays is a time-trended metric with multiple data points during each interval. The data points measure the number of Concurrent Plays or simultaneously active sessions in 60-second data buckets throughout the interval. The maximum number of concurrent plays from any of the 60-second data buckets determines the number of concurrent plays during that interval. The Concurrent Plays metric only counts active sessions where the video has started playing before or during the data bucket and does not include sessions with rebuffering, pause, and other trick modes. Trick modes typically include rebuffering, pause, and other non-playing states that exceed a defined inactivity limit.
Each data bucket aggregates the previous 60 seconds of data, starting with 0 to 59 as the first bucket in a session.
The data buckets are analyzed across the intervals, with 60 data buckets in an hourly intervals and 1440 buckets in a daily interval.
Monitoring concurrent video plays is important to help you define your audience, determine video quality, and track which customers are actively engaged with a video.
Real-Time
For real-time data, the Concurrent Plays metric is the maximum number of active sessions in the 10-second bucket (with not more than 30 seconds latency), so you can also view data for any dimension group.
For aggregated intervals, Concurrent Plays is a snapshot of the maximum number of simultaneously active sessions for the displayed 15 min data.
This metric is an ‘Interval’ type metric and is presented as a summary and time series.
- Concurrent Plays summary: the maximum number of all the Concurrent Plays in the selected time period.
- Concurrent Plays time series: a time series for the selected time period, where each point is the maximum number of Concurrent Plays in that specific interval.
Note: When the value in this metric goes below the threshold, the value flashes red, indicating a low bitrate and a degraded viewer experience.
Related Details
|
Metric Details |
Description |
|
Dashboards and Metric Presentation |
|
|
Dimensions |
Use MetricLens dimensions to group this metric by metadata segments for enhanced root cause analysis. For example, grouping data for specific ISP and player dimensions can create month-over-month comparisons of Concurrent Plays between provider and player types. |
|
Diagnostics |
Analyze this metric by specific dimensions to understand the impact across multiple dimensions. For example, focusing the data on specific dimensions, such as operating system and city, can narrow the root cause of differences in Concurrent Plays to a known location and operating system. |
|
Manual Alert Support |
Yes. Configure alerts to receive proactive notification when Concurrent Play meets set levels. For more information, see Alerts. |
|
AI Alert Support |
Yes (The availability of AI alerts for concurrent plays is limited. To enable this feature, please contact your Conviva representative.) |
|
Metric Adjustments |
The metric excludes unsuccessful attempts, and Conviva sanitizes the active sessions to eliminate prolonged rebuffering and other modes indicating that the viewer may have disengaged from the video. Due to differences in data ingest and processing across granularities, occasional variances of about 1-2% may occur between minute, hourly, and daily Concurrent Plays metric data. |
For more metric definitions, see the Metric Dictionary.