you to cordon off test and other staging integrations
from actual production integrations for analytical purposes. So, while creating your iOS or Android integration, you can exclude data from these integrations
from actual live productions.
You will add each video as a separate integration.
To start, click Add Integration within an Environment,
and you’re taken to the screen shown on Figure 1 to
choose a software development kit (SDK). As you can
see, Mux currently has integrations with the HTML5
Video Element; Video.js (which also supports Brightcove players version 5.x); JW
Player 7; Bitmovin Player 5.x, 6.x, and 7.x;
Ooyala Player V4; THEOplayer 2.x (in beta);
iOS 8+ and tvOS 9+ (Objective-C); and Exo-Player v2 (in beta). If Mux doesn’t currently
support your player, it will either create the
integration for free or provide documentation and support for your own developers, which the company states should take
a day or so.
Integration complexity varies by SDK.
For my tests, I added Mux Data to a simple
HTML5 player in about 10 minutes (see
Figure 2), aided by a useful You Tube video produced by Mux co-founder Steve Heffernan
( go2sm.com/muxintegration). There are two
aspects to the link. The first script (to mux.
js) ties the video to the Mux system. The second allows you to add metadata to the integration, either for informational purposes
or to provide details about the video or environment that can’t be detected by the Mux
system and may help diagnose problems.
For example, you can use the experiment
name field to separate different configuration experiments when implementing a
new player or debugging a problem. You
can also add video titles and IDs to quickly
identify video-specific problems.
Data Tracking and Reporting
Mux tracks a number of common metrics
like time to first frame, exits before video
start, player and page load time, playback
failures, rebuffer frequency and percentage,
and seek time, as well as metrics like upscale
and downscale percentage. As you’ll see in
more detail in a moment, Mux can sort this
data by dimensions like browser and browser version, country, and OS, as well as via
much of the metadata added to the video,
like player name and version, video title, etc.
Data is collected continuously and is updated to the analytics about 2 minutes after
playback ends. You access the metrics in the
Mux system via the screen shown in Figure
3 on page 168, although you can also access
the data via an application programming interface (API) to view or to integrate it into
your internal systems ( go2sm.com/muxapi).
Choose a player software development kit.
Adding Mux to a simple HTML5 player