This guide will show you how to enable Digital Content Ratings (DCR) measurement on your Facebook Instant Articles.
DCR measurement can be added to your Instant Articles through the Analytics element:
<!-- Add Nielsen DCR Tracking Code here -->
For more information on the Analytics element, you can refer to the Analytics Services section of Facebook’s Instant Article Developer Documentation.
The Nielsen DCR Tracking code below will need to be added within the
<iframe> of the Analytics element on each article:
// load Nielsen JS Library
// create initialization object
var _nolggGlobalParams =
sfcode: 'XXX-cert', // location of collections environment. Value will be provided for testing
apid: 'PXXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX', // assigned App ID will be provided for testing
apn: 'PublisherName Instant Articles' // name to identify integration. Can be custom value
// create SDK instance
var gg1 = NOLCMB.getInstance(_nolggGlobalParams.apid);
// initialize SDK with initialization object
// create object with metadata for Instant Article
var staticmeta =
assetid: '', // *UPDATE*: unique ID for each article
section: '', // *UPDATE*: section or category for article
segA: '', // *UPDATE*: custom segment
segB: '', // *UPDATE*: custom segment
segC: 'Instant Articles'
// pass metadata for Instant Article when it is opened
Metadata can be passed through key-values using the Nielsen reserved keys. The tracking code includes the Nielsen reserved keys and placeholder values, <metadataPlaceholder>, for dynamic metadata. You will need to update these values.
The Nielsen reserved keys are:
|assetid||Unique ID for each article||dynamic||custom||✓|
|section||Section or category for article: Limit to 25 unique values||dynamic||custom||✓|
|segA||Custom segment: Limit to 24 unique values across custom segments A and B (segA + segB)||dynamic||custom|
|segB||Custom segment: Limit to 24 unique values across custom segments A and B (segA + segB)||dynamic||custom|
|segC||Reserved custom segment for Instant Articles||fixed||
The values passed through the Nielsen keys will determine the breakouts you will see in reporting. If you decide not to use custom segments A and B, then you do not need to pass a value in these keys.
You can reference the table to determine how the metadata you pass is used to define your reporting structure:
|Brand||apid||Brand is determined by assigned App ID passed during initialization|
|Sub-brand||apid||Sub-brand is determined by assigned App ID passed during initialization|
|Section||section||Section or category for Instant Article|
|Custom Segment A||segA||Available segment for custom reporting. Custom segments will roll into the sub-brand|
|Custom Segment B||segB||Available segment for custom reporting. Custom segments will roll into the sub-brand|
|Custom Segment C||segC||Custom segment C is reserved for reporting ‘Instant Articles’. The Instant Articles custom segment will be available under sub-brand and will include the total metrics for all your Instant Articles|
If you would like your Instant Articles to report into the same reporting structure as your website, we recommend passing the same dynamic metadata in Section, Custom Segment A, and Custom Segment B as you are on your website. This way your Instant Articles numbers contribute to those aggregations.
There are limits on the number of unique values that can be aggregated on in reporting. The specific limitations by key are:
|section||maximum of 25 unique values (section <= 25)|
|segA||total sum of segA and segB must be a maximum of 24 unique values (segA + segB <= 24)|
|segB||total sum of segA and segB must be a maximum of 24 unique values (segA + segB <= 24)|
We will confirm the production values to use after testing is completed.