Consent management platforms allow website or mobile application publishers to easily implement a user consent interface. These tools display a pop-up window on the first visit to a site, present the different purposes and data controllers, retain users' choices and implement solutions to respect these choices. The CMP must allow for the recording and storage of such consent in order to comply with the GDPR and its requirement for proof of consent. This consent must be free, specific, informed and unequivocal. The CMP also allows consent to be passed on, if necessary, to partners.
CMP example :
The law may differ from country to country. It is your responsibility to find out what the law is and to follow it.
By default, our tools look for the presence of a CMP and collect the user's choice.
If our tools do not detect a CMP or if the user refuses consent, then Kwanko will measure the results of your affiliate campaign with an analysis of the information needed to track performance (no personal data is collected).
Our tools are compatible with the TCF v1/v2 standard proposed by the IAB, this standard is available with most consent management platforms. The IAB Kwanko identifier is 702.
Without TCF v1/v2, our tools are also compatible with Axeptio and Onetrust CMPs.
How do you check if your CMP is compliant with TCF v1/v2?
Open your browser's console:
Windows: Ctrl + Shift + K
Mac: Ctrl + Option + K
Windows: Ctrl + Shift + J
Mac: Ctrl + Option + J
Enter the command below: __tcfapi
If you get an Uncaught ReferenceError: __tcfapi is not defined your CMP is not compatible with the TCF v1/v2 standard. Please contact your CMP supplier so that they can help you activate this standard.
Note: If you are using an Axeptio or Onetrust CMP you do not need to do this check. However, you should check that Kwanko is added to the list of authorized partners in your CMP.
What if I don't have a CMP?
It is recommended that you choose a CMP compatible with the TCF v1/v2 standard proposed by the IAB.