DCR Static Google Tag Manager

From Engineering Client Portal

Engineering Portal breadcrumbArrow.png Digital breadcrumbArrow.png DCR & DTVR breadcrumbArrow.png DCR Static Google Tag Manager


Google Tag Manager provides easy-to-use tag templates for many Google and non-Google tools.

  • The Google Tag Manager framework is place on a publisher’s web page making it easy to add and maintain tags across sites without additional code.
  • All tag modification/additions, are performed via a point and click User Interface.

Quick Start - Adding DCR Static Measurement

Login to your Google Tag Manager Account

Create the Container Script

  • Container script setup instructions are located here.
  • Once created, the snippet needs to be embedded within each webpage on your site.
<!-- Google Tag Manager -->
<noscript><iframe src="//www.googletagmanager.com/ns.html?id=GTM-5XXXXX"
height="0" width="0" style="display:none;visibility:hidden"></iframe></noscript>
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
<!-- End Google Tag Manager -->

Add the DCR Tag

  • In Google Tag Manager, select an account and default workspace.
  • To add a tag: Click NEW. Select the tag type (DCR Static Lite) and specify the trigger to be on Page View.
  • Populate DCR Static template with Nielsen variables.

Tag Parameters

Detailed information on the parameters for the script tag can be found on Digital Measurement Metadata. These parameters will automatically sent to Nielsen once the page is loaded completely. Please contact your Technical Account Manager for more details.

GTM params.png

You should now be presented with a screen such as the one below:

Once these fields have been populated, you can Preview, and finally Publish. You have now fully implemented DCR Static Page Measurement to your site.

Dynamic Parameters

Dynamic Variables

There may be times when you will want to dynamically pass values to the DCR Static Lite tag, and this can be accomplished for the following fields: Assetname, Segment A, Segment B and Segment C.

Dynamic Example

Immediately before the Google Tag Manager Container code, you can declare some variables and pass dynamic values. GTM currently supports the four following dynamic parameters. If no value is sent for the below variables, the values provided during the tag setup in GTM will take priority.

Parameter Name Description Example
nol_assetname Unique Value assigned to page/site section entertainment
nol_segA First Breakout news
nol_segB Second Breakout celebrities
nol_segC Third Breakout slideshow

For example:

  // param override
  window.NOLLite = {
  debug: true,
 	"nol_assetname" : "entertainment-video",
 	"nol_segA": "SegA_value_here",
 	"nol_segB": "SegB_value_here",
 	"nol_segC": "SegC_value_here"	 
Note: If you do not select to pass any values dynamically, the values you placed in the Google Tag Manager Template will be used instead.

Reporting Structure

The figures below show the reporting structures for Static content:

static reporting.jpg


Monitoring Tools Testing the Browser Implementation

The steps to test the implementation are given below.

Step 1

Filter HTTP traffic with the string "imr" to capture traffic from the SDK. This will capture traffic going to Nielsen servers.

Step 2

Verify that the Nielsen SDK is being downloaded correctly and is the correct version.


Step 3

When the page is loaded for the first time, the Browser SDK fires a View ping as soon as content is loaded. Utilizing your HTTP traffic filter tool, you can now validate the metadata that is being sent to the Nielsen collection servers.

Example View Ping Below:


Step 4

The first duration ping is fired after 5 minutes of content is viewed and is indicated by the cr value containing a D. This should fire every 5 minutes but only when the page is in focus.


Step 5

Test the Opt-Out implementation