Consent management

In full attribution mode the SDK stores a first-party identifier in the visitor's browser. In most jurisdictions that requires consent. The SDK has a built-in consent gate so you can honour that decision without removing tracking altogether.

The consent gate

One flag controls everything that touches browser storage. When consent is withheld, the SDK:

• Does not create or read a stored session identifier
• Does not store the landing page or visitor marker
• Treats clakta.identify() as a no-op
• Still records page views and events, using server-estimated sessions

So revoking consent degrades a full-attribution project to privacy-friendly behaviour rather than turning tracking off. You keep traffic and same-day attribution; you lose cross-session identity.

Set the initial value

Pass consent to init() with whatever your banner already decided:

clakta.init({
  id: "YOUR_SCRIPT_ID",
  consent: false,
})

It defaults to true. If your audience requires opt-in, set it to false explicitly and grant it later — do not rely on the default.

Update it at runtime

Call this from your banner's accept and reject handlers:

clakta.consent.update(true)   // granted
clakta.consent.update(false)  // revoked

Revoking immediately clears every stored identifier — the session key, the landing page and the visitor marker, in both localStorage and sessionStorage (older SDK versions used the latter). Subsequent events fall back to server-estimated sessions.

Read the current state at any time:

if (clakta.consent.get()) {
  // identifiers are in use
}

A complete opt-in flow

import clakta from "@clakta/javascript"

const stored = localStorage.getItem("cookie-consent")

clakta.init({
  id: "YOUR_SCRIPT_ID",
  consent: stored === "granted",
})

function onAccept() {
  localStorage.setItem("cookie-consent", "granted")
  clakta.consent.update(true)
}

function onReject() {
  localStorage.setItem("cookie-consent", "rejected")
  clakta.consent.update(false)
}

Note that tracking starts immediately either way — anonymous while consent is withheld, identified once it is granted. You do not lose the visitors who never interact with the banner.

If you must block tracking entirely

Some legal advice requires that nothing at all is sent before consent. In that case drop data-auto-init from the script tag (or do not call init yet) and initialize only after the visitor accepts:

<script src="https://cdn.clakta.com/script.js" defer></script>

function onAccept() {
  clakta.init({ id: "YOUR_SCRIPT_ID", consent: true })
}

Choosing an approach

Both leave the browser untouched until consent is granted. The gate simply keeps measuring in the meantime.

Related

• Tracking modes
• Identify customers
• Data retention