Show Menu

Track core playback on Android

This documentation covers tracking in version 2.x of the SDK. If you are implementing a 1.x version of the SDK, you can download the 1.x Developers Guide for Android here: Download SDKs
  1. Initial tracking setup
    Identify when the user triggers the intention of playback (the user clicks play and/or autoplay is on) and create a MediaObject instance.
    Variable Name
    Media name
    Media unique identifier
    Media length
    Stream type (see StreamType constants below)
    Media type (see MediaType constants below)
    StreamType constants:
    Constant Name
    Stream type for Video on Demand.
    Stream type for Live content.
    Stream type for Linear content.
    Stream type for Audio On Demand
    Stream type for Audio Book
    Stream type for Podcast
    MediaType constants:
    Constant Name
    Media type for Audio streams.
    Media type for Video streams.
  2. Attach metadata
    Optionally attach standard and/or custom metadata objects to the tracking session through context data variables.
    • Standard metadata
      Attaching the standard metadata object to the media object is optional.
    • Custom metadata
      Create a dictionary for the custom variables and populate with the data for this media. For example:
      HashMap<String, String> mediaMetadata =  
        new HashMap<String, String>(); 
      mediaMetadata.put("isUserLoggedIn", "false"); 
      mediaMetadata.put("tvStation", "Sample TV Station"); 
      mediaMetadata.put("programmer", "Sample programmer");
  3. Track the intention to start playback
    To begin tracking a media session, call trackSessionStart on the Media Heartbeat instance. For example:
    public void onVideoLoad(Observable observable, Object data) {  
        _heartbeat.trackSessionStart(mediaInfo, mediaMetadata); 
    The second value is the custom media metadata object name that you created in step 2.
    trackSessionStart tracks the user intention of playback, not the beginning of the playback. This API is used to load the media data/metadata and to estimate the time-to-start QoS metric (the time duration between trackSessionStart and trackPlay ).
    If you are not using custom media metadata, simply send an empty object for the second argument in trackSessionStart .
  4. Track the actual start of playback
    Identify the event from the media player for the beginning of the media playback, where the first frame of the media is rendered on the screen, and call trackPlay :
    // Video is rendered on the screen) and call trackPlay.  
    public void onVideoPlay(Observable observable, Object data) { 
  5. Track the completion of playback
    Identify the event from the media player for the completion of the media playback, where the user has watched the content until the end, and call trackComplete :
    public void onVideoComplete(Observable observable, Object data) { 
  6. Track the end of the session
    Identify the event from the media player for the unloading/closing of the media playback, where the user closes the media and/or the media is completed and has been unloaded, and call trackSessionEnd :
    // Closes the media and/or the media completed and unloaded,  
    // and call trackSessionEnd().  
    public void onMainVideoUnload(Observable observable, Object data) {  
    trackSessionEnd marks the end of a media tracking session. If the session was successfully watched to completion, where the user watched the content until the end, ensure that trackComplete is called before trackSessionEnd . Any other track* API call is ignored after trackSessionEnd , except for trackSessionStart for a new media tracking session.
  7. Track all possible pause scenarios
    Identify the event from the media player for media pause and call trackPause :
    public void onVideoPause(Observable observable, Object data) {  
    Pause Scenarios
    Identify any scenario in which the Video Player will pause and make sure that trackPause is properly called. The following scenarios all require that your app call trackPause() :
    • The user explicitly hits pause in the app.
    • The player puts itself into the Pause state.
    • ( Mobile Apps ) - The user puts the application into the background, but you want the app to keep the session open.
    • ( Mobile Apps ) - Any type of system interrupt occurs that causes an application to be backgrounded. For example, the user receives a call, or a pop up from another application occurs, but you want the application to keep the session alive to give the user the opportunity to resume the media from the point of interruption.
  8. Identify the event from the player for media play and/or media resume from pause and call trackPlay .
    // trackPlay() 
    public void onVideoPlay(Observable observable, Object data) {  
    This may be the same event source that was used in Step 4. Ensure that each trackPause() API call is paired with a following trackPlay() API call when the media playback resumes.
See the following for additional information on tracking core playback: