Implementing cookie consent pop up in Kentico CMS - update to munchkin code

MegTucker
Level 1

Implementing cookie consent pop up in Kentico CMS - update to munchkin code

Hi everyone,

Hoping to gain some guidance on implementing a cookie consent pop up in our Kentico CMS and making the necessary updates to our munchkin code so that it is triggered when someone 'accepts' cookies in the Kentico generated pop up.

 

We will be implementing a cookie consent pop up each time a new user visits our website for the first time. (resources below for reference)

Cookies in Kentico:

https://docs.xperience.io/k12sp/configuring-kentico/data-protection/working-with-cookies

Instructions on how to add cookie consent pop up in v12.0 of Kentico:

https://docs.xperience.io/k12sp/configuring-kentico/data-protection/adding-cookie-law-consent-to-web...

 

I'm wondering what changes we need to make to our munchkin code to ensure it is continues to operate in a similar manner as when the 'Do Not Track' settings in Marketo are on. I.e.  A users web page visits and clicked links will not be sent to Marketo unless they have clicked 'accept' on our kentico generated cookies pop up. 

 

Further, these are the 3 cookie levels we would display to the user in the cookie consent pop up.

 

Simplified cookie level Corresponding API level Description
No cookies System Enables the minimum cookies required for the website to work, and remembers whether the user allows cookies or not.
Only essential cookies Essential Enables all cookies required for website functionality, but no tracking cookies.
All cookies All Enables all cookies used on the website.

 

Any help would be appreciated.

Meg

1 REPLY 1
SanfordWhiteman
Level 10 - Community Moderator

Re: Implementing cookie consent pop up in Kentico CMS - update to munchkin code


A users web page visits and clicked links will not be sent to Marketo unless they have clicked 'accept' on our kentico generated cookies pop up.

Simply do not run Munchkin.init() unless they have clicked accept.

 

You may also make use of the mkto_opt_out option discussed here and here and elsewhere, but it’s not necessary as you can manage whether Munchkin is functional using your own code.