GDPR

How to use a Custom Cookie Banner

  • 30 April 2020
  • 0 replies
  • 739 views

Userlevel 2
Badge +3
  • Gainsight Employee: ACE
  • 882 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 inSided 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 inSided 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, unfortunately you can’t do it yourself. 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 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 more information about cookies in your terms & conditions page. By default this page already includes information on our cookie policy, you can also find an example on our own terms & conditions page: https://community.insided.com/site/terms

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


0 replies

Be the first to reply!

Reply