How do site notices work?

[TeresaChavez]

1. What should happen when one clicks "Accept" in the consent tool? Does a cookie get set? If so can you tell me the name and domain it's set on?
   • The consent tool should now reads 'Accept Changes' (This was updated - when it was 'Accept' people were getting confused and thinking it was the same as Accepting consent.) In this case, a cookie gets set. It's the cookies of whichever vendors were opted out of so we can't tell you a specific domain or cookie name as there are a lot of them.
   • In the case of the 'Accept' button in our banner/barrier, the cookie that drops is our consent cookie named '_evidon_consent_cookie'. There are a few options on Step 1 (Countries & Languages in the wizard) as to what domain it gets dropped under. Generally it will  be under the root domain of the site the notice is running on.
2. Is this the same behavior if the user clicks on "Accept" when they first get the notice?
   • No, Accept on the banner/barrier is consent acceptance. 'Apply Changes' on the consent tool is confirming the users opt out choices and then firing off said opt outs.
     Withdraw consent removes the consent cookie (_evidon_consent_cookie) causing the banner/barrier to reappear for that user on future visits to the site. Consent was withdrawn so we 'reset' the acceptance flow
3. Our U.S. users are seeing the consent banner that is targeted to EU users.  This is happening across all our sites. How can I resolve this?

   • If there is no experience set up for a locale, the banner experience will display the default notice experience. If your users are seeing the EU consent banner regardless of location, this means the EU is the default notice.
     To fix this you will need to add another country as the default. For example, make the U.S. the default country, then ensure that the consent type is set to "no consent notification" so the banner doesn't display. 
     If anyone comes from outside of EU countries, the banner will default to the US setup and nothing will display.

4. What happens when a user withdraws consent?
   • When a user chooses to 'withdraw consent', our 'consent cookie' (_evidon_consent_cookie) is removed from that user's browser, starting the consent process all over again.
   • 
   • We can't remove cookies from other vendors, so vendor cookies (e.g. Facebook, Twitter, etc) will stay on the user's device, but because the consent process is restarted, the vendor tags are blocked from communicating with and reading that cookie, making it unusable

5. What should a site user expect when they select the Decline button? Is there any way to customize this functionality?

   When a site user selects the Decline button in a banner or barrier,  the consentDeclined event is triggered. This hides the notice for the current session, but when the site user opens a new session, either by refreshing or opening a new browser, they will be asked to decline again.

   If you would like a different experience for your site visitors, we recommend adding code into the consentDeclinedCallback callback function. Here is the exact function, if it is not included in your tag:

   window.evidon.consentDeclinedCallback = function () {
   
   // this is executed if the user explicitly declines giving consent by
   
   // using a Decline button

   }

   If you would like to suppress the banner or barrier from showing again, you can add the following code inside that function:

   window.evidon.notice.dropSuppressionCookie(# of days to suppress);

   When you call this API function, the banner or barrier will not display for the number of days provided in the call. For example, window.evidon.notice.dropSuppressionCookie(30); will suppress the UI for 30 days.

   You can also take custom actions inside the decline callback.