This topic describes how Ooyala web and SDK players will continue to work after your videos are migrated to Video Cloud, keeping your online videos working while you complete the migration to the Brightcove players.
Introduction
Brightcove offers a highly customizable web player, and also native players for Android, iOS, and tvOS.
However, we know that replacing player embed codes and rebuilding device apps will take time, so Brightcove has built an adaptor that will allow your existing Ooyala players to continue working by retrieving the video data from Video Cloud instead of Backlot:
How it works
All the Brightcove players retrieve video and playlist data via the Playback API. You don't have to set up the API requests, manually, though. The web player has a Catalog library that handles the requests, and the device SDKs have built-in methods for that.
To keep your Ooyala players functioning, Brightcove has built an adapter that points player requests for video and playlist data to the Player API and the same videos in Video Cloud.
Analytics
Going forward, you will be using Video Cloud Analytics. The fixes to allow your existing Ooyala players with your Video Cloud videos includes sending analytics data to the Video Cloud analytics system. There is no modification you need to make to your pages or players.
You can access Video Cloud analytics data either using the standard and custom reports in the Analytics module or the Analytics API. See Migrating from the Analytics REST API to Brightcove Analytics API if you will getting analytics data via the API.
Mapping of Analytics Data
The table below shows how Ooyala analytics data fields are mapped to Video Cloud analytics data.
Ooyala Analytics | Video Cloud Analytics |
---|---|
Batch - Metric - Displays | video_impression (Video Impression) |
Batch - Metric - VideoStarts | vide0_view (Video View) |
Batch - Metric - playRequested/play | play_request (Play Request) |
Batch - Metric - TimeWatched | video_seconds_viewed (Video Seconds Viewed) |
Batch - Metric - PlayThrough25 | video_engagement_25 (Video Engagement 25) |
Batch - Metric - PlayThrough50 | video_engagement_50 (Video Engagement 50) |
Batch - Metric - PlayThrough75 | video_engagement_75 (Video Engagement 75) |
Batch - Metric - PlayThrough100 | video_engagement_100 (Video Engagement 100) |
Batch - Metric - PercentageWatched | video_percent_viewed (Video Percent Viewed) |
Batch - Metric - PlayerLoads | player_load (Player Load) |
Batch - Metric - UniquePlays | daily_unique_viewers (Unique Users/Unique Viewers) |
Batch - Dimension - Pcode | account (Account) |
Batch - Dimension - Asset | video (Video) |
Batch - Dimension - CountryCode | country (Country) |
Batch - Dimension - Region | region (Region) |
Batch - Dimension - City | city (City) |
Batch - Dimension - DeviceType | device_type (Device Type) |
Batch - Dimension - os | device_os (Device OS) |
Batch - Dimension - Browser | browser_type (Browser Type) |
Batch - Dimension - PlayerId | player (Player) |
Batch - Dimension - Domain | destination_domain (Destination Domain) |
Batch - Dimension - URL | destination_path (Destination Path) |
Real time Concurrent Users - Live | ccu (Concurrent Users) |
Real time Top Assets - Live | (Top asset) |
What may not work
If you have add-ons integrated with the Ooyala player, they will continue to be functional. However, if these add-ons depend on video data that is not available, they will not function properly. See the mapping of Ooyala video and playlist fields to Video Cloud fields for more information.
In addition, if you have add-on that make requests to Ooyala APIs, these will not work in many cases, though some Backlot API endpoints will still be operational. The Discovery API will not be operational.
Analytics data will be collected and sent to the Brightcove Analytics system.
Next steps
While Brightcove is committed to keeping the videos and playlists in your Ooyala players working as you transition to Video Cloud, you should be working on a plan to move to the Brightcove players in order to take full advantage of their features and customizability.