In this sample, you will learn how to send information to the Data Collector so that you can get analytics data for videos that are not viewed in a Brightcove web or SDK player. Note that this technique should not be used if you are using the Brightcove web or SDK players, as it will result in duplicated analytics data.
In this topic, you will learn to use Brightcove Player's catalog library of methods for making requests to the Video Cloud catalog. The catalog's library makes it easy to get information on Video Cloud media and load them into a player. The content in this document applies to Video Cloud only.
In this topic, you will first get a high level overview of using the REST APIs. Then later in the document a deeper dive will discuss example code. The first example uses the Analytics API to retrieve and display in the player's controlbar the number of views the video currently in the player has had. The second, and slightly more complex, example uses the Analytics API in conjunction with the Brightcove Player catalog to retrieve the most popular videos from an account and show them in a playlist. The code discussion in this document will center on retrieving the desired data from the correct REST API. For security reasons, the Brightcove REST APIs cannot be directly accessed from a web client, and a proxy is needed (as detailed in this document). If using server to server communication a proxy is not needed.
When you use the Dynamic Ingest API to add videos to your Video Cloud account, what you most want to know is when the video has been processed and whether or not renditions were successfully created. .
When you use the Dynamic Ingest API to add videos to your Video Cloud account, what you most want to know is when the video has been processed and whether or not renditions were successfully created. This document explains how you can do that using Dynamic Ingest API notifications . We also provide a sample dashboard app that automates the process.
In this topic, you will get an overview of the Analytics Data Collection API v2, which allows you to add events to your Video Cloud Analytics data in situations where Brightcove cannot track the events directly. This topic primarily addresses changes from the v1 to the v2 version of the API. Note: You should NOT use this API to track events for the Brightcove Player, or for the Android and iOS SDK players, because that already happens automatically, and you would be adding duplicate data.
Note: By default, updates are applied to all players automatically. To prevent auto-updating of a player you must set it to manual updating (also known as locking a player). You can do this in the Studio Players module or using the Player Management API . Opting out of auto-updates should be a temporary measure, applied while you resolve any issues that the update creates. If you do not update players to the current version, you are missing out on new features and bug-fixes, and older versions of the player will cease to be supported at some point