Obtain valid configuration parameters
These parameters can be obtained from an Adobe representative after you set up your analytics account.
Provide the following capabilities in your media player:
Add your downloaded library to your project. Create local references to the classes for convenience.
MediaSDK-js-v3*.zip file that you downloaded.
Verify that the
MediaSDK.js file exists in the
MediaSDK.js on all site pages.
<body> tag on each page. For example:
To quickly verify that the library was successfully imported, check
ADB.Media is exported on Window object.
MediaSDK.js can also be used with compatible module loaders.
Create an instance of
AppMeasurement and configure
The Media SDK configuration requires an instance of
var appMeasurement = new AppMeasurement(“<rsid>”); appMeasurement.visitor = visitor; appMeasurement.trackingServer = “<visitor_namespace>.sc.omtrdc.net”;
Configure Media SDK
Media SDK should be configured once per webpage and the configuration applies to all the tracker instances created.
Media SDK (3.x) uses Media Collection API for tracking media which is different from the HB endpoint used in 2.x SDKs. Contact your Adobe representative to get more information.
Here is a sample
// Create MediaConfig object (same as above) var mediaConfig = new ADB.MediaConfig(); mediaConfig.trackingServer = Configuration.MEDIA_COLLECTION_ENDPOINT; mediaConfig.playerName = Configuration.PLAYER_NAME; mediaConfig.channel = Configuration.CHANNEL; mediaConfig.appVersion = Configuration.APP_VERSION; mediaConfig.debugLogging = false; mediaConfig.ssl = true; ADB.Media.configure(mediaConfig, appMeasurement);
After configuring Media SDK, tracker instances for tracking media content can be created using
var tracker = ADB.Media.getInstance();
Make sure that your
tracker instance is accessible and does not get deallocated until the end of the media session. This instance will be used for tracking all the following events for that session.
For detailed information about migrating from 2.x to 3.x, see 2.x to 3.x Migration.