ONE Display Marketplace and GDPR

Tags

ONE Display Marketplace tags follow the Ad Server tag guidelines. No changes are needed for Header Bidding for GDPR.

See the Verizon Media Ad Server Tag References Document for full details on how to define Standard Tags and Non-Standard Tags for ONE Display Marketplace tags.

Tag Parameters

GDPR requires each user to allow the use of personal data for targeting and other purposes. The user consent MUST be passed to the ad server for all standard and non-standard tag parameters.

• Standard tag parameters - include tag domain, request type, gdpr, and gdpr_consent. Get the full list here Standard Tag Parameters.
• Non-standard tag parameters - include the alias or cookie parameter. Find the full list here Non-Standard Tag Parameters.

 

Parameter	Description	Example
gdpr_consent	Parameter that passes a base64 websafe encoded IAB user consent string. The string represents user consent settings and contains the purpose and vendor bits. gdpr_consent must be sent along with the gdpr parameter. If gdpr=1, then Ad Server checks for consent in the gdpr_consent string. The consent is encoded when receiving. Ad Server decodes it and checks if the user allows "personalized advertising" (purpose) for Verizon Media (vendor). If gdpr=1, but the consent parameter value is not valid or no consent parameter is delivered with the ad request, Ad Server will opt out the user. In this case, personal user data cannot be logged or used for targeting.	Source: IAB Digital Advertising presentation
gdpr	Denotes whether or not this user must be comply with the regulation. If any of the below conditions is true, the request is subject to GDPR (gdpr=1) and Ad Server validates the consent string from the gdpr_consent parameter. The gdpr_consent parameter is present in the request. The page’s content targets EU users (needs to be defined by the Publisher for example with the help of a Consent Management Provider (CMP). The user is located in EU (Ad Server will perform a lookup of the users IP in case parameter is not defined). If the network owner (= Publisher) knows that his websites and users are always under GDPR compliance, a back end network setting can be set to “always gdpr=1”. In this case, the parameter is not needed and the Ad Serverwill always check for consent in in gdpr_consent. If the parameter gdpr is not present or the value is not valid, the Ad Server will still check and verify GDPR compliance. Ad Server looks up the user's IP address to verify if they are from EU or not.	Yes: gdpr=1 No: gdpr=0
gdpr_pd	Used for generic URL parameters and only in connection with Key Value and Keyword Targeting. If gdpr_pd=0, no personal data (from the perspective of the callee) is included. If gdpr_pd=1, the Publisher is using some type of personal data in values of these parameters. If no consent is present the Ad Server ignores data in the KV or keyword parameters for Targeting and deletes data from the ad request before saving. Note: "defined" URL parameters, must state whether or not they include personal data.	Default: gdpr_pd=1 Optional: gdpr_pd=0

 

Standard Tag Examples

Example JavaScript tag

 

Example IFRAME tag

 

Example Image tag

 

Non-Standard Tag Examples

Adxml Tag

 

Agency Tag

 

Beacon Tags

Transaction tracking beacon tag

User tracking beacon tag

 

Bind request

Note: A Bind Request is required to write cookies. To support GDPR the bind request must include the networkId and subNetworkId parameters. Without these parameters, Ad Server is unable to verify the network is trusted or enabled for consent override.

 

Friendly Iframe tag

 

JavaScript Tag (with GroupID Generator)

 

Mobile Tags

EU

US

 

MultiAd Tag

 

Newsletter Tag

 

Raw Data Tag

 

Reload Tag