Nielsen SDK Documentation

Contents

Nielsen SDK Onboarding Process

Steps to Release a Nielsen-enabled Application

The procedure to deploy a Nielsen-enabled player application into production comprises of five steps, as mentioned below.

Step 1: Client Onboarding

  • Client approaches Nielsen Client Team and discusses about the SDK Integration requirements.
  • Nielsen Client Team helps the client identify the most suitable product / implementation (DCR / DTVR / DAR etc. and App SDK (iOS or Android) / Browser SDK) based on the requirements.
  • Nielsen Client Team provides the pre-requisites for the integration and the list of downloads needed.

Step 2: Submit details and Download SDK

Following are the steps that the client should follow to download the required SDK package.

  • Visit the ‘Downloads‘ section of this site.
  • Click the Download SDK button.
  • Fill-in the basic user details and select the Nielsen Service that you subscribe to.
  • Submit the details to view the License Agreement for downloading the SDK.
    • The details are submitted to Nielsen Technical Account Manager (Nielsen TAM)
  • Read through the terms of agreement. Click I ACCEPT THE TERMS OF AGREEMENT button to accept the terms.
  • The subsequent page will provide the links to download the SDK and the time-stamped copy of the license agreement (in PDF).
  • Download the required SDK (iOS / Android / Browser) and Release Notes.
  • Based on the details received from the client, Nielsen TAM performs the following checks and assigns two appids (for Test & Production) and two sfcodes (for Test & Production) to the client.
    • Whether all third-party vendors (transcoding, encoding, etc.) listed are certified by Nielsen (if applicable)
    • Whether the CMS variable mapping for data is correct / valid

Step 3: Integration

  • Develop the player application and integrate the SDK. Set the appid, the application name (appname), and assign a software version (appversion) to the application.
    • Use the test appid during development, test, and certification.
    • Implementation Engineer (from Nielsen) will provide support for any queries, troubleshooting etc. related to SDK.
  • Once the player application is developed with the SDK integrated, complete the Pre-Certification Checklist provided by Nielsen TAM and submit along with the application for certification.

Step 4: Certification

The certification process takes up to three weeks to complete.

  • Implementation Engineer performs sanity testing before submitting the application to Nielsen QA team.
  • Nielsen QA team will perform the required testing.
  • Upon QA sign-off, the player application will be certified.

Step 5: Go Live

  • Upon certification, replace the test appid and sfcode used in the player application with the corresponding production appid and sfcode.
  • Submit the production-ready application to Nielsen TAM for data validation.
  • Upon successful data validation from Nielsen TAM, submit the production-ready application for distribution.

For more information, refer to the respective Developer Guide pages – iOS, Android or Browser.

Data Elements Checklist

Data Item Description
appid Nielsen Technical Account Manager provides two appids per application – Test appid (pre-certification use) and Production appid (post-certification use). Use Production appid only when the app has completed certification process with Nielsen and is ready to submit to App Store.
appname Name of your application.
sfcode sfcode will be provided by Nielsen and specifies which Nielsen collection facility the app should connect to. Connect to a development server during development and switch to production server once app has been certified by Nielsen.
dma If the app is supplying the Nielsen designated market area code (dma), consult Nielsen Technical Account Manager before doing the same.
ccode If the app is supplying the country code (ccode), consult Nielsen Technical Account Manager before doing the same.
CMS Metadata Discuss about the unique CMS metadata details with Nielsen Technical Account Manager prior to launch.