
Security News
vlt Launches "reproduce": A New Tool Challenging the Limits of Package Provenance
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
@bitmovin/player-integration-conviva
Advanced tools
Conviva analytics integration for the Bitmovin Player
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.
npm install
npm run lint
to lint TypeScript filesnpm run build
to build project into dist
directorynpm run start
to open test page in browser, build and reload changed files automaticallyBuild the script by running npm run build
Include bitmovinplayer-analytics-conviva.js
after conviva-core-sdk.min.js
in your HTML document
Create an instance of ConvivaAnalytics
before calling player.load(...)
and pass in your Conviva CUSTOMER_KEY
and optional configuration properties:
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
});
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 calling player.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({…});
[3.0.1] - 2019-05-16
FAQs
Conviva analytics integration for the Bitmovin Player
We found that @bitmovin/player-integration-conviva demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
vlt's new "reproduce" tool verifies npm packages against their source code, outperforming traditional provenance adoption in the JavaScript ecosystem.
Research
Security News
Socket researchers uncovered a malicious PyPI package exploiting Deezer’s API to enable coordinated music piracy through API abuse and C2 server control.
Research
The Socket Research Team discovered a malicious npm package, '@ton-wallet/create', stealing cryptocurrency wallet keys from developers and users in the TON ecosystem.