DAR Mobile Attributes Requirements

Engineering Portal / Digital / Digital Ad Ratings / DAR Mobile Attributes Requirements

Introduction

The standard Nielsen Digital Ad Rating (DAR) tag only supports cookie based web browser viewing on PCs, MACs, and tablets/smartphone (web-browser). However, when ads are served to tablets/smartphones via native app-store applications, the cookie based tag does not function correctly. Additional tag attributes are needed in order for audience reach measurement to function. Example tags are detailed later in this document.

One way Nielsen clients can accomplish this is by the use of Nielsen’s native iOS/Android App SDK. Nielsen’s App SDK automatically adds these additional tag attributes to the standard cookie based webbrowser tag before the tag is forwarded on to the Nielsen census collection system. However, there is a significant portion of the publisher mobile app universe where it is either not feasible, or desirable to integrate Nielsen’s native App SDK into 3rd party applications.

The purpose of this document is to detail the tag URL parameters required that are additional to the standard cookie based web-browser tag.

The most critical additional parameter required is the insertion of the Advertising ID (IFA / IDFA / AdID) from the users device that has been exposed to the Ad creative.

If you are reading this document as an Ad server representative then it is assumed that you have published a specification that mobile app publishers follow to pass the appropriate Advertising ID in the Ad request payload. Typically, your Ad server will then expand a macro or label with that value passed in the Ad request URL, insert into the DAR mobile app tag and redirect to Nielsen collections. See s. See #Appendix A: Example Implementation, figure 2 for an example tag workflow.

The standard way of triggering a Digital Ad Ratings (DAR) tag on Mobile-App is for the publisher app to trigger (either directly or via Ad server) the tag upon Ad exposure to the user. i.e. a client-side initiated tag. If you wish to implement server-side dispatch of mobile in-app DAR tags then see additional section in this document titled server-side tag dispatch. Please read the rest of this document before reading the section on server-server.

Once you have completed your integration, you will be required to submit to a short certification. See #Appendix B: Implementation, Testing & Certification. Certification also grants inclusion to the approved publisher and certified Ad server vendor list.

Important Note: for 2018, the MRC has mandated a series of changes to audience measurement that will require additional tag events to be communicated to Nielsen so that we may compute duration weighting etc. You are strongly urged to contact your Nielsen client service representative to seek a briefing from Nielsen on the best technical methods for tagging in order to be compliant with these changes.

Specification of Extension to DAR Tags for Mobile-App Audience Measurement

In this section, the additional URL parameters required beyond the standard cookie based web-browser tag are described in detail.

For each of the tag examples detailed below, we can support both non-secure (http) and secure (https) flavors. The standard cookie based web-browser tag is included below for reference purposes.

Important note: the values against each value-pair in the following tags are for illustrative purposes only. Values for CA, PC and CE will vary depending on the specific campaign being measured and capabilities of the Ad server for macro/value expansion. For more detail on the core DAR parameters, please see the Nielsen DAR Tag Implementation Guide.

Web Browser DAR tag (cookie based persons identification) http://secure-gl.imrworldwide.com/cgibin/m?ci=nlsnci535&am=3&at=view&rt=banner&st=image&ca=nlsn12452&cr=crtve&pc=<creativeid>_plc0001&ce=<siteid>&r=<timestamp>

Mobile-App DAR Tag Extension (IFA based persons identification) http://secure-gl.imrworldwide.com/cgibin/m?ci=nlsnci535&am=3&at=view&rt=banner&st=image&ca=nlsn12452&cr=crtve&pc=<creativeid>_plc0001&ce=<siteid>&c7=osgrp,IOS&c8=devgrp,TAB&c9=devid,XXXX-XX-XXXXX-XXXX &c10=plt,MBL&c12=apv,<appVersion>&c13=asid,NIELSEN-PROVIDEDID&c14=osver,7.0.4&uoo=1&r=<timestamp>

Additional DAR Tag Parameters for Mobile	Description	Mandatory parameter for mDAR?
&c7	OS Grouping
&c8	Device Grouping
&c9	Advertising ID	✔
&c10	Platform
&c12	App Version
&c13	AppID (Nielsen assigned App ID)	✔
&c14	OS Version
&uoo	Opt-out indicator	When applicable

Note: Clients are encouragesd to make an effort to always fill-in optional parameters. Note: Do not URL encode the values.

C7 - OS Grouping (Optional)

Valid device OS Grouping data values are the following literal values:

• osgrp,IOS
• osgrp,DROID
• osgrp,ANDROID

Note: If one of the above values cannot be specific, then the parameter should not be included int he call.

C8 - Device Grouping

Valid literal values for phone, tablet, portable media player (iPod) and unknown are as follows:

• devgrp,PHN
• devgrp,TAB
• devgrp,PMP
• devgrp,UNWN
• devgrp,DSK

Note: If one of the above values cannot be specific, then the parameter should not be included in the call or should be left empty

C9 - Advertising ID

This is the advertiser ID for the client’s mobile device. IDFA for iOS, Google Advertising ID for Android:

• devid,<IDFA>
• devid,<IFA>
• devid,<Google Advertising ID>

Note: For Android devices, the Google Advertiser ID should be used as the default and the Android ID as the second option.

Note: If C9 is <empty>, upon receiving the ping, the Nielsen collection server will attempt a 302 redirect to the data provider per the regular DAR pixel for browsers.

As of August 1, 2014, Google is enforcing use of the Advertising ID for advertising and user analytics (http://play.google.com/about/developer-content-policy.html).

"Beginning August 1st 2014, all updates and new apps uploaded to the Play Store must use the advertising ID (when available on a device) in lieu of any other device identifiers for any advertising purposes."

It is preferred that the IDFA or Google Advertising ID be sent as is from the mobile device (“cleartext”). However, if mandated, we will support SHA256 hashed values with no-salt. Passing a hashed value (and/or salting) using any other standard will result in a failed match by the data provider upon receiving the ping. In turn, this results in impressions surfacing in the DAR unmeasurable audience totals. Please contact Nielsen if you anticipate a large percentage of hashed values coming in from your publisher clients.

Privacy, Ad Tracking, and Ad Targeting

In newer iterations of the iOS and Android device operating systems, a facility exists allowing users to “opt-out” of “Ad Tracking”. It is Nielsen’s interpretation that this setting is primarily designed to allow users to specify opt-out of Ad Targeting rather than Ad Measurement. DAR does not provide Ad Targeting data.

However, it is also Nielsen’s position that the publisher or Ad network should provide a mechanism to also allow a user to opt-out of Ad Measurement. The Nielsen SDK will honor the Nielsen Ad Measurement opt-out settings configurable @ http://www.nielsen.com/us/en/campaigns/privacy-policy-opt-out.html.

However if the integration approach described in this document is being used instead of the Nielsen SDK then YOU as the publisher or Ad network must provide a capability to opt-out of Ad Measurement as the configuration on www.nielsen.com will not be detectable. You may elect to interpret the iOS / Android “Ad Tracking” setting for the purpose of limit Ad measurement or provide a separate discreet mechanism to allow a user to opt-out of Ad measurement.

Please see &uoo later in this document for implementation details of the optout indicator.

For additional clarification on privacy policy, please contact your Nielsen representative.

C10 - Platform

To determine this value, Nielsen suggests that the ad network leverage user agent information to determine if the client device is either a mobile or desktop device.

Valid literal values for mobile and desktop data values are as follows:

• plt,MBL
• plt,DSK

Note: If one of the above values cannot be specific, then the parameter should not be included in the call or should be left empty.

C12 - App Version (Optional)

This is the version of the ad network system software or SDK that is implemented in this extension. Although this field is not required, this feature can be useful for troubleshooting purposes following deployment.

• apv,<N.N>

C13 - AppID

This Nielsen provided ID is unique to the ad network and is required for certification.

• asid,<NNNNNNNNN-NNNN-NNNN-NNNN-NNNNNNNNNNNN>

An App ID will be provided for testing. A separate App ID will be provided for production use. Please request from your Nielsen representative.

Note: If you are a publisher leveraging the non-SDK solution, you will be provided with a unique App ID for each combination of app and device OS type.

C14 - OS Version (Optional)

Operating system version

• osver,<OS Version>

Example: for iOS -> 7.0.4

UOO - Opt Out (Optional)

Opt-out parameter

• <Boolean state>

<Boolean state> is a Boolean representation of whether the user is opting out or not.

The absence of uoo in the tag is interpreted as an implicit opt-in. i.e. not opting out.

The following pairings of opt-out are supported. Important: you must choose one set of paired values only and inform your Nielsen representative.

Opt-out	Opt-in
uoo=true	uoo=false
uoo=1	uoo=0
uoo=yes	uoo=no

Note: if your Ad server is not capable os supporting the discrete &uoo parameter then you can set the c9 value to devid,optout (for example …&c8=PHN&c9=devid,optout&c10=MBL…)

Server-Side Tag Dispatch

The standard way of triggering a Digital Ad Ratings (DAR) tag on Mobile-App is for the publisher app to trigger (either directly or via Ad server) the tag upon Ad exposure to the user. i.e. a client-side initiated tag.

It is important to note that MRC/IAB measurement standards stipulate that the Ad exposure event still be initiated and recorded from the client-side, even if the Ad measurement tag (in this case a DAR tag) is physically initiated from the server-side. Evidence may be required (publisher log file or similar) from the MRC/IAB that the user was exposed to the Ad creative on their device.

The following additional changes to the standard mobile-app DAR tag are required to support dispatch the DAR tag from a server-side publisher ad server:

1. X-Forwarded-For (XFF) IP: The original client IP address must be passed in the X-ForwardedFor (XFF) HTTP header field. When the impression is fired directly from the Ad Server, the XReal-IP will be the Ad Server IP.
2. Cachebuster: Already present in the DAR tag, this now becomes mandatory. A cachebuster or random number ensures a new call is made to the Ad Server. By including a cachebuster ('r' parameter), the tag will not be cached. The timestamp of when the Ad was served can be used.
3. User Agent (UA): The HTTP UA from the client device should be used to populate the HTTP UA in the server-server connection/ping.
4. TLS: the tag received by Nielsen must be TLS v1.2 compliant or greater.

Important note: the current iteration of server-server tag collection only supports mobile-app (IFA and AAID) and will NOT support cookie based audience measurement.

Appendix A: Example Implementation

In the below examples, you will see the overall DAR flow (Figure 1) and a detailed illustrative Ad Request / Response model (Figure 2).

Figure 1 – End to End Data Flow

Nielsen certified publishers and platforms will append the new parameters (below) with the appropriate URL safe values passed to Nielsen’s current DAR tag. The current DAR tag should be acquired using the existing processes for each campaign/placement.

&c7=osgrp,IOS&c8=devgrp,PHN&c9=devid,XXXX-XX-XXXXXXXXX&c10=plt,MBL&c12=apv,AppVersion&c13=asid,XXXX-XX-XXXX-XXXX

Figure 2 – Illustrative Ad Request / Ad Response

The above is an example of how an Ad server is supporting the build of mobile DAR tags for its publisher clients.

• Step 2 in Figure 1 is a summary of steps 1 and 2 in Figure 2 above.
• Steps 3 and 4 in Figure 1 is a summary of steps 3 through 9 in Figure 2 above.

Appendix B: Implementation, Testing & Certification

Once you have integrated the ping per the above specs, Nielsen requires you to pass through a one-time certification before traffic can be accepted into the production environment.

The overall process is:

1. Valid DAR contract or NDA is in place.
2. Kick-off meeting with Nielsen onboarding team.
3. Confirm meet minimums testing requriements:
   1. Host Ad/Tag for in-app delivery
   2. Can pass opt-out back to Nielsen
   3. Can pass Device ID in cleartext or SHA-256
4. Nielsen provides the mDAR testing form that includes the test App ID and the test tag
5. Implement the specification and provide Nielsen the completed testing form.
6. Identify the live campaigns for intial testing and run the test tag; suggest 5,000-10,000 impressions.
7. Nielsen validates the data received from the test and confirms the initial test successful and provides the production App ID.
   1. Goal is to test that all minimum requirements in step 3 are confirmed passed to Nielsen with no issues.
8. Ensure contracts are in place for external test campaign with Nielsen Client Service team.
9. Identify another live campaigns for production testing with production tag and app ID.
10. Nielsen validates the data received from the final test and confirms certification for any DAR countries tested.
    1. Goal to test in full DAR E2E environment, receive matches from data provider for demographics and correct identification of mobile impressions.