Skip to main content

3. Build Conditional Logic for GDPR for Web

Conditional firing is a method to manually control firing of third-party vendors on page or in your mobile application. In essence it is a script or a logic that takes care of those third-party resources and forces them to obey the CMP signals.

You need to set up conditional firing logic in two cases:

  • If you are using (advertising) vendors or other resources that do not participate in the IAB Europe Transparency and Consent Framework. The benefit of the TCF is that it puts a contractual obligation on the advertising vendors to wait for the consent signal of the CMP that is present on the page before they can pass the bid request. This means that the vendors that do not participate in the TCF, do not have such restrictions and can just release their assets on page load. In order to prevent this from happening, website owners should use conditional firing: a technical means to make those third parties respect the CMP and listen to its signals.

  • Sometimes even the Transparency and Consent Framework’s vendors can drop cookies without consent. For example, some of them skip the ePrivacy compliance and focus on GDPR, claiming legitimate interest for their data processing activities. This is why we recommend you to check if this approach works for you and what is the extent of your liability. Conditional firing is a simple way to control the TCF vendors on your sites and enforce ePrivacy compliance.

Hardcoded Tags
Tags fired through a Tag management solution