Nielsen SDK Documentation

Digital Audio Implementation Guide – Android

Digital Audio Implementation Guide

API Version 5.1.1


To start using App SDK, the following details are required.

  • App ID (appid): Unique ID assigned to the player/site and configured by product.
  • Nielsen SDK and Sample Player: A part of the downloaded package.

If you do not have any of these pre-requisites or if you have any questions, please contact our SDK sales support team.

Step 1: Import Library

Refer to Setting up Development Environment for information on importing libraries.

  • The latest version of App SDK allows instantiating multiple instances of App SDK object and can be used simultaneously without any issues.

The latest version of App SDK contains only appsdk.jar file and does not feature any native shared libraries like

Step 2: Initialize SDK

Initialize App SDK as soon as the application is launched. Refer to Initialization for more details on initializing an AppSDK object and the parameters required.

Step 3: Configure and fire API Calls

Configure API calls – play

Use play() to pass the channel descriptor information through channelName parameter when the user taps the Play button on the player.

  • ChannelName is a 32-character field containing the name of the program or feed such as: “WENZ-FM”, “The Dove-Tampa”, “Hot 107.9”, or “Aerosmith Radio”.
  • channelName is an optional parameter for Digital Audio implementations.

Configure API calls – loadMetadata

Use loadMetadata() to pass ‘content’ metadata. The CMS data must be passed as a JSON object.

Refer to Metadata section for the parameters to be passed in the JSON object.

loadMetadata() after the first play() call must have type as radio (“type”: “radio”).

Configure API calls – setPlayheadPosition (Content)

Use setPlayheadPosition() to pass the position of the playhead while the content is being played.

# Key Description Values Required? (Y/N) Example


Live UTC of the live content. Client-defined Yes Seconds since 1970.

If playhead is not available from audio Measurement, allow the app to start a timer (1-5 seconds) and use the timer event to send playhead position to the SDK. Once the actual playhead is available, let the app send the proper playhead position. This allows the SDK to calculate and provide a closer value for duration.

Buffering state

  • Do not supply playhead position while the content is being buffered.
  • If the content is in buffering state continuously for more than 30 seconds, call stop() API.

Sample Playhead

Configure API calls – stop

Call stop() only at the end of ad and when the stream playback is stopped by a user or an interruption from another event. Common events are; network loss, power / standby, incoming call, alarm, etc. Call stop() only when buffering continues for 30 seconds (not when it starts). Call play() when resuming a stream (previously stopped) or starting playback of a new stream.

API Call sequence

Call loadMetadata() with JSON metadata for ad as below.

Call setPlayheadPosition() every one second until a pause / stop. The sample API sequence can be used for reference when identifying the specific events that need to be called during content playback without ads.

Type Sample code Description
Start of stream;

// channelName contains JSON metadata of channel/video name being played
// contentMetadataObject contains the JSON metadata for the content being played
Content mAppSdk.setPlayheadPosition(playheadPosition); // playheadPosition is position of the playhead while the content is being played
End of Stream mAppSdk.stop(); // Content playback is completed

Step 4: Handling Foreground and Background states of App

There are two ways of handling the foreground and background states of the client application.

  • Let App SDK handle the app states information (foreground / background) and use it, as necessary. Click here for more information.
  • Capture app states through the application and trigger the corresponding API (appInForeground() or appInBackground()) upon every change of state. This allows Nielsen App SDK to know the app state. Click here for more information.

New devices (Android 4.0 and later versions)

Add application tag to Manifest XML file

When client’s app supports only new devices (Android 4.0 and above) and the client has not implemented a custom Application class for some other purpose,

  • Add the following entry (application tag) into the Manifest XML file to use SDK’s state detection feature.

This is the custom Application class where the whole background detection implementation is done.

No new permissions are required to change the properties in Manifest XML file.

Older devices (Android 4.0 or earlier version)

Identify the change of state through the application and call the respective API (appInForeground() or appInBackground()) upon every change of state (foreground / background). The SDK will use this information to pass the app launch times, etc. to Collection facility.

Step 5: Interruptions during playback

As part of integrating Nielsen App SDK with the player application, the Audio / Video app developer needs to handle the following possible interruption scenarios.

  • Pause / Play
  • Wi-Fi OFF / ON
  • Airplane Mode ON / OFF
  • Alarm Interrupt
  • Call Interrupt ( SIM or Third party Skype / Hangout call)
  • Alarm Interrupt
  • Content Buffering
    • Device Lock / Unlock (Video players only, not for Audio players)
    • App going Background / Foreground (Video players only, not for Audio players)

Click here for more details.

Nielsen Measurement Opt-Out Implementation

As a global information and measurement leader, we are committed to protecting the privacy and security of the data we collect, process and use. Our digital measurement products are not used to identify the consumer in any way, but they help us and our clients measure and analyze how consumers engage with media across online, mobile and emerging technologies, and offer insights into consumer behavior.
  • When the app user wants to opt in or opt out of Nielsen measurement, a new dynamic page (with content string obtained from userOptOutURLString()) should be displayed.
  • This Opt-out page should be displayed in a webview (within the app) and not in any external browser.
  • Capture the user’s selection in this page and pass it to the SDK through userOptOut() for Nielsen to save the user’s preference.
  • For more details, refer to Opt-Out Implementation and Nielsen Digital Privacy.

The SDK will continue measurement even after the user has opted out from Nielsen measurement.

Pre-Certification Checklists

After the application is ready to be sent for Nielsen Certification, please go through the Pre-Certification Checklist and ensure the app behaves as expected, before submitting to Nielsen.

Testing an Implementation – App

Click here for information on Testing the App Implementation.