...
If both platform and ad space have activated TCF, Ingenious suggest parameters for TCF signaling signalling and macros to the advertiser's On-Page Tracking Code and to Creatives Tracking Code on publisher's side.
Note: tracking codes already built in to partners or advertisers system are not replaced automatically when TCF is activated or deactivates.
...
Inactive mode- This means that TCF macros are neither added to tracking links nor is tracking traffic treated restrictively. There is no TCFv2.0 based filtering for this ad space.
Setup mode without traffic restrictions - TCF macros appear in the ad media tracking links and can be used for setup and testing. Tracking system interprets and stores the TCF signals but there aren’t any restrictions in the request data storage and processing.
Restrictive mode - Ad media tracking links are generated containing macros for TCF. If GDPR applies and there is no sufficient consent, our system will restrict the amount of stored and processed request information according to purposes enabled by enduser.
Inactive Mode
If the platform operator has activated TCF functionality for the platform, the partner will be able to configure TCF mode on the ad space edit page.
The initial TCF mode is set to “Inactive mode” and does not change the default behaviour. This means that neither TCF macros are attached to the tracking links for creatives delivered through this ad space, nor is tracking traffic restricted. No tracking requests based on TCF consensus will be restricted.
Attention: Even if the partner sends reasonable filled GDPR parameters with a request, request processing will not be affected. It is necessary that the option must be set to “Restrictive mode” if requests are to be restricted based on TCF.
Setup mode
If setup mode is activated for the ad space, TCF params (s. Macros ) appear in ad media tracking code and product data feed urls. Partner is to properly obtain and set these params by obtaining the TC String from his CMP.
The parameter &gdpr_consent=${GDPR_CONSENT_XXXXX} contains the vendor id the consent String has to contain the consent for. We interpret the TCF parameters and pass them along with the request for diagnostics. The TCF params are also forwarded on redirects.
In the setup mode we don’t restrict the way we store and process the actual request.
Restrictive mode
In restrictive mode, we restrict the request handling in accordance to TCF policies and TCF features enabled for the given vendor id in the submitted consent string.
Parameter gdpr
If no value is provided, geoIP lookup takes place and GDPR applies for EU IP addresses.
If the parameter is set to 0 GDPR does not apply to request handling
If the parameter is set to 1, GDPR applies and we handle request in restrictive way
Parameter gdpr_consent (consent string)
A valid consent string Is compulsory when GDPR applies. Following restrictions are applied if we don’t encounter users consent for the purposes.
No consent on Purpose 1 - don’t create new cookies, ignore existing cookies
No consent on Purpose 7 - don’t process given tracking request (optout)
Common Infos about TCFv2.0
...