HubSpot Ideas

arinker

Cookie consent banner API – Possibility to set consent status by category via JavaScript

To embed third-party content (YouTube videos, tweets...) in a GDPR-compliant way and with a good UX, it would be helpful to provide the ability to set cookie consent status by category via JavaScript.

 

Then it would be possible to provide a simple switch within a gdpr-third-party-placeholder-info-text instead of having to call the cookie settings. 

 

Example

On major news portals, such as www.spiegel.de or www.sueddeutsche.de, you can flip a switch right on the content.

youtube embeds.png

 

API Suggestion

The API could look like this:

  • Give analytics cookies consent:

 

_hsp.push(['setPrivacyConsent', consent.categories.analytics = true]);

 

  • Revoke analytics cookies consent:

 

_hsp.push(['setPrivacyConsent', consent.categories.analytics = false]);

 

  • Give advertising cookies consent:

 

_hsp.push(['setPrivacyConsent', consent.categories.advertising = true]);

 

  • Revoke advertising cookies consent:

 

_hsp.push(['setPrivacyConsent', consent.categories.advertising = false]);

 

  • Give functionality cookies consent:

 

_hsp.push(['setPrivacyConsent', consent.categories.functionality = true]);

 

  • Revoke functionality cookies consent:

 

_hsp.push(['setPrivacyConsent', consent.categories.functionality = false]);

 

 

Current situation

The following example and screenshots show the current situation. It would be better to have the checkbox directly in the third-party placeholder, without having to open and click through the cookie settings: https://www.hr-heute.com/magazin/eignungsdiagnostik-fehler-bei-der-personalauswahl-minimieren

 

Bildschirm­foto 2023-01-25 um 14.56.23.pngBildschirm­foto 2023-01-25 um 14.56.45.pngBildschirm­foto 2023-01-25 um 14.56.39.png

Final Thoughts

Surely you could build a parallel solution next to the Cookiebanner. However, this brings the following disadvantages. Visitors who have agreed to all cookies must agree again. HubSpot's native cookie scanning and blocking solution must be bypassed, and cookie setting, deleting, and blocking must be set up manually for each third-party-embedded.