Skip to main content
GDPR

How to implement a custom cookie banner


Julian
Forum|alt.badge.img+5
  • Gainsight Employee ⭐️⭐️⭐️
  • 908 replies

In compliance with GDPR, cookie banners are required to inform users of the usage of the cookies in order for the website to be transparent about the data collection practices.

In addition to data protection, cookies also affect the content view of your community. Embedded content, such as YouTube videos, can be visible or not, depending on the user's consent level. If a user does not accept cookies, only a simple URL would be displayed instead then the video itself.

If you use a custom cookie banner, you have to be sure it’s mapped to the CC platform functionality, otherwise the data you want to collect won’t be collected or the content you want to show won’t be visible in the desired way. 

You can read all about the set of cookies levels on CC platform in this article. Ideally, your cookie banner should generate 3 different values for the consent level, which will then be mapped to 3 “internal” levels:

  • Level 1 - User session is stored

  • Level 2 - Allowing Google analytics to track user’s visit anonymously

  • Level 3 - Allowing Google analytics and embedded content (YouTube videos, virtual board etc.)

So what needs to be done?
 

The mapping itself is done by our Support team. Your responsibility is to inform us that you use a custom cookie banner and to make sure that the generated cookies have static values. If the cookie value is dynamic, meaning that for each session the value is different, then it won’t be possible for us to map it to platform functionality.

Also, you need to include information about cookies in your Terms & Conditions page. By default this page already includes information on our cookie policy.

Once the cookies are mapped, you are good to go!

Did you find this topic helpful?

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings