AdOpt is a CMP - Consent Management Platform, that allows you to build a transparent and trustful relationship with your website visitors.
Thus, all visitors who access your site will be approached by the banner with a notification that asks for the consent of each one of them in a direct, free, informed and detailed way.
Below are the detailed steps that process this consent registration at AdOpt.
How does the AdOpt cookie banner work?
This is an example of how the platform works: 1. The visitor accesses your site.
2. AdOpt verifies if this access is from a new visitor (i.e., already has the AdOpt cookie, or not) 2.1 - If yes, the banner is not shown and only the controller is visible in the corner of the site (controller = little widget with the AdOpt logo, or your company logo) 2.2 If not, AdOpt will treat you as a new visitor. 2.3 Tags classified as Required/Essential are triggered.
4. It configures your preferences, and records the listing of each one of the cookie categories and the tags present, selected.
5. When you click on "Accept", AdOpt generates a unique cookieID for that visitor, which is stored in his/her browser.
7. They are encrypted and stored individually, in the "Consent Log" session within the AdOpt Platform at dash.goadopt.io/consent-log.
**8. If the AdOpt Account Owner, for that website, has integrated AdOpt auto-blocking with Tag Manager. ** Whenever this visitor accesses the website, the list with the tags authorized or not (item 6.3) will be dropped in the visitor's browser. Thus, at each new access the tags, within GTM, consult the AdOpt list to be triggered, or to be inactive for that single access.
9. If the visitor makes an opt-out request: a - AdOpt updates the CookieID that made the request, with a "mark/tag" classifying this cookie as inactive/opt-out. Thus, within the AdOpt system this "CookieID" will be unusable, and only serve for registration purposes - proof of consent.
b - The 2(two) emails are fired notifying the Visitor (if identified) and the website/company account manager. b.1 - The company receives this email and can analyze if there are other integrations that use this information to then, follow up on the request in other integrated systems. (systems, call backs, and APIs) b.1.1 - If you don't have any data associated with the cookie, you don't need to do anything. For, in AdOpt will be only the anonymous information for purposes of proof of consent, whose copy you have already received in the e-mail. b.2 - If the Visitor has also informed the e-mail, you should use this data to exclude him from all other systems, using it as an access key, for your data mapping. (here is an article on data mapping) b.2.1 - If you have in your files, the notification that proves that the exclusions were made, use it in the visitor's email for this matter.
b.3 - The Visitor is notified, by a pop-up and by a link - in the footer of the e-mail received, that takes him/her to an educational, and public, environment that teaches him/her how to manually delete Cookies from his/her Browser.
c - AdOpt keeps this record in its database, informing you that the CookieID #abc.example.123 made a request at that moment (date/time). So, in case you need it for use in legal needs, and privacy audits, it will be easily accessible.
© AdOpt since 2020 • Made by people who love🍪