AdOpt is a consent management platform that allows you to build a relationship of transparency and trust with your website visitors.

So, every visitor who accesses your site will be greeted by a banner with a notification asking for their consent in a free, direct, informed, and detailed manner.

Below is a step-by-step explanation of how consent registration works in AdOpt.

1. The visitor accesses your site.

2. AdOpt checks if this access is from a new visitor (meaning they don't have the AdOpt cookie).

   1 – If yes, the banner is not displayed, and only the controller (a small dot with the AdOpt or your site's logo) is visible in the corner of the site.

   2.2 If not, AdOpt treats them as a new visitor.

   2.3 Necessary/Essential tags are triggered.

3. The visitor receives a privacy setup notification from AdOpt, including:

   1 – A list of third-party Tags/Cookies and their classification by the AdOpt site manager.

   3.2 – Public links to the Privacy Policy and Terms of Use.

   3.3 – Public links to AdOpt's opt-out page for that site.

4. The visitor configures their preferences, with the option to detail the list of each category of cookies and present tags.

5. Upon clicking "Accept," AdOpt generates a unique CookieID for that visitor, which is stored in their browser.

6. Consent information, including:

   1 – Date and Time,

   6.2 – Anonymized CookieID,

   6.3 – An updated list of accepted or rejected Tags and Cookies,

   6.4 – The version of the Privacy Policy and Terms of Use available at that time,

   is individually recorded in the "Consent Log" within the AdOpt platform (logged area).

7. If the AdOpt banner for the respective site has been integrated AdOpt with Tag Manager, whenever this visitor accesses the site, the list of authorized or unauthorized tags (item 6.3) will be in the visitor's browser.

   – Here's a tutorial on blocking third-party tags

   So, with each new visit, the tags in GTM check AdOpt's list to determine whether they should be activated or inactive for that unique visit.

8. If the visitor submits an opt-out request:

   a – AdOpt updates the CookieID that made the request, marking this cookie as inactive/opt-out. This way, within the AdOpt system, this "CookieID" will be invalidated and will only serve as a record for proof of consent.

   b – Two emails are sent to notify the data subject (if identified) and the site/company manager.

   1 – The company receives this email and can analyze whether there are other integrations that use this information to proceed with the request in other integrated systems (systems, call backs, and APIs).

   b.1.1 – If you have no data associated with the cookie, you don't need to take any action. AdOpt will only have anonymous information for proof of consent, a copy of which you have already received in the email.

   b.2 – If the data subject has also provided an email, you should use this data to exclude them from all other systems, using it as an access key through your data mapping.

   – Here's an article on data mapping

   b.2.1 – If it's in your processes to notify that the deletions have been made, use the data subject's email for this notification.

   b.3 – The data subject is notified through a pop-up and a link in the email footer that directs them to an educational and public environment that teaches them how to manually delete cookies from their browser.

   – Here's the tutorial sent to the data subject

   c – AdOpt maintains this record in its database, indicating that the CookieID #xyz.example.1234 made a request at that moment (date/time). So, if you need it for legal bases and privacy audits, it will be easily accessible.

This is a fairly comprehensive breakdown of the process!

If you feel that any part of how a cookie banner works is missing, please feel free to write to us here or leave a comment for us!

Thank you very much! The AdOpt Team.