Skip to Content
Mux Docs: Home

Monitor THEOplayer

This guide walks through integration with the THEOplayer Android SDK to collect video performance metrics with Mux data.

This documents integration instructions for THEO Technologies' THEOplayer library

The Mux integration with THEOplayer is built on top of Mux's core Java SDK, and the full code can be seen here: muxinc/mux-stats-sdk-theoplayer-android.


The following data can be collected by the Mux Data SDK when you use the THEOplayer Android SDK, as described below.

Supported Features:

  • Engagement metrics
  • Quality of Experience Metrics
  • Available for deployment from a package manager
  • Custom Dimensions
  • Average Bitrate metrics and renditionchange events
  • Ads metrics

renditionchange events are tracked, bitrate metrics are not available

1Install the Mux Data SDK

Add the Mux SDK to your project using one of the following approaches:

Add Gradle dependency on the Mux THEOplayer SDK (preferred)

Add the Mux Maven repository to your Gradle file:

repositories {
maven {
url ""

Next, add a dependency on the Mux Data THEOplayer SDK.

The current version is v0.2.0. Additional releases can be found on our releases page.

implementation 'com.mux.stats.sdk.muxstats:muxstatssdktheoplayer_v5:[CurrentVersion]'

2Initialize the monitor with your THEOplayer instance

Get your ENV_KEY from the Mux environments dashboard.

Env Key is different than your API token

ENV_KEY is a client-side key used for Mux Data monitoring. These are not to be confused with API tokens which are created in the admin settings dashboard and meant to access the Mux API from a trusted server.

First, create the CustomerPlayerData and CustomerVideoData objects as appropriate for your current playback, and be sure to set your ENV_KEY.

import com.mux.stats.sdk.core.model.CustomerPlayerData;
import com.mux.stats.sdk.core.model.CustomerVideoData;
import com.mux.stats.sdk.core.model.CustomerViewData
import com.mux.stats.sdk.core.model.CustomData;
import com.mux.stats.sdk.core.model.CustomerData;
CustomerPlayerData customerPlayerData = new CustomerPlayerData();
CustomerVideoData customerVideoData = new CustomerVideoData();
CustomerViewData customerViewData = new CustomerViewData();
CustomData customData = new CustomData();
CustomerData customerData = new CustomerData(customerPlayerData, customerVideoData, customerViewData);

Next, create the MuxStatsSDKTHEOPlayer object by passing your Android Context (typically your Activity), a THEOplayerView instance, a player name, and the customer data objects.

import com.mux.stats.sdk.muxstats.MuxStatsSDKTHEOPlayer;
// Make sure to monitor the player before calling `prepare` on the THEOplayer instance
muxStatsTHEOplayer = new MuxStatsSDKTHEOPlayer(
this, player, "demo-player", customerData);

In order to correctly monitor if the player is full-screen, provide the screen size to the MuxStatsSDKTHEOPlayer instance.

Point size = new Point();
muxStatsTHEOPlayer.setScreenSize(size.x, size.y);

In order to determine a number of viewer context values as well as track the size of the video player, set the player view.


Finally, when you are destroying the player, call the MuxStatsSDKTHEOPlayer.release() function.


After you've integrated, start playing a video in your player. A few minutes after you stop watching, you'll see the results in your Mux data dashboard. Login to the dashboard and find the environment that corresponds to your env_key and look for video views.

3Add Metadata

In the Java SDK, options are provided via the objects within the CustomerData object.

All metadata details except for envKey are optional, however you'll be able to compare and see more interesting results as you include more details. This gives you more metrics and metadata about video streaming, and allows you to search and filter on important fields like the player version, CDN, and video title.

For more information, see the Metadata Guide.


Changing the video

There are two cases where the underlying tracking of the video view need to be reset. First, when you load a new source URL into an existing player, and second when the program within a singular stream changes (such as a program within a live stream).

Note: You do not need to change the video info when changing to a different source of the same video content (e.g. different resolution or video format).

New source

When you change to a new video (in the same player) you need to update the information that Mux knows about the current video. Examples of when this is needed are:

  • The player advances to the next video in a playlist
  • The user selects a different video to play

This is done by calling muxStatsTHEOplayer.videoChange(CustomerVideoData) which will remove all previous video data and reset all metrics for the video view. See Metadata for the list of video details you can provide. You can include any metadata when changing the video but you should only need to update the values that start with video.

It's best to change the video info immediately after telling the player which new source to play.

New program (in single stream)

In some cases, you may have the program change within a stream, and you may want to track each program as a view on its own. An example of this is a live stream that streams multiple programs back to back, with no interruptions.

In this case, call muxStatsTHEOplayer.programChange(CustomerVideoData). This will remove all previous video data and reset all metrics for the video view, creating a new video view. See Metadata for the list of video details you can provide. You can include any metadata when changing the video but you should only need to update the values that start with video.

Detect when a video is being played full-screen

For most use cases, the SDK is capable of detecting whether or not a video is being played full-screen. Specifically, it can do so in the case where the player view is the same size as the device display (excepting ActionBars and other framework window decoration).

For other uses cases (non-overlaid controls, window decoration via plain Views, etc) you may need to tell the SDK when the user switches to full-screen.

public void onCreate(@Nullable Bundle savedInstanceState) {
// If you are using SimplePlayerView, StyledPlayerView, etc
theoPlayerView = findViewById(;
theoPlayerView.getFullscreenManager().addFullscreenChangeListener(new FullscreenChangeListener() {
public void onEnterFullscreen() {
public void onExitFullscreen() {

Error tracking

By default, Mux's integration with THEOplayer automatically tracks fatal errors as thrown by THEOplayer. If a fatal error happens outside the context of THEOplayer and you want to track it with Mux, you can call muxStatsTHEOplayer.error like this:

// Error code: integer value for the generic type of error that
// occurred.
// Error message: String providing more information on the error
// that occurred.
// For an example, the HTML5 video element uses the
// following:
// for codes and messages. Feel free to use your own codes and messages
int errorCode = 1;
String errorMessage = "A fatal error was encountered during playback";
MuxErrorException error = new MuxErrorException(errorCode, errorMessage);

Note that muxStatsTHEOplayer.error(MuxErrorException e) can be used with or without automatic error tracking. If your application has retry logic that attempts to recover from THEOplayer errors then you may want to disable automatic error tracking like this:


It is important that you only trigger an error when the playback has to be abandoned or aborted in an unexpected manner, as Mux tracks fatal playback errors only.

Release notes

Current release


  • Add support for THEOplayer v7
  • fix: NullPointerException with getPlayerData() inside MuxStats (#29)

Previous Releases


  • Support THEOPlayer v5 and higher


  • Update THEOplayer to 2.92.0 (#18)


  • Update to MuxCore 7.0.10
MuxCore Fixes
  • Fix event-handling errors in rare cases


  • Initial release

Was this page helpful?