Articles in this section

See more

THEOplayer

Avatar
Tony Gentile
  • Updated
Follow

Datazoom is a high-availability real-time data collection solution. This document summarizes how to integrate the THEOplayer player with the Datazoom platform.

Login to Datazoom here:  https://app.datazoom.io
1 - Sign in.png

Add a Collector as indicated here:  How to add a Collector

2 - Select Collectors to edit-2.png


Copy the CONFIG ID to be used in the subsequent steps

Copy icon.png


Plugin Integration

Datazoom provides plugins for data collection through our Beacon Services. Integrate the THEOplayer plugin into your web application with the following snippet:

<script src='https://platform.datazoom.io/beacon/v1/config?configuration_id=CONFIG_ID'></script>

  • Insert this JS line into your HTML

  • Replace the CONFIG_ID value with the collector configuration ID.

This inserts Datazoom's data collection SDK into the page.

Activate Data Collection for a THEOplayer

To activate data collection for a THEOplayer instance, create a Datazoom context which references the player instance with the following snippet:

datazoom_context = datazoom.createContext(theo_player);

For example:

<!DOCTYPE html>
<html lang="en">

<head>
    <link rel="stylesheet" type="text/css"
        href="https://cdn.myth.theoplayer.com/60b5ca02-a9e7-42b3-aab8-e008a4dfece4/ui.css">
    <!-- THE THEO PLAYER CDN -->
    <script src="https://cdn.myth.theoplayer.com/60b5ca02-a9e7-42b3-aab8-e008a4dfece4/THEOplayer.js"></script>
    <!-- THE DATAZOOM BEACON SCRIPT -->
    <script src='https://platform.datazoom.io/beacon/v1/config?configuration_id=CONFIG_ID'></script>
</head>

<body>

    <div>
        <div id="video" style="width:50%">
            <div class="video-js theoplayer-skin vjs-16-9"></div>
        </div>
    </div>

    <script>
        var theo_player;
        var datazoom_context;

        var url = "https://dash.akamaized.net/akamai/bbb_30fps/bbb_30fps.mpd";

        // Create a Player instance and replace license with your license key.
        theo_player = new THEOplayer.Player(document.getElementById("video").children[0], {
            libraryLocation: "https://cdn.myth.theoplayer.com/60b5ca02-a9e7-42b3-aab8-e008a4dfece4/",
            license: "xxxxx-xxxxxx-xxxxx-xxxxxxx-xxx"
        });

        theo_player.source = {
            sources: [{
                src: url,
                type: "application/dash+xml"
            }]
        };
        //Activates data collection
        datazoom_context = datazoom.createContext(theo_player);
    </script>

</body>

</html>

Stop Data Collection

If the data collection must be stopped for any reason, for example after the destruction of the corresponding player instance, invoke the destroy() method of the Datazoom context object as in the following example:

if (theo_player) {
    theo_player.destroy();
    theo_player = null;
}

if (datazoom_context) {
    datazoom_context.destroy();
    datazoom_context = null;
}

NPM (Node Package Manager)

We have made it convenient to manage your THEOplayer Collector integration by providing NPM (Node Package Manager) support. Please see installation details here.

References:

THEOplayer API Doc : https://docs.theoplayer.com/getting-started/01-sdks/01-web/00-getting-started.md

To enable CMCD on THEO player requires THEO’s CMCD connector plugin library. Please contact THEO.

CMCD Support

Datazoom provides two discrete settings that control CMCD data collection, one for a specific player event, “Media Object Request”, and one for the corresponding CDN log response.

Player Collector configuration options

Use this option to enable your configured CDN to collect and return CMCD data, contained in the CMCD node of the log line JSON

  • Off - no CMCD keys are passed

  • Lite - only the CMCD keys Session ID (sid) and Request ID (rid) are passed to the CDN via query parameter or request header with every “Media Object Request”.

  • Full - the full set of keys specified by the CMCD standard are passed to the CDN via query parameter or request header with every “Media Object Request”

    Screenshot 2024-04-18 at 1.49.13 PM.png

Bitmovin and JW Player support only the “Lite” setting above

Data Pipe configuration options

Select the CMCD data points you wish to be included in content requests.

  • Media Object Request - The video player will emit an event called “media_object_request” that will contain the selected CMCD keys below

  • CMCD keys - Select the CMCD keys you wish to have included with each Media Object Request


Ad Support - client side ads

Datazoom provides data collection options for Google IMA and Freewheel. By using the integration options described below you can collect a number of ad related events and related metadata to further understand ad performance.

Freewheel

To enable a Datazoom collector to capture the ad related data points, the required steps for a web application differ depending on how the ad framework (e.g., Freewheel) is integrated with the video player. In general, there are two types of integration method between the video player and ad framework:

1. Leverage ad framework integration supported by the video player

Players such as Akamai AMP player, JW Player, THEOplayer, … etc., support Freewheel ad integration as a part or an optional module of the player. Since the corresponding Datazoom collector for the player is prebuilt with knowledge of the player’s ad related features, for a web application who simply leverages the video player for ads, no additional code is required to enable ad data collection in this scenario.

A web application may choose to utilize the video player for the purpose of content presentation only, while building its own ad implementation by utilizing the ad framework directly. In these use cases, the video player has no awareness of the ad implementation and therefore it will fall under the second scenario described below.

2. Ad implementation external to the video player

Players that mainly focus on core playback/streaming functionalities, such as HLS.js player, Dash.js player, or the native HTML5 <video> element, often do not come with ad integration features. For a web application who likes to enable ads independent of the video player, it can choose to utilize the ad framework library (e.g., Freewheel MRM AdManager SDK) directly or bring in some third-party components. In either cases, since it is impossible for the corresponding Datazoom collector to gather ad information through the video player, some provisioning steps (see the section below: Attach the Freewheel Context) will be required to enable ad data collection.

Attach the Freewheel Context

For a web application who enables ads by utilizing Freewheel MRM AdManager SDK directly or through some third-party components, it will be interacting with the Freewheel Context object. This object is responsible for creating ad requests, parsing the ad request responses, and managing the presentation of the resulted ads. Besides, the Freewheel Context object also provides events and metadata regarding the resulted ads and the presentation status.

Therefore, for a Datazoom collector to gather ad information in this scenario, the application should give access by attaching the Freewheel Context object to the collector context as soon as it becomes available. The Datazoom collector context interface expose these methods for this purpose:

// share a Freewheel Context object with the collector context
context.attachFwContext(freewheel_context) {}

// unshare the Freewheel Context object as an optional cleanup step
context.detachFwContext() {}

For example, a video page using HTML5 <video> element and managing Freewheel MRM AdManager SDK directly can set everything up and attach the Freewheel Context object (to the collector context) as below:

// Create the video player and the collector context
var media_element = document.getElementById("video");
var datazoom_context = datazoom.createContext(media_element);

// Create the Freewheel AdManager
var fw_admanager = new tv.freewheel.SDK.AdManager();
fw_admanager.setNetwork(1234);
fw_admanager.setServer("ad_server_url");

// Create the Freewheel Context object
var fw_context = fw_admanager.newContext();
fw_context.setProfile("some_profile");
/* other Freewheel Context configurations
 fw_context.setVideoAsset(...);
 fw_context.setSiteSection(...);
 fw_context.addTemporalSlot(...);
 ...
 */

// Share the Freewheel Context object with the collector context
datazoom_context.attachFwContext(fw_context);

// Request ads
fw_context.submitRequest();

/* other code related to ad presentation and player coordination
 ...
 */

That’s it. The Datazoom collector is now provided with the required access to gather ad related information.

If some third-party component is used to add ad implementation, the best way to enable ad data collection is by querying the underlying Freewheel Context object and attaching it to the collector context in the same way as described above.

Google IMA

To enable a Datazoom collector to capture the ad related data points, the required steps for a web application differ depending on how the ad framework (e.g., IMA) is integrated with the video player. In general, there are two types of integration method between the video player and ad framework:

1. Leverage ad framework integration supported by the video player

Players such as Akamai AMP player, JW Player, Bitmovin Player, Shaka player, … etc., support IMA ad integration as a part or an optional module of the player. Since the corresponding Datazoom collector for the player is prebuilt with knowledge of the player’s ad related features, for a web application who simply leverages the video player for ads, no additional code is required to enable ad data collection in this scenario.

A web application may choose to utilize the video player for the purpose of content presentation only, while building its own ad implementation by utilizing the ad framework directly. In these use cases, the video player has no awareness of the ad implementation and therefore it will fall under the second scenario described below.

2. Ad implementation external to the video player

Players that mainly focus on core playback/streaming functionalities, such as HLS.js player, Dash.js player, or the native HTML5 <video> element, often do not come with ad integration features. For a web application who likes to enable ads independent of the video player, it can choose to utilize the ad framework library (e.g., IMA) directly or bring in some third-party components. In either cases, since it is impossible for the corresponding Datazoom collector to gather ad information through the video player, some provisioning steps (see the section below: Attach IMA Objects) will be required to enable ad data collection.

Attach IMA Objects

For a web application who enables ads by utilizing IMA directly or through some third-party components, it will be interacting with two primary IMA objects mostly:

  • adsLoader: Usually a singleton object, which handles ad-request (e.g., VAST) transactions based on ad tags given as inputs. Upon each successful completion of an ad-request, one adsManager object is created to oversee the presentation of the resulted ads.

  • adsManager: An object instance is created upon each successful completion of an ad-request. It provides events and metadata regarding the resulted ads and the presentation status.

Therefore, for a Datazoom collector to gather ad information in this scenario, the application should give access by attaching these IMA objects to the collector context as soon as they become available. The Datazoom collector context interface expose these methods for this purpose:

// share the adsLoader object with the collector context, usually once per context
context.attachImaAdsLoader(adsLoader) {}

// share a adsManager object with the collector context, once per ad-request
context.attachImaAdsManager(adsManager) {}

// unshare adsLoader as an optional cleanup step
context.detachImaAdsLoader() {}

// unshare adsManager as an optional cleanup step
context.detachImaAdsManager() {}

For example, a video page using HTML5 <video> element and managing IMA directly can set everything up and attach the adsLoader (to the collector context) as below:

// Create the video player and the collector context
var media_element = document.getElementById("video");
var datazoom_context = datazoom.createContext(media_element);

// Create the IMA adsLoader
var adContainer = document.getElementById("ad-container");
var adDisplayContainer = new google.ima.AdDisplayContainer(adContainer, media_element);
var adsLoader = new google.ima.AdsLoader(adDisplayContainer);

// Share the adsLoader object with the collector context
datazoom_context.attachImaAdsLoader(adsLoader);

Then, whenever an ad-request is successfully completed, an adsManager object is created and attached to the collector context as below:

adsLoader.addEventListener(google.ima.AdsManagerLoadedEvent.Type.ADS_MANAGER_LOADED,
    function(event) {
        // Create an IMA adsManager
        var adsManager = event.getAdsManager(media_element);
        // Share the adsManager object with the collector context
        datazoom_context.attachImaAdsManager(adsManager);
    }
);

That’s it. The Datazoom collector is now provided with the required access to gather ad related information.

If some third-party component is used to add ad implementation, the best way to enable ad data collection is by querying the underlying IMA adsLoader/adsManager objects and attaching them to the collector context in the same way as described above.

Related articles

Comments

0 comments

Article is closed for comments.