Checking cookie consent from your own code

When a script of your own should only run once a visitor has agreed to cookies, ask ClickWhale what that visitor has allowed. The same calls let you build your own consent buttons and links.

Wrap it in DOMContentLoaded. Your code runs before ClickWhale's own script, so ClickWhale doesn't exist yet at the moment your code first runs. The listener in the example below waits until it does.

Waiting for consent

Ask, and run your code only when the answer includes the category you need:

<script>
document.addEventListener("DOMContentLoaded", function () {
  ClickWhale.consent.on(function (granted) {
    if (granted.indexOf("analytics") !== -1) {
      // the visitor has agreed to analytics
    }
  });
});
</script>

ClickWhale.consent.on calls your function straight away with what the visitor has already agreed to, and again each time they change their mind, so you don't have to worry about which happened first.

For code on the site-wide Functional, Analytics or Marketing pages you don't need any of this: those pages already wait for their category. See Site-wide custom code.

The calls

Two attributes do the same without a script:

• data-cw-open-consent on a link or button reopens the cookie dialog, for a "Cookie settings" link in your footer.
• data-cw-allow="functional" on a button grants that one category. It's the same mechanism behind the Allow and play placeholder on a blocked video.

Timing

• Code in a category page runs late. It's held inert until the visitor accepts, so it can start seconds after the page did, or on a later page, or never. Don't assume it runs during page load.
• Withdrawing doesn't unload anything. A script that already ran keeps running until the visitor navigates. Narrowing consent takes full effect on the next page.

Common issues