Intentional consent puts clarity and control in the visitor’s hands. The idea is simple: people should understand what runs and why, choose deliberately, and change that choice later without friction. Cookie Compliance builds the banner, wording, and logging around that principle.
The idea behind Intentional Consent
- Accountable by design. The system records the decision and the enabled purposes so you can demonstrate how and when consent happened.
- Clarity over tactics. The experience explains purposes in plain language and avoids dark patterns. By default, scrolling and timeouts never count as consent. If you turn on Consent on Scroll or Consent on Click, scrolling down the page or clicking outside the banner saves the pre-selected level. This applies to the Classic engine; the New engine preselects nothing.
- Parity of choices. The banner shows the levels (Private, Personalized, and Balanced when you offer three choices) side by side as equal choices, saved with one button; Private is the decline-all choice. Visitors can also open details before acting.
- Purpose-bound use. Consent enables only the purposes a visitor selects—nothing extra.
- Reversible and respectful. The Update consent control stays available. People can revisit or withdraw their choice at any time.
How Cookie Compliance expresses consent
Cookie Compliance uses two layers that visitors and teams can understand:
- Access Levels — human-friendly presets: Private, Balanced, Personalized.
- Purpose Categories — the “why” behind processing: Basic Operations, Site Optimization, Content Personalization, Ad Personalization.
Each Access Level turns on a fixed set of purposes (see Consent Message Guide); you decide which purpose each provider belongs to.
Consent choices: 2 or 3 options
You choose whether the banner presents two or three choices:
- Two choices:
- Private or Reject (only Basic Operations)
- Personalized or Accept (all purposes)
- Three choices:
- Private or Reject (Basic Operations only)
- Balanced or Accept Some (Basic Operations, Content Personalization and Site Optimization)
- Personalized or Accept All (all purposes)
Choose the model that best fits your policy and audience. The wording and layout keep both paths equally visible.
Default consent level (before any action)
Before a visitor acts, the banner uses a default consent level defined in the application. It is one setting for the whole site; Geolocation does not change it. The default does not imply acceptance—it only sets the starting posture the page follows until the visitor chooses (preselected on the Classic engine; the New engine preselects nothing).
Examples:
- Strict policy → default = Private (only Basic Operations)
- Lighter policy → default = Balanced or Personalized
Consent duration
Cookie Compliance uses a single Duration parameter to control how long consent remains valid and when the banner asks again after it expires. You can offer a Consent duration selector to let visitors choose (e.g., 1–6 months), or hide it and rely on your preset.
Duration should match your legal basis and policy. Visitors can revoke or change their choice earlier via the Update consent control.
Before consent: prior protection
- Non-essential scripts are held. Scripts and iframes that match providers in your catalog stay held until the visitor chooses (in regions whose rule requires consent first); a held script file may download, but it does not run. To keep blocking complete, gate tags you fire through Google Tag Manager with consent triggers (on the New banner engine, recognised tags GTM fires are also held automatically), and add a URL pattern for any tracker the built-in list does not recognise. The Free plan covers 1,000 visits per 30-day cycle (see Pricing); past that, blocking pauses until the next cycle or until you upgrade. Your cookie policy describes the cookies your site uses.
- GPC (if enabled). When a browser sends Global Privacy Control, Cookie Compliance starts in a protected state and holds every non-essential purpose off (only Basic Operations run) until the visitor explicitly opts in. (In Show full banner mode, if Consent on Scroll, Click or Close is on, scrolling, clicking or closing the banner saves the preselected Default Consent Level as that choice. This applies to the Classic engine; the New engine preselects nothing.)
- Geolocation rules. Per region (e.g., EU, UK, US, CA, BR, Other) you choose whether the banner shows, whether the Update consent control shows, whether autoblocking applies, and which privacy links appear. The default consent level stays the same everywhere.
After consent: immediate, consistent behavior
- The banner updates the running state right away; no page reload required.
- Consent Modes—Google, Meta (Facebook), and Microsoft—read the same state. Tags degrade gracefully before consent and expand only after the visitor accepts the relevant purposes.
- An Update consent or change is saved at once. Scripts that already ran keep running until the next page load; from then on, only the allowed providers run. Turn on Reloading to reload the page as soon as the new choice is saved.