Consent data is transmitted to the vendors in different ways, depending on the integration and the vendor's compliance requirements.
1. IAB Vendors:
While using IAB integration Didomi ensures that for vendors part of the IAB (TCF), consent data is communicated via a standardized consent string known as the "TC String".
This string, encoded in the "euconsent-v2" cookie is generated by the Didomi SDK and shared with all scripts on the page, allowing only consented vendors to process user data.
Tools like Uniconsent TCF Decoder or IABTCF can be used to decode the "Euconsent-v2" cookie string.
Vendors will retrieve information through the __tcfapi function instead of the euconsent-v2 cookie; refer to this article for more information.
2. Custom Vendors:
Custom logic is required to ensure scripts only run when consent is given. This usually means wrapping scripts in conditional checks that verify consent status prior to execution. Management can be manual or through systems like Google Tag Manager, which can trigger scripts based on consent status.
Visit our developer guide for more information.
3. Google Vendors (Google Advertising Products and Google Analytics Products) when Google Consent Mode is enabled:
Google Consent Mode, integrates with platforms like Didomi to adjust the behavior of Google tags according to user consent.
Consent information is communicated through modifications in tag configurations and API calls, which may involve Google Tag Manager or direct changes in the website's source code.
Visit our developer guide for more information.