Template:GDPR-Macro: Difference between revisions

From Technical Specifications
Jump to navigation Jump to search
No edit summary
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
==IAB TCF 2.0 (GDPR macro)==
==IAB TCF 2.0 (GDPR macro)==
iq digital only admits technology service providers (vendors) for the delivery of advertisements and coordinated tracking that comply with the rules of IAB-TCFv2.0 (Transparency and Consent Franemwork) and have been approved for inclusion on our customers websites (see: ''' [[Technology provider|Vendorlist iq digital]]'''.
iq digital only admits technology service providers (vendors) for the delivery of advertisements and coordinated tracking that comply with the rules of IAB-TCFv2.0 (Transparency and Consent Franemwork) and have been approved for inclusion on our customers websites (see: ''' [[Technology provider|Overview technology provider]]''').
<br/><br/>
<br/><br/>



Latest revision as of 13:07, 21 March 2022

IAB TCF 2.0 (GDPR macro)

iq digital only admits technology service providers (vendors) for the delivery of advertisements and coordinated tracking that comply with the rules of IAB-TCFv2.0 (Transparency and Consent Franemwork) and have been approved for inclusion on our customers websites (see: Overview technology provider).

The provision of tracking (e.g. tracking pixels) for advertising media or 3rd party redirects must be inclusive GDPR macro (gdpr and gdpr_consent). The creator of the tracking /3rd-party URL makes sure that these parameters are replaced with its ID value (GVL-ID), added only once and passed to services that expect and can handle them correctly.

URL parameter Corresponding Macro Representation in URL*
gdpr GDPR &'gdpr=${GDPR}
gdpr_consent GDPR_CONSENT_XXXXX -
XXXXX represents the numerical Vendor ID (Global Vendor List)
&gdpr_consent=${GDPR_CONSENT_XXXXX}
Example: &gdpr_consent=${GDPR_CONSENT_123} for Vendor ID 123.

Source: IAB GDPR-Transparency-and-Consent-Framework.

* The actual provision of the parameters within the final URL may differ from the above example with respect to separators (& or ;).