IAB TCF v2.0
Experimental features are subject to change
IAB TCF v2.0
A tracking pixel in Connect can be configured to process user consent in accordance to the IAB TCF v2.0 specification by adding a few parameters and macros to the pixel URL:
- a
TC
parameter with a value of0
or1
to signal if consent should be checked - a
gdpr
parameter with a value of{GDPR}
- a
gdpr_consent
parameter with a value of{GDPR_CONSENT_734}
The gdpr
and gdpr_consent
parameter values are macros that CMPs will look for in order to convey the actual user's consent and must look exactly like above. The CMP will replace these values with actual consent data once the pixel is rendered in a user's browser.
A complete tracking pixel URL, using IAB consent processing could look like the following
https://sandbox.cintnetworks.com/?a=99&i=4500123&e=1&c=1&tc=1&gdpr={GDPR}&gdpr_consent={GDPR_CONSENT_734}
Connect is currently configured to check user consent for the following purposes
- Purpose 1 - Store and/or access information on a device
- Purpose 7 - Measure ad performance
- Purpose 8 - Measure content performance
- Purpose 9 - Apply market research to generate audience insights
- Purpose 10 - Develop and improve products
For more documentation and explanations regarding IAB TCF v2 purposes, check out the official documentation here
https://iabeurope.eu/iab-europe-transparency-consent-framework-policies/
Updated over 3 years ago