Brightcove enables cloud-based publishing and distribution of digital media. You can use Arm Treasure Data with Brightcove to store digital media events and raw data about media access and usage.
Create a connector so that every time a video event occurs in browsers, Arm Treasure Data is notified. Treasure Data stores the data, and allows you to analyze the data via SQL.
In the Brightcove admin console, click the app menu and click the setting of “Players.” The Player is the object that feeds data to Treasure Data.
Then, click New Player or an existing player in the Players section.
In the Player Edit section, select "Plugins" tab. In plugins setting page, click Add a Plugin and then select "Custom Plugin".
Videojs plugin library
In the Options section, specify the following parameters:
See: Server Side Cookie
In addition to the plugin library, you must specify the Treasure Data SDK library in the "Scripts" tab.
Treasure Data SDK
Putting the Treasure Data SDK library in the "Scripts" tab.
Current version: v2.2.0
We also support the old version. You can use the version as well if you want.
Old version: v1.9.2
After saving the settings, publish your player.
After the player is configured and ready, you can get media code.
In the Brightcove admin console, click the app menu and click Media.
In the media page, select a video you are to use with the player and then click Publish > Web Player.
Select the player that is configured to work with the plugin.
Copy the code from the code area. You embed this code into your web page.
The Player now can track media events that occur on the web page and send that data to Treasure Data.
You can confirm for data import by embedding the code into your web page and then some interactions with the player (play, seek, etc.).
Confirm Import in Treasure Data
In Treasure Data, create a query to track the events coming in from the Brightcove player. It usually takes 3-5 minutes before events appear in the TD Console.
You can use the following parameters. The parameters are provided as part of the embed code.
- bc_video_id: Unique ID for a video content
- bc_video_name: the video content name
- bc_event: A value is set for each event type that has occurred
- Player Loaded
- Contents Loaded
- FullScreen Start: Start full-screen mode
- FullScreen Exit: Exit full-screen mode
- Volume Change: Change Volume
- Complete: Video is completed
- Percent of View: % of video completion
- Seek: Move seek
- bc_duration: length of a video content
- bc_session_id: unique id for session
- 0 is mute, 1 is maximum volume.
- percent of view completion
- bc_seek_start, bc_seek_end: If a user skips from 5 seconds point to 10 seconds point, bc_seek_start and bc_seek_end will be set 5 and 10.
Support for Gallery In Page Format
Note: When you use TD's SSC feature with Brightcove, you should use this 'Gallery' code, not the 'Media' code. Because the source domain of the TD tag fired by the Media code is the Brightcove domain, the expected SSC (cookie associated with the 1st party domain of the video playback site) cannot be obtained. However, since the TD tag fired by the Gallery code is linked to the domain of the video playback site, SSC can be obtained expectedly.
You can import event data from the Gallery in page format, which Brightcove provides as a multi-video experience within one creative.
The following Gallery formats are supported:
Create a gallery in page creative, after that, you can set the player for the creative.
Publish the change and you can get the code from "Embed code area". The experience is captured as an event that can be imported into Treasure Data.
As an example, when a viewer views a video and then selects the next video in the creative to watch, the data connector captures the change and starts to track events with the next video.