Wiki source code of TCF2

Last modified by Pavla Roháčová on 2020/12/09 10:46

Content · Comments (0) · Attachments (2)

Hide line numbers

 1: 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...
 2: 
 3: For more information regarding specification see [[**IAB**>>https://iabeurope.eu/tcf-2-0/||rel="__blank"]]
 4: 
 5: 
 6: __What is needed to use TCF2 in adserver:__
 7: 
 8: * you need CPM for user consents managing - adserver doesn't support this functionality
 9: * The CMP must be able to pass the user's consent to the browser/adserver using unified manner according to the IAB
10: * The adserver must be set to work with TCF-2
11: 
12: (((
13: **NOTTE! Enabling this feature can slow down running campaigns with specific targeting **that requires a cookie or specific user consent 
14: 
15: * capping
16: * regions
17: * IP
18: * OS
19: * browser
20: * keyword
21: * URL parameters/ adserver code
22: * retargeting
23: )))
24: 
25: (((
26: __Setting up work with TCF2 in adserver__
27: 
28: 1. Log in to the Install admin account Přihlaště se na účet Install admin
29: 1. Click on "My account" setting in the upper right corner
30: 1. Activate the option "Applying TCF2 when selecting Ads.."
31: 
32: __Forwarding consent via TCF2 to 3rd parties:__
33: 
34: Sometimes you need to pass information about user conset to the 3rd parties, such as the advertiser who provided you with the display code
35: 
36: * insert following part to the adserver compatible placeholder part in advertisers code:
37: ** %%GDPR%%
38: ** %%GDPR_CONSENT_STRING%%
39: 
40: (((
41: [[image:tcf2_1.png]]
42: 
43: 
44: [[image:tcf2_2.png]]
45: )))
46: )))

Wiki source code of TCF2

Navigation

AdServer v2