Skip to content
Cookie consent with accessible dialog, agnostic tag triggers and conditional content, script and embed hooks.
JavaScript CSS
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.

Cookie Consent

Build Status

JavaScript utility library

  • No dependencies
  • Customizable cookie types (required, pre-checked, labeling)
  • Conditional script tags, iframes and elements based on cookie consent and type

Built with ❤️ by GRRR.

Screenshot of the GDPR proof cookie consent dialog from @grrr/cookie-consent


$ npm install @grrr/cookie-consent

Note: depending on your setup additional configuration might be needed. This package is published with untranspiled JavaScript, as EcmaScript Modules (ESM).


Import the module and initialize it:

import CookieConsent from '@grrr/cookie-consent';

const cookieConsent = CookieConsent({
  cookies: [
      id: 'functional',
      label: 'Functional',
      description: 'Lorem ipsum.',
      required: true,
      id: 'marketing',
      label: 'Marketing',
      description: 'Lorem ipsum.',
      checked: true,

Conditional scripts

Conditionally show script tags. Add the data-cookie-consent-attribute with the id of the required cookie type, and disable the script by setting the type to text/plain:

// External script.
<script src="https://..." data-cookie-consent="marketing" type="text/plain"></script>

// Inline script.
<script data-cookie-consent="marketing" type="text/plain">
    alert('hello world');

Conditional iframe embeds

Conditionally show or hide iframe embed. Add the data-cookie-consent-attribute with the id of the required cookie consent type, and disable the iframe renaming the src-attribute to data-src:

<iframe data-cookie-consent="marketing" data-src="https://..."></iframe>

Conditional content

Conditionally show or hide elements. Add the data-cookie-consent-<state>-attribute with the id of the required cookie consent type. There are two types of state: accepted and rejected.

<div data-cookie-consent-accepted="marketing" hidden>Accepted</div>
<div data-cookie-consent-rejected="marketing" hidden>Rejected</div>


  • When hiding, the module will add aria-hidden="true" and style="display: none;" to remove it from the DOM.
  • When showing, the module will remove any inline set display style, along with any hidden or aria-hidden attributes.


All options are optional and will fallback to the defaults, except the array of cookies.

  prefix: 'cookie-consent', // The prefix used for styling and identifiers.
  append: true,             // By default the dialog is appended before the `main` tag or
                            // as the first `body` child. Disable to append it yourself.
  cookies: [                // Array with cookie types. 
      id: 'marketing',      // The unique identifier of the cookie type.
      label: 'Marketing',   // The label used in the dialog.
      description: '...',   // The description used in the dialog.
      required: false,      // Mark a cookie required.
      checked: false,       // The default checked state (only valid when not `required`).
  labels: {                 // Labels to provide content for the dialog.
    title: 'Cookies & Privacy',
    description: '<p>This site makes use of third-party cookies. Read more in our 
                  <a href="/privacy-policy">privacy policy</a>.</p>',
    button: 'Ok',
    aria: {                 // Some `aria-label`s to improve accessibility.
      button: 'Confirm cookie settings',
      tabList: 'List with cookie types',
      tabToggle: 'Toggle cookie tab',


CookieConsent(options: object)

Will create a new instance.

const cookieConsent = CookieConsent({
    cookies: [
        // ...

To make the instance globally available (for instance to add event listeners elsewhere), add it as a global after the instance has been created:

const cookieConsent = CookieConsent();

window.CookieConsent = cookieConsent;


Will fetch the dialog element, for example to append it at a custom DOM position.

document.body.insertBefore(cookieConsent.getDialog(), document.body.firstElementChild);


Will show the dialog element, for example to show it when triggered to change settings.

el.addEventListener('click', e => {


Will hide the dialog element.

el.addEventListener('click', e => {

isAccepted(id: string)

Check if a certain cookie type has been accepted. Will return true when accepted, false when denied, and undefined when no action has been taken.

const acceptedMarketing = cookieConsent.isAccepted('marketing'); // => true, false, undefined


Will return an array with preferences per cookie type.

const preferences = cookieConsent.getPreferences(); 

// [
//   {
//     "id": "analytical",
//     "accepted": true
//   },
//   {
//     "id": "marketing",
//     "accepted": false
//   }
// ]

on(event: string)

Add listeners for events. Will fire when the event is dispatched from the CookieConsent module. See available events.

cookieConsent.on('event', eventHandler);


Events are bound by the on method.


Will fire whenever the cookie settings are updated, or when the instance is constructed and stored preferences are found. It returns the array with cookie preferences, identical to the getPreferences() method.

This event can be used to fire tag triggers for each cookie type, for example via Google Tag Manager (GTM). In the following example trackers are loaded via a trigger added in GTM. Each cookie type has it's own trigger, based on the cookieType variable, and the trigger itself is invoked by the cookieConsent event.


cookieConsent.on('update', cookies => {
  const accepted = cookies.filter(cookie => cookie.accepted);
  const dataLayer = window.dataLayer || [];
  accepted.forEach(cookie => dataLayer.push({ 
    event: 'cookieConsent', 


No styling is being applied by the JavaScript module. However, there is a default stylesheet in the form of a Sass module which can easily be added and customized to your project and its needs.


View the base stylesheet.

Note: no vendor prefixes are applied. We recommend using something like Autoprefixer to do that automatically.


With the styling from the base module applied, the interface will look roughly like this (fonts, sizes and margins might differ):

Screenshot of the GDPR proof cookie consent dialog from @grrr/cookie-consent

You can’t perform that action at this time.