...
Users consent is submitted via passing the TC String in the tracking URL. When a creative is rendered, the src address of <img> html-tag is sent by the browser via HTTP GET request to Ingenious Server. Also when user clicks on this creative, click request is also sent to Ingenious tracking server.
...
If both platform and ad space have activated TCF, Ingenious suggest parameters for TCF signalling and macros to the advertiser's On-Page Tracking Code Tag and to Creatives Tracking Code Tag on publisher's side.
Note: tracking codes tags already built in to partners or advertisers system are not replaced automatically when TCF is activated or deactivates.
...
The supported URL parameters and the corresponding macros should be added only once and are defined below:
URL parameter | Corresponding Macro | Representation in URL |
|---|---|---|
gdpr | GDPR | &gdpr=${GDPR} |
gdpr_consent | GDPR_CONSENT_XXXXX | &gdpr_consent=${GDPR_CONSENT_XXXXX} |
XXXXX means here the numeric Vendor ID. E.g. &gdpr_consent=${GDPR_CONSENT_123} for Vendor ID 123.
Values to fill in the macros:
Macro | possible values | purpose |
|---|---|---|
${GDPR} | 0 / 1 | 0 gdpr does not apply; 1 gdpr applies |
${GDPR_CONSENT_XXXXX} | URL-safe base64-encoded Transparency & Consent string. | Only meaningful if Encodes the TC string, as obtained from the CMP JS API or OpenRTB |
Nested calls and redirects
...
In order to register on IAB TCF v2.0 Global Vendor List (GVL) we claimed Purposes, Special Purposes, Features and Special Features described in https://iabeurope.eu/iab-europe-transparency-consent-framework-policies/, see “Appendix A: Purposes and Features Definitions”. The lawful bases could be chosen as Consent, Legitimate Interests or Flexible. Wherever we specified Legitimate Interest or Flexible as lawful basis, the Legitimate Interests is documented in our Privacy Policy https://www.ingenioustechnologies.com/privacy-policy/.
ID | Purpose Name | Allowable Lawful Basis | Ingenious Choice |
|---|---|---|---|
P1 | Store and/or access information on a device | Consent | Consent |
P7 | Measure ad performance | Consent, Legitimate Interests | Flexible (both is possible) |
ID | Special Purpose Name | Allowable Lawful Basis | Ingenious Choice |
|---|---|---|---|
SP1 | Ensure security, prevent fraud, and debug | Legitimate Interests | Legitimate Interests |
SP2 | Technically deliver ads or content | Legitimate Interests | Legitimate Interests |
ID | Feature Name | Ingenious Choice |
|---|---|---|
F1 | Match and combine offline data sources. | No |
F2 | Link different devices | Yes |
F3 | Receive and use automatically-sent device characteristics for identification | Yes |
ID | Special Feature Name | Ingenious Choice |
|---|---|---|
SF1 | Use precise geolocation data | No |
SF2 | Actively scan device characteristics for identification | No |
If there is a need for different set of TCF purposes and features, custom Vendor IDs can be set on Platform level by our Customer Success.
...
The resulting URL in the tracking codes tags on the partner side looks like:http://trackignurl.com/amc=a.b.c.d&gdpr=1&gdpr_consent=${GDPR_CONSENT_123}
...
If setup mode is activated for the ad space, TCF params (s. Macros ) appear in ad media tracking code tag and product data feed urls. Partner is to properly obtain and set these params by obtaining the TC String from his CMP.
...
Both Setup and Restrictive modes can be validated using tracking preview mode (Preview Mode )
Example:
Wenn calling a click code with following parameters appended
...