DCR Static iOS SDK

Engineering Portal / Digital / DCR & DTVR / DCR Static iOS SDK

Prerequisites

To start using the App SDK, the following items are required:

	Item	Description	Source
☑	App ID (appid)	Unique ID assigned to the player/site and configured by product.	Contact Nielsen
☑	sfcode	Environment that the SDK must point to	Contact Nielsen
☑	Nielsen SDK	Includes SDK libraries and sample implementation; See iOS SDK Release Notes	Download

If you do not have any of these pre-requisites or if you have any questions, please contact our SDK sales support team. Refer to Digital Measurement Onboarding guide for more information on how to get a Nielsen App SDK and appid.

Import Library

Refer to Importing Frameworks for information on importing libraries.

• The latest version of App SDK allows instantiating multiple instances of App SDK object and can be used simultaneously without any issues.

Initialize SDK

Initialize App SDK as soon as the application is launched. Refer to Initalization for details on initializing an AppSDK object and the parameters required.

Configure API calls

play

For static <App Measurement> content, play API is not required.

loadMetadata

Use loadMetadata to pass ‘content’ and ‘ad’ Digital Measurement Metadata. The CMS data must be passed as a JSON object.

    loadMetadata(String jsonMetadata)

Refer to loadMetadata for the list of parameters to be passed in the JSON object.

Note: The loadMetadata call must have ("type": "static").

playheadPosition (Content)

For static <App Measurement> content, no playhead has to be supplied to the SDK.

stop

For static <App Measurement> content, stop API is not required.

API Call sequence

Call loadMetadata with JSON metadata as below.

Swift

 
let staticMetadata = [
        "type": "static",
        "assetid": "C77664",
        "section": "siteSection",
        "segA": "segmentA",
        "segB": "CustomSegmentValueB", //optional
        "segC": "CustomSegmentValueC", //optional
];

Objective C

 
NSDictionary * staticMetadata = @ {
    @ "type": @ "static",
        @ "assetid": @ "C77664",
        @ "section": @ "siteSection",
        @ "segA": @ "Segment A",
        @ "segB": @ "CustomSegmentValueB", //optional
        @ "segC": @ "CustomSegmentValueC", //optional
}

Configure Metadata

Map the Nielsen keys to variables so that the content metadata is dynamically updated.

The Nielsen reserved keys are:

Key	Description	Data Type	Value	Required?
type	asset type	fixed	'static'	Yes
assetid	Unique ID for each article	dynamic	custom (no Special Characters)	No
section	section of each site (e.g. section value should be first level in page URL: website.com/section). Limit to 25 unique values	dynamic	custom	Yes
segA	custom segment for reporting: Limit to 25 unique values across custom segments (segA + segB + segC)	dynamic	custom	No
segB	custom segment for reporting: Limit to 25 unique values across custom segments (segA + segB + segC)	dynamic	custom	No
segC	custom segment for reporting: Limit to 25 unique values across custom segments (segA + segB + segC)	dynamic	custom	No

The values passed through the Nielsen keys will determine the breakouts that are seen in reporting. The custom segments (A, B & C) will roll into the sub-brand. To not use custom segments A, B and C, do not pass any value in these keys.

Aggregation Limits There are limits on the number of unique values that can be aggregated on in reporting. The specific limitations by key are:

Key	Aggregation Limit
section	maximum of 25 unique values (section <= 25)
segA	Maximum number of unique values allowed across segA, segB, and segC is 25 (segA + segB + segC<= 25)
segB	Maximum number of unique values allowed across segA, segB, and segC is 25 (segA + segB + segC<= 25)
segC	Maximum number of unique values allowed across segA, segB, and segC is 25 (segA + segB + segC<= 25)

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 are not used to identify the consumer in any way, but they 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 app user wants to opt in or opt out of Nielsen measurement, a new dynamic page (with content string obtained from optOutURL) should be displayed.
• Use optOutStatus to retrieve the device’s Opt-Out status.
• This Opt-out page should be displayed in a webview (within the app) and not in any external browser.
• Capture the user’s selection in this page and pass it to the SDK through userOptOut for Nielsen to save the user’s preference.
• For more details, refer to iOS SDK API Reference - iOS 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 the app behaves as expected, before submitting to Nielsen.

Testing an Implementation - App

See Digital Measurement Testing.