Show Menu
ARGOMENTI×

Adobe Media Analytics (3.x SDK) for Audio and Video Extension

Use this documentation for information on installing, configuring, and implementing the Adobe Media Analytics (3.x SDK) for Audio and Video extension (Media Analytics extension). Included are the options available when using this extension to build a rule, along with examples and links to samples.
The Media Analytics (MA) extension adds the core JavaScript Media SDK (Media 3.x SDK). This extension provides the functionality for adding the Media tracker instance to a Launch site or project. The MA extension requires two additional extensions:
This extension deploys with Media 3.x SDK, which is not backward compatible with Media 2.x SDK. If your page already uses Media 2.x SDK, use Adobe Media Analytics for Audio and Video Extension instead of this extension.
After you have included all three of the extensions mentioned above in your Launch project, you can proceed in one of two ways:
  • Use Media APIs from your web app
  • Include, or build, a player-specific extension that maps specific media player events to the APIs on the Media tracker instance. This instance is exposed through the MA extension.

Install and configure the MA extension

  • Install: To install the MA extension, open your extension property, click Extensions > Catalog , hover over the Adobe Media Analytics (3.x SDK) for Audio and Video extension, and click Install .
  • Configure: To configure the MA extension, open the Extensions tab, hover over the extension, and then click Configure :

Configuration options:

Option
Description
Collection API Server
Defines the Media Collection API Server (Contact your Adobe representative to get this server)
Application Version
The version of the media player app/SDK
Player Name
Name of the media player in use (e.g., "AVPlayer", "HTML5 Player", "My Custom VideoPlayer")
Channel
Channel name property
Debug Logging
Enable or Disable logging
Enable SSL
Enable or Disable sending pings over HTTPS
Export APIs to Window Object
Enable or Disable exporting Media Analytics APIs to global scope
Variable Name
window
Reminder: The MA extension requires the Analytics and Experience Cloud ID extensions. You must also add these extensions to your extension property and configure them.

Using the MA extension

Using from a webpage/JS-app

The MA extension exports the Media APIs in the global window object by enabling the "Export APIs to Window Object" setting in the Configuration page. It exports the APIs under the configured variable name. For example, if the variable name is configured to be ADB , then Media APIs can be accessed by window.ADB.Media .
The MA extension exports the APIs only when window["CONFIGURED_VARIABLE_NAME"] is undefined and does not override existing variables.
  1. Media APIs:   window["CONFIGURED_VARIABLE_NAME"].Media
  2. Create Media Tracker Instance:   window["CONFIGURED_VARIABLE_NAME"].Media.getInstance
    Return Value: A Media tracker instance for tracking a media session.
    var Media = window["CONFIGURED_VARIABLE_NAME"].Media;
    
    var tracker = Media.getInstance();
    
    
  3. Using the Media tracker instance, follow the JS API documentation to implement media tracking.
You can obtain the sample player here: MA Sample Player . The sample player acts as a reference to showcase how to use the MA extension to support Media Analytics directly from a webapp.

Using from other extensions

The MA extension exposes media as shared module to other extensions. (For additional information on Shared Modules, see Shared Modules documentation .)
Shared Modules can only be accessed from other extensions. That is, a webpage/JavaScript app cannot access the shared modules, or use turbine (see code sample below) outside of an extension.
  1. Media APIs:   media Shared Module
  2. Create the Media tracker instance as follows:
    Return Value: A Media tracker instance for tracking a media session.
    var Media =
      turbine.getSharedModule('adobe-media-analytics', 'media');
    
    var tracker = Media.getInstance();
    
    
  3. Using the Media tracker instance, follow the JS API documentation to implement media tracking.
Testing: For this release, to test your extension you must upload it to Adobe Experience Platform Launch , where you have access to all dependent extensions.