View source for DAR Mobile Attributes Requirements

{{Breadcrumb|}} {{Breadcrumb|Digital}} {{Breadcrumb|Digital Ad Ratings}}  {{CurrentBreadcrumb}}
[[Category:Digital]]

== Introduction ==
Currently, Nielsen’s DAR tags are well supported online via '''browser'''-based viewing on PCs, MACs, and tablets/smartphones. However, when ads are served to tablets/smartphones via native '''app-store applications''', additional attributes are needed in order for Nielsen clients to employ Nielsen’s mobile DAR (mDAR) measurement product.

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 mobile attributes to mDAR measurement pings that are sent to Nielsen’s collection system. However, there is a significant portion of the mobile application universe where it is either not feasible, or desirable to integrate Nielsen’s native App SDK into 3rd party applications.

This document describes additional attributes that must be added to DAR pings to create mDAR-compliant tags by way of a server-side macro replacement. This method is often referred to as Nielsen’s “non-SDK” DAR solution. Nielsen envisions that these attributes be added by ad networks when they respond to ad requests from client mobile devices.

To support the insertion of the Advertising ID, it is assumed that you have published a specification that app publishers follow to pass the appropriate Advertising ID (for example, IDFA) in the Ad request URL. Typically, your Ad server will expand a macro that grabs that ID seen in the Ad request URL and pass it via the DAR pixel outlined below. See [[#Appendix A: Example Implementation]].

Finally, 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 platform vendor list.
{| class="wikitable"
|-
! Additional DAR Tag Parameters for Mobile !! Description !! Mandatory?
|-
| &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 ||
|}
<blockquote>'''Note''': Clients are encouragesd to make an effort to always fill-in optional parameters.

'''Note''': Do not URL encode the values.</blockquote>

== C7 - OS Grouping (Optional) ==
Valid device OS Grouping data values are the following literal values:
* osgrp,IOS
* osgrp,DROID
* osgrp,ANDROID
<blockquote>'''Note''': If one of the above values cannot be specific, then the parameter should not be included int he call.</blockquote>

== 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
<blockquote>'''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</blockquote>

== 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>
<blockquote>'''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.</blockquote>

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).

<blockquote>'' "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."</blockquote>

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
<blockquote>'''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.</blockquote>

== 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.
<blockquote>'''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.</blockquote>

== 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.
{| class="wikitable"
|-
! Opt-out !! Opt-in
|-
| uoo=true || uoo=false
|-
| uoo=1 || uoo=0
|-
| uoo=yes || uoo=no
|}
<blockquote>'''Note''':  if your Ad server is not capable os supporting the discrete &uoo parameter then you can set the c9 value to <code>devid,optout</code> (for example <code>…&c8=PHN&c9=devid,optout&c10=MBL…</code>)</blockquote>

== Examples of DAR and mDAR Tags ==
For each of the tag examples detailed below, we can support both unsecure (http) and secure (https) flavors.

'''Important note''': the values in the following tags are for illustrative purposes only. Please contact your Nielsen representative for specific parameter values for your use of DAR.

'''Test and Certification'''
* <code><nowiki>http://secure-cert.imrworldwide.com</nowiki>/cgi-bin/m?ci=nlsnci535<wbr />&am=3<wbr />&at=view<wbr />&rt=banner<wbr />&st=image<wbr />&ca=nlsn12452<wbr />&cr=crtve<wbr />&pc=%3cclientname%3e_plc0001<wbr />&ce=%3cclientname%3e<wbr />&c7=osgrp</code>

'''Production'''
* <code><nowiki>http://secure-gl.imrworldwide.com</nowiki>/cgibin/m?ci=nlsnci535<wbr />&am=3<wbr />&at=view<wbr />&rt=banner<wbr />&st=image<wbr />&ca=nlsn12452<wbr />&cr=crtve<wbr />&pc=<clientname>_plc0001<wbr />&ce=<clientname><wbr />&c7=osgrp,IOS<wbr />&c8=devgrp,TAB<wbr />&c9=devid,XXXX-XX-XXXXX-XXXX<wbr />&c10=plt,MBL <wbr />&c12=apv,AppVersion<wbr />&c13=asid,NIELSEN-PROVIDEDID<wbr />&c14=osver,7.0.4<wbr />&uoo=1<wbr />&r=[timestamp]</code>

'''Standard DAR tag (for information and completeness)'''
* <code><nowiki>http://secure-gl.imrworldwide.com</nowiki>/cgi-bin/m?ci=nlsnci535<wbr />&am=3<wbr />&at=view<wbr />&rt=banner<wbr />&st=image<wbr />&ca=nlsn12452<wbr />&cr=crtve<wbr />&pc=%3cclientname%3e_plc0001<wbr />&ce=%3cclientname%3e<wbr />&uoo=1<wbr />&r=%5btimestamp</code>

== 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'''

[[File:mDAR_Dataflow.png]]

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. 
<syntaxhighlight lang="url">'''&c7'''=osgrp,IOS'''&c8'''=devgrp,PHN'''&c9'''=devid,XXXX-XX-XXXXXXXXX'''&c10'''=plt,MBL'''&c12'''=apv,AppVersion'''&c13'''=asid,XXXX-XX-XXXX-XXXX</syntaxhighlight>


'''Figure 2 – Illustrative Ad Request / Ad Response'''

The below 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 below. Steps 3 and 4 in figure 1 is a summary of steps 3 through 9 in figure 2 below.

[[File:ad_response.png]]

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