Cookie consent banner API

Super admins and users with permission to edit website settings can customize visitor cookie tracking and consent banners to comply with EU cookie laws and the General Data Protection Regulation (GDPR).

A cookie consent banner allows visitors to opt in or opt out of being tracked in your HubSpot account with cookies. This feature works for all HubSpot pages as well as any external pages with your HubSpot tracking code installed. Customize the cookie tracking settings and cookie consent banner.

In this article, learn how to manage the cookies that are added to a visitor's browser through the cookie consent banner.


Remove cookies

_hsp.push(['revokeCookieConsent']);

Remove the cookies created by the HubSpot tracking code that are included in the consent banner under GDPR, include the HubSpot cookies related to tracking the visitor. As a result of the cookies being removed, the visitor would see the cookie consent banner on their next page load, as they would appear as a new visitor.

This function does not remove cookies placed by non-HubSpot banners. You can find the specific list of cookies that will be removed on HubSpot's Knowledge Base

If cookie blocking is turned on, this function will revoke consent so any third-party cookies will not be updated or dropped during future visits to the website. 

/* Example code to remove the consent banner cookies when a visitor clicks an element with the 'removeCookies' id. */ var _hsp = window._hsp = window._hsp || []; document.getElementById("removeCookies").onclick = function() { _hsp.push(['revokeCookieConsent']); };

Place do not track cookie

_hsq.push(['doNotTrack']);

Places the __hs_do_not_track cookie in the visitors browser, which will prevent the HubSpot tracking code from sending any information for the visitor.

You can remove the cookie by calling the function again and including the {track: true} argument:
_hsq.push(['doNotTrack', {track: true}]);

Please note: this function prevents all information from being collected by the tracking code, including anonymized traffic and custom event data.

/* Example code to place the __hs_do_not_track cookie for the visitor when they click an element with the 'doNotTrack' id. */ document.getElementById("doNotTrack").onclick = function() { _hsq.push(['doNotTrack']); };

Get privacy consent status

_hsp.push(['addPrivacyConsentListener', callbackFunction]);

Get the privacy consent status of the current visitor. There are 3 categories of consent that can be used to provide more granular control to the user. These each have their own keys within the consent.categories object:

  • consent.categories.analytics
  • consent.categories.advertisement
  • consent.categories.functionality

The callbackFunction will be called, depending on the state of the page:

  • If the banner is not enabled, or if the visitor has previously seen the banner and clicked accept or decline:
    • the callbackFunction will be called immediately if the banner code is already loaded.
    • the callbackFunction will be called after the tracking code loads if the function is pushed to _hsp before the tracking code loads.
  • If the banner is enabled, the callback function will be called when the visitor clicks on the accept or decline button.  
// Log the analytics category consent status of the current visitor to the console var _hsp = window._hsp = window._hsp || []; // analytics _hsp.push(['addPrivacyConsentListener', function(consent) { console.log(consent.categories.analytics); }]); // advertisement _hsp.push(['addPrivacyConsentListener', function(consent) { console.log(consent.categories.advertisement); }]); // functionality _hsp.push(['addPrivacyConsentListener', function(consent) { console.log(consent.categories.functionality); }]); // or it can all be done in one call _hsp.push(['addPrivacyConsentListener', function(consent) { console.log(`analytics: ${consent.categories.analytics}`); console.log(`advertisement: ${consent.categories.advertisement}`); console.log(`functionality: ${consent.categories.functionality}`); }]);

Cookies not by category

Please note: This is provided for backward compatibility with older scripts. For all new websites you should use the cookies by category method, giving more granular control over cookie activation.

_hsp.push(['addPrivacyConsentListener', callbackFunction]);

Allows you to get the true or false privacy consent status of the current visitor.

The callbackFunction will be called, depending on the state of the page:

  • If the banner is not enabled, or if the visitor has previously seen the banner and clicked accept or decline:
    • the callbackFunction will be called immediately if the banner code is already loaded.
    • the callbackFunction will be called after the tracking code loads if the function is pushed to _hsp before the tracking code loads.
  • If the banner is enabled, the callback function will be called when the visitor clicks on the accept or decline button.  
// Log the consent status of the current visitor to the console var _hsp = (window._hsp = window._hsp || []); _hsp.push(["addPrivacyConsentListener", function (consent) { if (consent.allowed) { console.log('something') } }])

The callbackFunction accepts a consent object as its only argument.

The consent object has a single allowed property that will be true if:

  • The cookie consent banner is not enabled, or is enabled in notify-only mode.
  • The visitor clicks accept on the banner when opt-in mode is enabled.
  • The visitor has previously clicked accept on the banner when opt-in mode is enabled.

The property will be false if the consent banner is enabled in opt-in mode and the visitor clicks or has previously clicked the decline button.

Call the showBanner function to resurface the banner, enabling website visitors to make changes to their consent preferences. For example:

​​var _hsp = window._hsp = window._hsp || []; ​​_hsp.push(['showBanner']);

The behavior ofshowBannervaries by policy and is only available for Opt-In and Cookie-By-Category policies. 

For Opt-In policies, calling showBanner  will cause the banner to reappear, as shown in the video below:

HubSpot Video

 

For Cookies-By-Category policies, calling showBanner will cause the modal for selecting each category to reappear, as shown in the video below:

HubSpot Video

UI Examples

This functionality can be made available to visitors in the form of buttons/links on your website that they can use to re-open the banner and edit their preferences. The following are examples with code. 

Button

A button, often placed in the website footer.

<button type="button" id="hs_show_banner_button" onClick="(function(){ var _hsp = window._hsp = window._hsp || []; _hsp.push(['showBanner']); })()" > Cookie Settings </button>#hs_show_banner_button { display: inline-block; text-align: center; height: 50px; background-color: #425b76; border: 1px solid #425b76; border-radius: 3px; padding: 10px 16px; text-decoration: none; color: #fff; font-family: inherit; font-size: inherit; font-weight: normal; line-height: inherit; text-shadow: none; }
HubSpot Video

 

Fixed position button

A button with fixed positioning on the bottom of the screen. This kind of button has the advantage of being readily available and easy to find, while being somewhat obtrusive UX.

<button id='hs-hud-cookie-settings' onClick="(function(){ var _hsp = window._hsp = window._hsp || []; _hsp.push(['showBanner']); })()"> Cookie Settings </button> button#hs-hud-cookie-settings { position: fixed !important; bottom: 0px; right: 10px; color: white; background-color: #425b76; padding: 5px; border-top-right-radius: 5px; border-top-left-radius: 5px; border-width:0; appearance:none; }
HubSpot Video

 

A link or highlighted text.

<a id="hs-cookie-settings-link" onClick="(function(){ var _hsp = window._hsp = window._hsp || []; _hsp.push(['showBanner']); })()"> Cookie Settings </a>#hs-cookie-settings-link { cursor: pointer; }
HubSpot Video

 

Block third party cookies manually

The HubSpot Consent Banner supports manual handling of third party tracking technologies and cookies. It's recommended to use manual handling if you have a complicated website and/or a dedicated web developer. If auto-blocking does not work for your site, manual blocking is also a good option.

Manual blocking is implemented through the Cookie Banner Consent Listener API. This API is used to prevent tracking technologies from running until they have consent. To get started, take a look at the examples below.

General usage

If you want to install a tracking script onto your website to display targeted ads to visitors. You could use something like the below:

<script src=”https://my.advertisement.script.com/ads”></script>

When this script is pasted into the head HTML of a page on a website it would run anytime someone visits that page, regardless of their consent status. Visitors will have cookies placed on their browser without consent.

To prevent the script from running without consent, you can use the HubSpot Cookie Banner Consent Listener API to install the script when the visitor has consented to its cookies. Consent listeners are functions that run whenever the visitor submits their consent. To use this functionality, a consent listener needs to be created that adds the script to the page if the visitor has consented to advertisement cookies.

<script> var _hsp = window._hsp = window._hsp || []; _hsp.push(['addPrivacyConsentListener', (consent) => { if (consent.categories.advertisement) { const script = document.createElement('script'); script.src = "https://my.advertisement.script.com/ads"; document.head.appendChild(script) } }]) </script>

This script will register the consent listener with the cookie banner. When consent to cookies is submitted, the consent listener will run, adding HubSpot's third party ads script to the page.

Example: Google Tag

Google Tag or gtag.js can be used to add Google Analytics. For example:

<!-- Google tag (gtag.js) --> <script async src="https://www.googletagmanager.com/gtag/js?id=GA_TRACKING_ID"></script> <script> window.dataLayer = window.dataLayer || []; function gtag(){window.dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'GA_TRACKING_ID'); </script>

To load Google Analytics when analytics consent has been given, the gtag script needs to be added when consent is given:

<!-- Google tag (gtag.js) --> <script> var _hsp = window._hsp = window._hsp || []; _hsp.push(['addPrivacyConsentListener', (consent) => { if (consent.categories.analytics) { const script = document.createElement('script'); script.src = "https://www.googletagmanager.com/gtag/js?id=GA_TRACKING_ID"; script.async = 'true' document.head.appendChild(script) } }]) </script> <script> window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} gtag('js', new Date()); gtag('config', 'GA_TRACKING_ID'); </script>

Example: HotJar

HotJar is another example of analytics tracking. For example:

<!-- Hotjar Tracking Code --> <script> (function(h,o,t,j,a,r){ h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)}; h._hjSettings={hjid:HOT_JAR_ID,hjsv:6}; a=o.getElementsByTagName('head')[0]; r=o.createElement('script');r.async=1; r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv; a.appendChild(r); })(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv='); </script>

To ensure Hotjar runs when analytics consent is given, the consent listener can be added.

<!-- Hotjar Tracking Code --> <script> var _hsp = window._hsp = window._hsp || []; _hsp.push(['addPrivacyConsentListener', (consent) => { if (consent.categories.analytics){ (function(h,o,t,j,a,r){ h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)}; h._hjSettings={hjid:HOT_JAR_ID,hjsv:6}; a=o.getElementsByTagName('head')[0]; r=o.createElement('script');r.async=1; r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv; a.appendChild(r); })(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv='); } }]) </script>

Google Consent Mode v2 is a framework designed to integrate website visitor consent preferences with Google's advertising and analytics tools. With it, websites can adjust how these tools behave based on the consent status of website visitors, particularly regarding cookies and data collection. Even when visitors don’t consent to cookies, Google services can operate in a limited mode and collect basic interactions without breaching privacy expectations. 

If you use HubSpot's native Google Analytics 4 or Google Tag Manager integrations, learn how to support Google Consent Mode v2

You will need to manually integrate Google Consent Mode v2 if either of the following scenarios are true:

  • You use a HubSpot cookie banner on an externally-hosted website or CMS.
  • You use a HubSpot cookie banner on the HubSpot CMS, and you use a code snippet to integrate with either Google Analytics or Google Tag Manager. 

To manually integrate Google Consent Mode v2:

  • Set up a cookie consent banner in HubSpot with an opt-in policy type targeting EEA, EU, and UK visitors.
  • Follow Google’s instructions for implementing Consent Mode v2
  • Include the below code snippet in the head tag of your site. This snippet will update the consent status when it’s submitted via the HubSpot cookie banner. The snippet below: 
    • declares functions required to push consent updates to Google's products.
    • adds a consent listener that the cookie banner will call when consent becomes available.
    • translates cookie banner consent into Google consent and sends it to Google's products using the util functions we declared earlier
<script> var _hsp = window._hsp = window._hsp || []; window.dataLayer = window.dataLayer || []; function gtag(){dataLayer.push(arguments);} // set up default denied consent gtag('consent', 'default', { 'analytics_storage': 'denied', 'ad_storage': 'denied', 'ad_user_data': 'denied', 'ad_personalization': 'denied', 'region': ["AT", "BE", "BG", "HR", "CY", "CZ", "DK", "EE", "FI", "FR", "DE", "GR", "HU", "IS", "IE", "IT", "LV", "LI", "LT", "LU", "MT", "NL", "NO", "PL", "PT", "RO", "SK", "SI", "ES", "SE", "UK", "CH"] }); // send consent updates from the HubSpot Cookie Banner _hsp.push(['addPrivacyConsentListener', function(consent){ var hasAnalyticsConsent = consent && (consent.allowed || (consent.categories && consent.categories.analytics)); var hasAdsConsent = consent && (consent.allowed || (consent.categories && consent.categories.advertisement)); gtag('consent', 'update', { 'ad_storage': hasAdsConsent ? 'granted' : 'denied', 'analytics_storage': hasAnalyticsConsent ? 'granted' : 'denied', 'ad_user_data': hasAdsConsent ? 'granted' : 'denied', 'ad_personalization': hasAdsConsent ? 'granted' : 'denied' }); }]); </script> // Customer custom gtag code below: <script async src="https://www.googletagmanager.com/gtag/js?id=TAG_ID"> </script>

Was this article helpful?
This form is used for documentation feedback only. Learn how to get help with HubSpot.