Media

Collecting media data is critical for tracking user behavior when your customers consume video or audio content through Android and iOS mobile applications or on the web. mParticle provides a toolset for integrating media analytics into your customer experience.

The mParticle Media SDK provides a dedicated API for tracking common media events including session start/end, play, pause, and other milestones, as well as logging recurring advertising impressions and chapters for segmented content.

The mParticle Media SDK works hand in hand with the mParticle platform. Data logged from the Media SDK is forwarded to the Android SDK and then forwarded to any included integrations.

The mParticle Media SDK is compatible with Adobe Analytics for Media, supporting the full range of media-related events including heartbeat events. This simplifies an otherwise complicated and error-prone process of setting up media session event tracking and Adobe Heartbeat yourself.

Getting Started

Add the SDK

Before you can begin using the Media SDK, you need to have a working instance of the mParticle core SDK. Please see the core SDK getting started section for more details.

dependencies {
    implementation 'com.mparticle:android-media:1.0'
}

Creating an instance of a Media Session

The Android Media SDK provides a MediaSession object. Each MediaSession object represents a single end to end media experience and relates one-to-one to a piece of content. For example, if a customer is watching a video, pausing, seeking and scrubbing, that is considered a single session. If they stop the video, and play another piece of content, that is a new session.

var mediaSession = MediaSession.builder(MParticle.getInstance()) {
    title = "Media Title"
    duration = 1000
    mediaContentId = "123"
    streamType = StreamType.LIVE_STEAM
    contentType = ContentType.VIDEO
}
mediaSession.mediaSessionAttributes = mutableMapOf(
    "my_session_attribute" to "My Session Attribute"
)

You can access the source code and contribute to the mParticle Media SDK Github repo here.

Summary Events

Summary events are automated events that contain an accumulated record of what occured during a session, individual segments, and individual ads.

Session Summary Events

A Session Summary event tracks from when a MediaSession is initialized to when it’s de-initialized or when logMediaSessionEnd is called. The more accurate and detailed developers are with logPlay, logPause, logAdStart, and other media events, the more accurate the summary data will be.

The following table explains the different parts of the Session Summary event.

Segment Summary Events

A Segment Summary event tracks from when logSegmentStart is called to when either logSegmentSkip or logSegmentEnd is called. Segments could be the chapters of an audiobook or scenes in a movie.

The following table explains the different parts of the Segment Summary event.

Ad Summary Events

An Ad Summary event tracks from when logAdStart is called to when either logAdSkip or logAdEnd is called.

The following table explains the different parts of the Ad Summary event.

Logging media events

Once your session is instantiated, you will need to trigger a SessionStart. This should be done at the moment the user interacts with your content. For example, if the media is set to trigger on a user click, and your player fires a play event when the content starts, the session must begin before the play event.

1. Start a session

// set playhead
val currentPlayheadPosition = 300

// create any custom attributes
val customAttributes = mapOf(
    "<media attribute key>" to "<media attribute value>",
    "<custom attribute key>" to "<custom attribute value>"
)

// build Options object for logging Media Session Start
val options = Options(currentPlayheadPosition, customAttributes)

// call Media Session Start heartbeat event
mediaSession.logMediaSessionStart(options)

2. Log a play event

val options = Options(currentPlayheadPosition = 300)

mediaSession.logPlay(options)

3. (optional) Fire other events for user interaction, i.e. pause

val options = Options(currentPlayheadPosition = 300)

mediaSession.logPause(options)

4. End the Media Content once the content is complete

val options = Options(currentPlayheadPosition = 300)

mediaSession.logMediaContentEnd(options)

5. End the Media Session once the user interaction is over (such as after a post-roll or if the app is terminated)

val options = Options(currentPlayheadPosition = 300)

mediaSession.logMediaSessionEnd(options)

Logging Advertising

In most cases, advertising comes in as a series of Ad Breaks each containing numerous Ads. The Media SDK provides both sets of functionality so that you can track this behavior.

1. Fire an AdBreakStart event

mediaSession.logAdBreakStart {
        id = "123456"               // included as ad_break_id for Ad Break Start/End and Summary events
        title = "pre-roll"          // ad_break_title 
        duration = 6000             // ad_break_duration 
}

2. Trigger an AdStart event

mediaSession.logAdStart {
        id = "4423210"                                          // included as ad_content_id for Ad Start/End and Summary events
        advertiser= "Moms Friendly Robot Company"               // ad_content_advertiser
        title= "What?! Nobody rips off my kids but me!"         // ad_content_title
        campaign= "MomCorp Galactic Domination Plot 3201"       // ad_content_campaign
        this.duration = 60000                                   // ad_content_duration
        creative= "A Fishful of Dollars"                        // ad_content_creative
        siteId= "moms"                                          // ad_content_site_id
        placement= "first"                                      // ad_content_placement
        position= 0                                             // ad_content_position
}

3. Fire AdEnd or AdSkip when appropriate

mediaSession.logAdEnd()

4. Trigger an AdBreakEnd event when all ads have completed

mediaSession.logAdBreakEnd()

Custom media session attributes

You can create custom media session attributes when initializing a new media session directly in MediaSession.builder(). These custom session attributes are helpful when you need to track data like the specific page a piece of content was viewed on.

Custom media session attributes are automatically propagated to all subsequent media events logged during the session in addition to the media session summary event. Since custom session attributes are propagated to any event (a media event, advertising event, or a custom events) that is logged during the session, you don’t need to set these attributes again when you trigger the start of a media session.

How are these unique from custom event attributes?

There are several differences between event-level custom attributes and custom media session attributes:

• Custom media session attributes are propagated to all media events, ad events, or other custom events that are logged during the current media session.
• Custom session attributes are also propagated to segment summary events and ad summary events, while custom event-level attributes are not.
• Custom event attributes in the Media SDK are not included in the media session summary event.

Custom media session attribute limitations

• 100 key/value pairs per media session
• Keys must be strings and cannot exceed 255 characters
• Values may be strings, numbers, booleans, or dates, and cannot exceed 4096 characters

var mediaSession = MediaSession.builder(MParticle.getInstance()) {
    title = "Media Title"
    duration = 1000
    mediaContentId = "123"
    streamType = StreamType.LIVE_STEAM
    contentType = ContentType.VIDEO
}
mediaSession.mediaSessionAttributes = mutableMapOf(
    "my_session_attribute" to "My Session Attribute"
)

Generating Custom Events

The Media SDK will generate a MediaEvent for client-side kits such as Adobe Media Analytics, however the event can be converted to look just like a typical mParticle custom event that may be used to create audiences, used in calculated attributes, and sent to most mParticle integrations for analysis and activation.

To enable Custom event generation, pass a boolean to the initialization of your MediaSession to enable the Log Custom Event feature:

val mediaSession = MediaSession.builder {
    title = "Media Title"
    mediaContentId = "123"
    duration = 1000
    streamType = StreamType.LIVE_STEAM
    contentType = ContentType.VIDEO

    logMPEvents = true
}

To log a custom event that does not correspond with the supported Media Session events, you can generate a completely custom event:

val mpEvent = mediaSession.buildMPEvent("Milestone", mapOf(
    "type" to "95%"
  ))
MParticle.getInstance()?.logEvent(mpEvent)

Custom Event Schema

The Media SDK will generate Custom events per the specification below.

Event Names

The Media SDK exposes methods that will trigger Media Events based on the most common player functions. The Media SDK maps every MediaSession API to a predefined Custom event name. The table below details all of the predefineed Media Events:

Event Attributes

The media attributes below are a list of all available for capturing valuable information with every media event listed above. The customer will choose which attributes will be logged for each event to best describe the session characteristics for that event at that time. Should you require attributes not listed below, you may add your own media attributes.

Note: Depending on your player, you will need to either enable the callback method to receive updates for playhead position and quality of service (QoS) or set up a job to frequently poll for the current values.

Example Event

{
    "event_type": "custom_event",
    "data": {
        "custom_event_type": "media",
        "event_name": "Play",
        "custom_flags": {},
        "timestamp_unixtime_ms": "1573828863888",
        "event_id": "-109840007014118971",
        "source_message_id": null,
        "session_id": "-8572887793551346848",
        "session_uuid": "29959B6B-9C3B-486F-9807-B5534EA1B16A",
        "session_start_unixtime_ms": "1573828757702",
        "event_start_unixtime_ms": "1573828863888",
        "custom_attributes": {
            "content_title": "My sweet sweet media",
            "content_duration": "120000",
            "content_id": "1234567",
            "content_type": "Video",
            "stream_type": "OnDemand",
            "media_session_id": "96a023b8-b0c7-47b7-b687-09f73b9dfac3",
            "playhead_position": "110123"
        }
    }
}

Using the Event Listener

In cases where you may need to handle some custom functionality when a media event occurs, the Media SDK provides a mediaEventListener which will provide a callback.

For example, if you need to trigger a custom function when Play or Pause occurs:

mediaSession.mediaEventListener = { mediaEvent ->
        // Some custom callback method defined by user
        // Should only trigger when play or pause is fired
        when (mediaEvent.eventName) {
            MediaEventName.PLAY, MediaEventName.PAUSE -> {
                val mpEvent = mediaEvent.toMPEvent()
                MParticle.getInstance()?.logEvent(mpEvent)
            }
        }
    }

API Reference

Visit the complete API Reference for a deep dive into the Media SDK