Integration with Nielsen Analytics

You can easily integrate with Nielsen analytics in your Ooyala mobile applications.

Nielsen N.V. ( provides measurements and analytics about what consumers watch and buy across devices where video, audio, and text content is distributed. Nielsen combines measurements across linear (TV-based) and dynamic (Internet-based) delivery methods and ad models to provide unified audience data for a piece of content across any device. Nielsen data is used for making decisions on ad models, content airtime, content cancellations or renewals, and content syndication logistics.

Ooyala's Nielsen plug-ins for the iOS and Android SDKs allow developers to integrate Nielsen functionality into Ooyala mobile applications. A Nielsen-enhanced app contributes consumer viewing and engagement data to Nielsen for digital content played on iOS and Android devices. This data includes event information and metadata tags that allow for identification and filtering.

Features and Highlights

  • Support for Nielsen's audio watermark technologies used for TV audience measurement
  • Support for Nielsen's custom metadata and custom configurations
  • Support for CMS tags and the industry-supported ID3 metadata tags
  • Easy integration with Nielsen's App SDK
  • Support for Nielsen privacy policies that allow consumers to opt out of Nielsen features

Scope of Integration

Ooyala supports mobile app integration with the following Nielsen products:

Content Delivery Nielsen Product Description
VOD mDPR (mobile Digital Program Ratings) Used for digital-only or linear TV content with a dynamic ad model. The mobile app contributes audience data for on demand TV viewing, such as unique audience metrics, stream counts, and reach by age and gender. See the mDPR documentation for details.
Live TV mTVR (mobile Television Ratings) Used for mobile audience measurement and television ratings. See the mTVR documentation for details.

Custom Metadata

Nielsen requires that you provide additional metadata that it uses to identify and classify the asset. To use Ooyala's Nielsen integration, you must add custom metadata in Backlot for each asset - whether VOD or live. See Adding Custom Metadata for instructions.

Two custom metadata are required for all assets (VOD and live): nielsen_channelName and nielsen_dataSrc. All others are required if nielsen_dataSrc is "cms".

Name Description
nielsen_channelName Name of the program or feed being sent. 32-character free-form text field. Required.
nielsen_dataSrc Source of the data. Required. One of the following values:
  • "ID3" if the stream contains ID3 metadata. Required for mTVR.
  • "cms" if the stream does not contain ID3 metadata.
nielsen_assetid Unique ID of the content. Do not use spaces.
nielsen_category Program name.
nielsen_tv JSON Boolean. One of the following values:
  • "true" for TV-related content (broadcast on TV).
  • "false" for non-TV content (youtube videos, etc.) (default)
nielsen_title Episode title.

Any keys that begin with nielsen_ will be used to pass values over to Nielsen's collection facility. The leading nielsen_ string will be removed in the process. For example, a per-asset key in Backlot of nielsen_xyzpdq with a value of 123 is copied to Nielsen as the key xyzpdq and the value 123. Refer to the Nielsen App API Developer Guide for details.

If ID3 tags are included in the stream per Nielsen requirements (for example, containing, they will be passed over to Nielsen’s collection facility. To pass ID3 tags, the Ooyala mobile SDK must be configured to use the VisualOn stream player via OoyalaPlayer.enableCustomHLSPlayer = true. Refer to the Nielsen App API Developer Guide for details about the jsonMetadata parameter.