DCR Video & Static Data Collection: Difference between revisions

From Engineering Client Portal

No edit summary
 
Line 7: Line 7:
Depending on the consent signal passed (opt-in / opt-out) and local privacy regulations, data elements will be further processed for audience measurement purposes.
Depending on the consent signal passed (opt-in / opt-out) and local privacy regulations, data elements will be further processed for audience measurement purposes.


For specific technical guidance on SDK interoperability with OS specific consent features such as “Limit Ad Tracking/App Tracking” please see the “Privacy” section within the relevant Nielsen platform/OS implementation guides hosted here: https://engineeringportal.nielsen.com/docs/US_DCR_%26_DTVR
For specific technical guidance on SDK interoperability with OS specific consent features such as “Limit Ad Tracking/App Tracking” please see the “Privacy” section within the relevant Nielsen platform/OS implementation guides hosted here: [[US DCR & DTVR]]


== Data Points Collected ==
== Data Points Collected ==

Latest revision as of 20:44, 10 December 2021

This document details all the possible data elements that will be collected by the Nielsen Mobile App SDK or Browser SDK.

Details on consent transmission to Nielsen can be found here: https://www.nielsen.com/us/en/legal/privacy-statement/digital-measurement/#choices

Regardless of consent status (opt-out / opt-in), data elements will be collected for the minimum purpose of accurate volumetric aggregate denominator calculation in measurement metrics.

Depending on the consent signal passed (opt-in / opt-out) and local privacy regulations, data elements will be further processed for audience measurement purposes.

For specific technical guidance on SDK interoperability with OS specific consent features such as “Limit Ad Tracking/App Tracking” please see the “Privacy” section within the relevant Nielsen platform/OS implementation guides hosted here: US DCR & DTVR

Data Points Collected

Platform Data Element Description
Mobile App Device ID: Advertising ID Hashed IDFA/Google Ad ID for users who are not opted out
Mobile App Opt-out indicator uoo=true is derived as per device setting.
Mobile App & Browser Client identifier Nielsen generated, Client provided
Mobile App & Browser Operating System Collection Derived
Mobile App & Browser IP Address Collection Derived; Once collected, last two octets are obfuscated for any traffic originating from Europe
Mobile App & Browser User Agent (enables mapping on the Nielsen backend to validate platform) Passed by the device/browser headers to collection for resolving
Mobile App & Browser Device Group Collection Derived
Mobile App & Browser Ad creative type (display v. video, only if enabled by Client) Client provided
Mobile App & Browser Platform Type Collection Derived
Mobile App App Version Client supplied
Mobile App App ID Generated by Nielsen, passed by clients in initialization
Mobile App OS version Passed in hello ping for App SDK.
Mobile App & Browser Asset Name Client supplied
Mobile App & Browser Publisher (Content) Client supplied
Mobile App & Browser Program (Content) Client supplied
Mobile App & Browser Episode Client supplied
Mobile App & Browser Genre Client supplied
Mobile App & Browser Vod/Live Stream Client supplied
Mobile App & Browser Content type (static/video) Client supplied
Mobile App & Browser AirDate - Linear content Client supplied
Mobile App & Browser Ad load type (if applicable) Client supplied
Mobile App & Browser Time Started Calculated by SDK
Mobile App & Browser Time Ended Calculated by SDK
Mobile App & Browser User Association ID (UAID) SDK generated
Mobile App & Browser Custom Segment Client supplied
Mobile App & Browser Custom Segment Client supplied
Browser Referrer Page URL HTTP Header