This version of the Conviva Analytics Integration works only with Player Version >= 8.2.x. The recommended and tested version of the Conviva SDK is 2.151.0.36981. See CHANGELOG for details.
Install the npm package:
npm i @bitmovin/player-integration-conviva --save-dev
Build the JS file by running npm run build
- Clone Git repository
- Install node.js
- Install required npm packages:
npm install
- Run tasks:
npm run lint
to lint TypeScript filesnpm run build
to build project intodist
directorynpm run start
to open test page in browser, build and reload changed files automatically
-
Include
conviva-core-sdk.min.js
as first of all scripts in your HTML document -
Create an instance of
ConvivaAnalytics
before callingplayer.load(...)
and pass in your ConvivaCUSTOMER_KEY
and optional configuration properties:-
Using NPM import:
-
Import ConvivaAnalytics:
import { ConvivaAnalytics } from '@bitmovin/player-integration-conviva';
-
Usage
const playerConfig = { key: 'YOUR-PLAYER-KEY', // ... }; const player = new Player(document.getElementById('player'), playerConfig); const conviva = new ConvivaAnalytics(player, 'CUSTOMER_KEY', { debugLoggingEnabled: true, // optional gatewayUrl: 'https://youraccount-test.testonly.conviva.com', // optional, TOUCHSTONE_SERVICE_URL for testing deviceCategory: Conviva.Client.DeviceCategory.WEB // optional, (default: WEB) }); var sourceConfig = { // ... }; player.load(sourceConfig).then(function() { console.log('player loaded'); }, function(reason) { console.error('player setup failed', reason); });
-
-
Using custom Build:
-
Include
bitmovinplayer-analytics-conviva.js
afterconviva-core-sdk.min.js
in your HTML document -
Usage
var playerConfig = { key: 'YOUR-PLAYER-KEY', // ... }; var container = document.getElementById('player'); var player = new bitmovin.player.Player(container, playerConfig); // A ConvivaAnalytics instance is always tied to one player instance var conviva = new bitmovin.player.analytics.ConvivaAnalytics(player, 'CUSTOMER_KEY', { debugLoggingEnabled: true, // optional gatewayUrl: 'https://youraccount-test.testonly.conviva.com', // optional, TOUCHSTONE_SERVICE_URL for testing deviceCategory: Conviva.Client.DeviceCategory.WEB // optional, (default: WEB) }); var sourceConfig = { // ... }; player.load(sourceConfig).then(function() { console.log('player loaded'); }, function(reason) { console.error('player setup failed', reason); });
-
-
-
Release the instance by calling
conviva.release()
before destroying the player by callingplayer.destroy()
If you would like to track custom VPF (Video Playback Failures) events when no actual player error happens (e.g.
the server closes the connection and return net::ERR_EMPTY_RESPONSE
or after a certain time of stalling)
you can use following API to track those deficiencies.
conviva.reportPlaybackDeficiency('Some Error Message', Conviva.Client.ErrorSeverity.FATAL);
See ConvivaAnalytics.ts for parameter details.
Conviva suggests an timeout of about ~10 seconds and before reporting an error to conviva and providing feedback the user.
If you want to override some content metadata attributes you can do so by adding the following:
let metadataOverrides = {
applicationName: 'App Name',
viewerId: 'uniqueViewerId',
custom: {
customTag: 'customValue',
},
encodedFrameRate: 24,
// …
};
// …
// Initialize ConvivaAnalytics
// …
conviva.updateContentMetadata(metadataOverrides);
Those values will be cleaned up after the session is closed.
See ConvivaAnalytics.ts for details about more attributes.
If you want to use the same player instance for multiple playback, just load a new source with player.load(…)
.
The integration will close the active session.
player.load({…});