The transfer of approval information (IAB TCF v2 "TC-String") to AdSpirit can take place in two ways:
- manually
- automatic
1. Manually transferred
To pass the Consent String manually, append the parameters &gdpr_consent=....&gdpr=0/1 to the ad space code.
The publisher should then transmit one or more of the following parameters, depending on whether the publisher uses a CMP:
| &gdpr=1 or 0 | 1 = GDPR applies to the user, e.g. user is in the EU; 0 = GDPR does not apply to the user |
| &gdpr_consent=xxxxx |
TC-string of the user according to IAB CMP Framework |
2. Automatically pick up for async placements
For the automatic retrieval it is necessary that you use the asynchronous placement code. The async script code automatically retrieves the content data from an IAB CMP, if it is available at the time of loading. Otherwise you can use the attribute
data-asm-fetch-gdpr="1"
tell the code to wait for the CMP before loading the code.
3. Automatically fetch for other placement types
Synchronous script and IFrame placements can also retrieve the TC-String automatically. Simply activate the pre-targeting "Automatically fetch GDPR consent string" under "Settings > Other > Pretargeting".
Further information on the subject of settings and effects can be found in the Help under -> GDPR FAQ