Using Ooyala IQ with Third-Party Players

You now have the ability to integrate Ooyala analytics (Ooyala IQ) with any third-party system (non-Ooyala video players).

Ooyala IQ can provide metrics for:
  • An Ooyala player playing Ooyala assets (hosted in Backlot).
  • (NEW) A third-party player playing Ooyala assets (hosted in Backlot).
  • A third-party player playing third-party assets (hosted in a third-party CMS).
For this release you can integrate Ooyala IQ with third-party players for:

With this release, you can integrate Ooyala IQ with any player or device with one of our out-of-the-box SDKs or adapters or by integrating directly with the Ooyala IQ JSON API or JS SDK. We recommend that you use the JavaScript SDK for all platforms that support JavaScript and use the JSON API if your platform does not support JavaScript or if you are using Roku.

The following diagram shows how the integrations mentioned above integrate with Ooyala IQ. Items in light blue are managed by you, and items in dark blue are managed by Ooyala.

Data Flow

The following image shows the data flow from a third-party video platform to Ooyala.

What's New

You can view metrics for Ooyala and non-Ooyala video assets in third-party (non-Ooyala) players.

The Ooyala IQ UI has been adjusted to accommodate third-party player analytics. The adjustments include the following:
  • The Player panel shows the third-party player name when events come from a third-party player. For example, if you analyze events coming from JW player, you will see "JW Player" in the Player panel.
  • If content metadata is not ingested into Backlot, Ooyala IQ provides graceful UI degradation. This means that Ooyala IQ can provide analytics for third-party player events without requiring metadata ingestion from a third-party CMS system. For example, if Ooyala IQ doesn't get a video asset's title metadata, it will use the video asset's external ID in place of the title (see image below for an example).
  • If you are using Ooyala players and third-party players to play Ooyala video assets (hosted in Backlot), you can now use one Backlot account to stream video to an Ooyala player and a third-party player. You can view consolidated IQ analytics metrics in one dashboard (through one user account) for both types of players.You can see the different metrics for your Ooyala players and third-party players by looking at the Player and Device panels. Please note that for third-party assets (hosted in a third-party CMS), you will still need to set up a separate Backlot provider account to ingest asset metadata.

Getting Started with a Third-Party Player and Ooyala Assets

If you are using a third-party player to play Ooyala assets (hosted by Ooyala), follow the steps below to integrate the third-party player events with Ooyala IQ.

  1. Enable your third-party player to communicate player events to Ooyala IQ by integrating the Ooyala IQ JavaScript SDK or JSON API with your non-Ooyala video players by using one of the Ooyala out-of-the-box adapters or by building your own adapter. See Integrating Third-Party Players with IQ Using the JS SDK for details on the JavaScript SDK and Ooyala IQ JSON API for details on the JSON API.
  2. Make sure that your Ooyala assets are playable on third-party players.
    1. Check that your account processing profile is set up to create streams that the third-party player can play. Please check with the third-party player to see what stream types it supports. You can ask your Customer Success Manager for assistance checking your processing profile. The third-party player can then use the Ooyala playback authorization APIs to access the streams it can use (which will vary based on the third-party player).
      Note: We recommend that you test a variety of streams transcoded by Ooyala on the target device prior to ingesting your asset library to Backlot to make sure the streams playback properly.
    2. If you had to make changes to your processing profile to enable an encoding type, you will need to upload a new video file or re-encode the video file in order to get the newly generated file. Content replacement (replacing an asset) will not work for this step. You must upload a new file or open a support ticket with Ooyala Technical Support to reprocess the video without manually uploading it again to keep the same embed code.
    3. Use the Backlot API to query: /assets/<ASSET EMBED CODE>/streams and copy the URL for the desired encoding.
  3. Create your third-party player as you normally would, specifying the encoding URL gathered from step 2c as the file path to the video.
  4. Use the Ooyala Analytics Chrome Plugin to validate that your analytics pings are being properly sent to the Ooyala backend, or ask your Ooyala Customer Success Manager to validate your asset metadata in Backlot and event pings.

After enabling your third-party player to play Ooyala assets, your IQ account will automatically start showing metrics for the third-party player when analytics events occur for your Ooyala assets.

Getting Started with a Third-Party Player and Third-Party Assets

If you are using a third-party player to play third-party assets (not hosted by Ooyala), follow the steps below to integrate the third-party player events with Ooyala IQ.

  1. Create a trial Backlot account and ask your Customer Success Manager to enable the account for viewing your third-party assets and metadata in Backlot. You will view a simple version of Backlot that strips away irrelevant Backlot functionality.
  2. Access Ooyala IQ at http://analytics.ooyala.com or through the Backlot ANALYZE tab.
  3. (Optional) Sync your content metadata in your non-Ooyala CMS with the Ooyala Backlot CMS so that you can identify your videos in IQ Standalone. We strongly recommend that you do this, because without syncing your metadata, you will not be able to view your video titles in the IQ Standalone user interface. See Syncing Third-Party Metadata with Ooyala IQ for details on how to ingest your content metadata. Please talk to your Customer Success Manager if you want to work with Ooyala Professional Services for this step.
  4. Implement the relevant SDK with your non-Ooyala video players. Please talk to your Customer Success Manager if you want to work with Ooyala Professional Services for this step.
  5. Use the Ooyala Analytics Chrome Plugin to validate that your analytics pings are being properly sent to the Ooyala backend, or ask your Ooyala Customer Success Manager to validate your asset metadata in Backlot and event pings.

해당 내용이 도움 되었습니까?