Yieldr strives to be compliant with the privacy laws regarding the storage and reading of data. Websites (advertisers and publishers) are required to ask users for consent to store and read a cookie. In order to adhere to the user consent regulations, Yieldr’s technology needs to receive a signal from your website, telling it that the user has consented that 3rd parties (such as Yieldr) are allowed to both store and read data while visiting your website. By processing this signal, Yieldr will be able to adapt its technology in such a way that it adheres to the user consent status.

Using a Tag Management System

The most straightforward method to be compliant to the cookie law is through a Tag Management System (TMS). When you are using a TMS, this will present you with the possibility to load tags only in cases where you see fit. Basically, this means that the compliancy can best be handled by the TMS even before the Yieldr tag gets loaded. If you are using a TMS that allows this functionality, it is not necessary to make any changes to the Yieldr tag. Please review the documentation of your TMS for instructions on implementation.

Through the Yieldr Tag

When the parameter cookies_allowed is passed to the Yieldr tag, the behavior of the tags will change based on the value of the parameter. If the value is 1 (which should also be the default), the behavior will remain unchanged; meaning the Yieldr tag will assign a user ID and start loading its piggyback tags that store/read the necessary cookies. However when the value passed in cookies_allowed equals 0, the Yieldr tag will store user ID = 0 (unidentifiable), and will stop all other processes that would be triggered in a normal fashion. By stopping these processes, no cookies will be placed on the user’s device nor will any data be read from cookies that might have been stored in a previous process.

Did this answer your question?