Save Consent

Save Consent

What it is

Adds a primary action button to the banner that confirms the visitor’s current choices (Access Level, Purposes, and Consent Duration). Classic engine only: the New engine has no Save button; each choice saves on click.

Where to configure these settings

What happens when clicked

• Cookie Compliance records consent (banner → app, when plan/limits allow) and stores a consent cookie in the visitor’s browser.

  From that moment until the selected duration expires, the banner and autoblocking engine apply the visitor’s choices:

  • Access Level (Private, Balanced, or Personalized) controls which categories can run.
  • Purposes you expose in the UI are respected.
  • Consent Signals (Google, Microsoft, Facebook) receive updated signals.
  • Autoblocking allows or continues to block scripts/iframes/links according to the chosen level/purposes.

Customize it

• Button label (default): “Save my preferences”. This text is Classic engine only; the New engine has no Save button, so the Admin Portal does not show this field on a New-engine site.
• Consent Duration choices: configure in the app to show one or more of the available options (see duration list below).
• Languages: label and helper text follow your language settings.

Consent Duration options

When configuring the banner’s Duration dropdown, the following options are available:

• An hour
• 1 day
• 1 week
• 1 month
• 3 months
• 6 months
• 1 year
• Infinity (the banner never re-prompts the visitor)

Both the accepted-consent duration and the rejected-consent duration use this same set of options. That list is only the unconnected WordPress pair. A connected site edits Consent expiry on Configuration → Behavior: exactly three values, chosen from 1 month, 3 months, 6 months, 12 months, and 24 months.

WordPress Admin: Cookie Expiry Settings

For unconnected (Banner Only) users, the WordPress admin Cookie Consent tab > Cookie Expiry section shows two dropdowns — one for accepted-consent duration and one for rejected-consent duration — using the same 8 options listed above.

The Cookie Expiry accordion is shown only to unconnected (Banner Only) users. For connected users (Free or Professional plan), the Cookie Expiry accordion is hidden in the WP admin. Consent duration is edited in the portal at Configuration → Behavior. On a connected WordPress site the Cookie Expiry accordion is hidden. When GDPR or UK PECR is selected, the Cookie Consent tab can show a Consent expiry card. That card displays the three stored durations. It has no editor and no link to the portal.

Default Consent Level

What it is

On the Classic engine, sets the preselected Access Level shown on first load — before the visitor interacts. It determines the banner’s initial toggles. On the New engine nothing is preselected: the level only sets which Google Consent Mode categories start as granted before a visitor answers in opt-out regions, with Geolocation and Google Consent Mode on and not for a visitor who sends GPC or Do Not Track (ad signals stay withheld at every level). It does not loosen autoblocking: with Autoblocking on, in a region whose rules block before consent, every non-essential category stays blocked until the visitor makes a choice, whatever the default level. Two limits apply: a script that an already-allowed script adds later (for example a tag fired by GTM while Google Consent Mode lets GTM run) is not held, and on the Free plan blocking stops once the site passes its visit limit for the current cycle.

Cookie Compliance uses a three-level Access Level model:

• Private — non-essential categories OFF. Only basic operations run. This is the safest default under GDPR/ePrivacy-style rules.
• Balanced — Content Personalization and Site Optimization on. Ad Personalization remains off.
• Personalized — all non-essential purposes enabled, including marketing and personalization. Visitors grant the highest level of data sharing.

Compliance-first default

• By design, all non-essential technologies remain blocked until the visitor gives consent.
• The only fully compliant preselection under GDPR/ePrivacy-style rules is Private — non-essential categories OFF by default.

Business-flex option (use with caution)

• On the Classic engine, you can set Balanced as the default so Content Personalization and Site Optimization start pre-selected in the banner.
• This can improve short-term analytics continuity but may not meet strict consent-by-default expectations in many jurisdictions.

How autoblocking reacts

• Private default → non-essential tags remain blocked until the visitor consents.
• Balanced default → with Autoblocking on, in a region whose rules block before consent, nothing non-essential runs before a choice (subject to the two limits above). If the visitor saves without changing the selection (or closes the banner with Consent on Close on, or scrolls/clicks with those options on), Content Personalization and Site Optimization are allowed. This is why risk increases.
• Personalized default → under the same conditions, nothing non-essential runs before a choice either (subject to the two limits above), but saving the pre-selection (or the same close, scroll or click options) allows all non-essential scripts. Use only if your legal basis permits opt-out consent.