Using creatives with third-party technologies
Display & Video 360 customers can use creatives that include third-party technologies to provide functionality such as ad serving or independent reporting. Both the customers and the vendors who provide these technologies should respect their EU User Consent Policy obligations. If the vendor uses cookies or other local storage, the vendor will want to determine the end-user's consent, and Display & Video 360 supports macros for customers to configure how consent signals are passed to vendors.
On GDPR Inventory signals from IAB’s Transparency and Consent Framework (TCF), Display & Video 360 only serves ads with third-party technologies when all vendors meet the following criteria:
- Each vendor who is registered on the IAB Europe TCF Global Vendor List (GVL) needs to register for at least one purpose and have obtained a valid legal basis for that purpose.
- Each vendor who is not registered on the IAB Europe TCF Global Vendor List (GVL) must be included in the Additional Consent signal (passed in OpenRTB as
consented_providers_settings).
Macros
Display & Video 360 supports the following macros for passing GDPR-related information via third-party pixels for GDPR Inventory:
${GDPR}: 0 or 1, 0 = traffic from a non-GDPR region, 1= traffic from a GDPR region${GDPR_CONSENT_xxxxx}where xxxxx is the numeric Vendor ID of the vendor receiving the TC string: TC string received in bid request.addtl_consent=${ADDTL_CONSENT}where ADDTL_CONSENT is a dot-separated list of user-consented Google Ad Tech Provider (ATP) IDs, as described in Additional Consent signal.
