Nielsen SDK Documentation

DCR Implementation Guide – Browser SDK

API Version 5.1.0


DCR Static Lite <Page Measurement> allows clients to measure the time spent by users on static content (in focus). Unlike Video measurement, the Static Lite <Page Measurement> does not require a configuration file.

  • The cadence of the View and Duration pings for DCR Static Lite is same as Video content. (View ping when content is loaded completely and Duration ping every 5 minutes following that).
  • View ping gets triggered when content is loaded completely and Duration ping every 5 minutes following that irrespective of the page being in focus (duration is calculated by c27 param for the amount of time user is on the page)

DCR Static Lite <Page Measurement> is a compact version of DCR Static <Page Measurement> with the following primary differences.

Static <Page Measurement> Static Lite <Page Measurement>
Requires a configuration file. Does not require a configuration file.
Duration ping cadence is every 30 minutes. Duration ping cadence is every 5 minutes.


Before starting the integration with Browser SDK, secure the following details from your (point of contact) Nielsen TAM.

  • App ID (apid): Unique ID assigned to the player / site and configured by product.
  • sfcode: Location of collection environment. During testing, please use the sfcode as “dcr“.

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

Append the parameters as hashbang URL parameters, starting with a hash (#) in place of a query string (?).

  • The use of hashbang parameters provides the ability for the browser to cache DCR static script file as hashbang parameters are not sent to the server when requesting for the file.

Below is an example of a DCR static <script> tag.




Performance Tip

It is recommended to include the “async” attribute in the script tag to asynchronously load the script and allow the DOM to continue processing. This provides a non-blocking loading of DCR static, providing better page load performance and minimal affects to additional scripts or page processing.

Tag Parameters

The parameters for the script tag are defined below. These parameters will automatically be loaded into DCR Static Lite once the page is loaded completely. These are the only parameters supported by the tag.

Parameter Definition

Parameter Description Required? Specified by Example
nol_sfcode Location of collection environment. Yes Nielsen dcr
nol_ci Brand level aggregation Yes Nielsen My_ClientID
nol_apid UniqueID assigned to player/site. Yes Nielsen PXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX
nol_assetname Unique ID assigned to content Yes Client My_assetname
nol_apn User-defined string value for describing the player/site. Yes Client My_AppName
nol_vc Sub-brand level aggregation Yes Client vcID
nol_apv Version of the app build Yes Client 1.0
nol_segA Segment A. (defaults to NA) No Client NA
nol_segB Segment B. (defaults to NA) No Client NA
nol_segC Segment C. (defaults to NA) No Client NA
nol_cref1 Standard episode ID. This is a custom parameter No Client Reference11
nol_cref2 Content originator (required only for distributors). This is a custom parameter No Client Reference22
nol_ad Access method (defaults to 0) No Client 0 for browser, 1 for app
nol_devid Device id. Defaults to blank if not provided. No Client My deviceID

Advanced Tag Implementation

In case you want to set the parameters dynamically using JavaScript, refer to Advanced Dynamic Script Initialization.

This tagging is an alternative way of dynamically passing parameters to Static Lite in replacement of the standard <script> tag implementation.

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 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 user wants to opt in or opt out of Nielsen measurement, a new dynamic page (with content similar to should be displayed.
  • For more details, refer to Opt-Out Implementation and Nielsen Digital Privacy.

Pre-Certification Checklists

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

Testing an Implementation – Browser

Click here for information on Testing the Browser Implementation.