General Actions:
TCF2
Last modified by Pavla Roháčová on 2020/12/09 10:46
TCF2 unifies the method of forwarding the user's consent to the personal data processing between various advertising technologies, for example between adserver and advertiser's system, between adserver and SSP...
For more information regarding specification see IAB
What is needed to use TCF2 in adserver:
- you need CPM for user consents managing - adserver doesn't support this functionality
- The CMP must be able to pass the user's consent to the browser/adserver using unified manner according to the IAB
- The adserver must be set to work with TCF-2
NOTTE! Enabling this feature can slow down running campaigns with specific targeting that requires a cookie or specific user consent
- capping
- regions
- IP
- OS
- browser
- keyword
- URL parameters/ adserver code
- retargeting
Setting up work with TCF2 in adserver
- Log in to the Install admin account Přihlaště se na účet Install admin
- Click on "My account" setting in the upper right corner
- Activate the option "Applying TCF2 when selecting Ads.."
Forwarding consent via TCF2 to 3rd parties:
Sometimes you need to pass information about user conset to the 3rd parties, such as the advertiser who provided you with the display code
- insert following part to the adserver compatible placeholder part in advertisers code:
- %%GDPR%%
- %%GDPR_CONSENT_STRING%%
