OpenTV ENTera & OpenTV Platform Documentation
OpenTV ENTera & OpenTV Platform Documentation
Breadcrumbs

Bitmovin Analytics customer onboarding guide 

Overview 

This guide helps customers onboard to the Bitmovin Analytics platform and start monitoring playback performance, error trends, and user experience KPIs. It outlines the steps required to access the analytics dashboard, configure device-level tracking, and interpret critical KPIs used by NAGRAVISION SIT teams before release validation. 

Prerequisites 

The following account-level details and configurations are required to start using Bitmovin Analytics: 

  • Customer account ID and workspace creation 

  • Role assignment: Admin, Viewer, Developer 

  • Single Sign-On (SSO) configuration (if enabled) 

  • Customer-specific analytics key 

Steps

  1. Contact the NAGRAVISION Operations/DevOps team to request account setup. 

  2. Provide organisation details (company name and email domain). 

  3. Once the account is created, assign roles: 

    1. Admin: full dashboard and alert access 

    2. Viewer: read-only analytics access

  4. Log in to the Bitmovin Analytics dashboard here: https://dashboard.bitmovin.com/ . 

For SSO integration (optional): customers using Azure AD or Okta can integrate Bitmovin Dashboard via SAML-based SSO. Contact the NAGRAVISION DevOps team for configuration. 

For billing, access, or role-related queries, contact [email protected].

Observability and Documentation 

The Bitmovin Dashboard provides observability into performance, playback, and audience insights. Customers can refer to the official documentation: 

Key KPIs Monitored by NAGRAVISION SIT Team 

The following are the suggested KPIs to be monitored before each release to ensure playback stability and Quality of Experience (QoE): 

  • Startup Time – detects app or network-level latency. 

  • Buffering Ratio – identifies CDN or bandwidth instability. 

  • Playback Error Rate – validates app and DRM reliability. 

  • Average Bitrate – ensures adaptive streaming quality. 

  • Playthrough % – reflects user engagement and completion rate.

Filtering based on data fields 

The following table lists the suggested data fields that can be used for filtering for effective analysis and classification. This list also includes the standard and custom fields currently being used in the ION deployment context. It is recommended to verify that these bare minimum fields are available for a deployment in the respective dashboard.

Data Field

Description

Values & Usage Guidance

Application Version (Custom)

Tracks the specific version of the client application (player/app) used during the session

Useful for debugging issues introduced in recent updates

Browser

The web browser used for playback

Available browsers (common): Chrome, Safari, Microsoft Edge, Firefox

Country

The geographical country where the user is located (usually derived from IP address)

Used to analyse performance or content availability by region

Device Type

The general category of device used for playback

Examples: Phone, Tablet, Desktop, SmartTV, Game Console, Set Top Box (STB)

Platform

The specific operating system or app environment hosting the player

Examples: Web (HTML5/browser), iOS (Native App), Android (Native App), tvOS (Apple TV), Android TV, Tizen (Samsung), webOS (LG)

User Agent (Custom)

The full user agent string sent by the device/OS

Used primarily for advanced filtering and filtering by very specific device/OS versions

Customer User ID

A persistent, non-personal identifier linking the session to a specific user account in your system

Essential for linking analytics data to specific user reports or accounts (e.g., VIP user, test user)

Video Title

The human-readable name of the content being played

Examples: "Avengers: Endgame," "Season 3 – Episode 5: The Escape." Used for filtering content performance insights.

This helps the team to filter playback sessions by content name.

Video ID

A unique identifier assigned to the video asset

Examples: VID_987654, asset_f3c2d91e. Recommended for accurate, system-level filtering and asset-specific troubleshooting.

Supports debugging and troubleshooting issues related to specific video assets.

Recommended for filtering KPIs and analytics at the asset level.

Device Class

Class of device

Filter based on device class , e.g., TV, browser

IP Address

Public IP of the client

Analyse specific events originating from an IP.

ISP

ISP name

ISP name

City

Client city

Filter the events based on city.

Player version

Bitmovin player version

Filter based on player version.

Manifest URL

Content manifest URL

Filter based on URL.

Alert Configuration 

Customers can define alerts for playback degradation or failure. Recommended configurations: 

  • Startup Time > 1s – detects playback latency. 

  • Buffering Ratio > 3% – identifies buffering issues. 

  • Error Rate > 5% – detects large-scale playback failures. 

  • Bitrate < 2 Mbps – indicates poor quality delivery. 

The configuration for alert notifications is based on the guidelines in Bitmovin Alert configuration.

FAQs/Troubleshooting 

Q1: How to filter playback sessions by app version? 
→ Use customData1 = 'AppVersion_1.1.14' in Explorer filters. 
 
Q2: Before escalating playback issues, what to check? 
→ Time-to-play, buffering, error type, and correlation with CDN/DRM 
 
Q3: Should playback error codes be cross-referenced? 
→ Yes. Refer to https://bitmovin.com/docs/player/errors for decoding. 

Escalation Procedure 

Before escalation, collect the following: 

  • Error code and description 

  • Analytics session ID 

  • Device type and app version 

  • Network logs / CDN response

Escalate only if the issue van be reproduced consistently across multiple sessions.