Regulation Macros

This page documents macros that you can utilise in order to pass do no track (DNT) and GDPR consent macros from the supply (player) to the demand (tags).

Please note that Vidazoo is not storing log data of passed macros since Vidazoo is not maintaining record of any associated data to specific user or session.

Do Not Track (DNT)

Browser DNT

Available from player version 1.0.181

Vidazoo player can detect the Browser DNT and you can use the ${browser.dnt} macro on the Tag parameters to pass it to your demand partners via VAST/VPAID tag macros.

Values

  • false - track allowed

  • true - do not track

Publisher DNT

You can pass the publisher_dnt custom macro on the player (reference) and to map this macro value to ${macros.publisher_dnt} on the demand tag -> url tab -> parameters section.

Values

  • 0 - track allowed

  • 1 - do not track

Personalised Ads Consent

Use below parameters macros to pass the consent based on IAB Consent Framework. Learn more about related params here

Parameter

Passing Parameter

Parameter Value

REGS GDPR

You can pass the userGdpr parameter on the player query object and to map this macro value to${user.gdpr}on the tag. Learn More

object will signal whether or not the request is subject to GDPR regulations. 0=No, 1=Yes

USER CONSENT STRING

You can pass the userConsentStr parameter on the player query object and to map this macro value to value to${user.consentStr}on the tag. Learn More

IAB definition - Consent - The binary encoding scheme that is passed in base64 url/web safe format known as (daisybit). The Buyer should use the consent array information to know if the user gave consent and for which vendors it gave consent and for which purposes.

IAB Europe Transparency and Consent Framework - The binary encoding scheme that is passed in base64 url/web safe format known as (daisybit).

You can pass the userConsent parameter on the player query object and to map this macro value to${user.consent}on the tag. Learn More​.

Values

  • 0 no consent

  • 1 true consent

  • 2 legitimate interest

For demand that is able to identify both USER CONSENT or USER CONSENT STRING you can map the macro value to ${user.consentStrOrNum}on the demand tag -> url tab -> parameters section.

COPPA Compliance

COPPA imposes certain requirements on operators of websites or online services directed to children under 13 years of age, and on operators of other websites or online services that have actual knowledge that they are collecting personal information online from a child under 13 years of age (relevant to US traffic).

Player Supply Tag Level

<script src="https://<adserve domain>/basev/vpt.js?userId=${userId}&containerId=${playerId}&format=3&host=${domainName}&query[coppa]=false"></script>
  • Value Type: Boolean

  • Default value: false (query[coppa]=false)

Publisher shall not include or launch any Publisher’s Site(s) on any of Vidazoo’s Services if such Publisher’s Site(s) is directed at U.S. children under 13 as contemplated by the Children’s Online Privacy Protection Law, as amended (“COPPA”), without informing Vidazoo, by changing the above macro to "true" (query[coppa]=true) prior to launching any of such Publisher’s Site(s) on any of Vidazoo’s Services.

Player UI Level

If a player is used with content that is directed at children under the age of 13 years, you must set the player as "COPPA". To do so, you can use the toggle button at the player level to set the COPPA parameter on. When turned on, all traffic to this player will be treated as COPPA compliant.

​​

Demand Tag Level

If a tag is to be called by a player that is implemented on a site whose content is directed at children under the age of 13 years, you must set the Demand tag as "COPPA".To do so, you can use the toggle button at the demand tag to set the COPPA parameter on.

Scenario Level

If a scenario is dedicated to traffic coming from a player that is implemented on a site whose content is directed at children under the age of 13 years, you must set the Scenario as "COPPA", so that only demand tags that are flagged as COPPA compliant will enter it. When turned on, all traffic to this scenario will be treated as COPPA compliant.