Consent Configuration

Applies to: WordPress Plugin + Admin Portal

WP Admin: Cookie Consent tab > Consent Behavior
Portal: app.hu-manity.co > Configuration (Content, Behavior, Laws, Consent Signals)

Where to configure consent settings

Setting Where to configure
Consent messages (banner copy, button labels, Unblock text, Preferences labels) Portal: app.hu-manity.co → Configuration → Content
Default Consent Level Portal: app.hu-manity.co → Configuration → Behavior
Privacy Policy link, Do Not Sell/Share link Portal: app.hu-manity.co → Configuration → Behavior
Geolocation regional defaults Portal: app.hu-manity.co → Configuration → Laws
Consent duration Portal: app.hu-manity.co → Configuration → Behavior
Consent Modes (Google, Meta, Microsoft) Portal: app.hu-manity.co → Configuration → Consent Signals
Refuse button (optional opt-out button on banner) Unconnected site: WordPress admin → Compliance → Cookie Consent tab → Consent Behavior.
Connected: the Refuse button card on the Cookie Consent tab only displays the value.
Update consent icon (floating widget) Portal: app.hu-manity.co → Configuration → Behavior → Update consent
Unconnected site: WordPress admin → Compliance → Cookie Consent tab → Consent Behavior → Enable Update consent
Consent on Close (Accept on Close) — portalOnly Not available on an unconnected site.
Connected: display-only Accept on close card with a Manage in Admin Portal link. Edit it on Configuration → Behavior.
Consent on Click / Scroll Unconnected (Banner Only): WP admin → Compliance → Cookie Consent tab → Consent Behavior accordion.
Connected: the setting card only displays the value. Edit it on Configuration → Behavior. The card has no toggle and no portal link.
UI Blocking — portalOnly Not available on an unconnected site.
Connected: display-only Cookie wall card with a Manage in Admin Portal link. Edit it on Configuration → Behavior.
GPC Support Mode Professional, or a Free site that already has GPC on: WordPress Cookie Consent tab → Laws, languages & signals → Consent signals, and Configuration → Consent Signals. The GPC support card on the Cookie Consent tab does not edit it. A Free site that does not already have GPC on cannot enable it; the card shows Upgrade to Pro. Turning GPC off on Free removes the ability to turn it back on.
Reloading Unconnected (Banner Only): WP admin → Compliance → Cookie Consent tab → Consent Behavior accordion (Reload page on accept).
Connected: Configuration → Behavior. There is no Reloading card on the Cookie Consent tab.

Where unconnected and connected sites diverge. Unconnected users find the refuse, Update consent, accept-on-scroll, accept-on-click and reload toggles inside the Consent Behavior accordion on the Cookie Consent tab; UI Blocking and Consent on Close are not available there. For connected (Free or Professional) users, the Consent Behavior accordion is hidden and these settings (except reload, which has no card) instead appear as setting cards on the Cookie Consent tab. UI Blocking and Accept on Close are display-only cards with a Manage in Admin Portal link, and are edited on Configuration → Behavior. GPC is edited in the Consent Signals panel (Browser Signals) when the plan allows it, and on Configuration → Consent Signals. Accept on scroll, Accept on click, and Consent expiry are display-only cards with no portal link; edit scroll, click, and expiry on Configuration → Behavior.

Use the consent settings on Configuration → Content, Behavior and Laws to control the first-visit experience, how a choice gets made, and how visitors can change it later. The sections below describe the portal-side controls. On an unconnected WordPress site those toggles are in Cookie Consent tab → Consent Behavior. On a connected site that accordion is hidden.

Define the banner’s headline, explainer, and primary buttons. You can also set the Unblock texts (message + button) for blocked embeds and the Preferences section labels, including names for Private, Balanced, and Personalized levels. Keep English here; add translations on the Languages page.

By law, non-essential storage stays off until a visitor saves a choice. “Private” maps to a “reject non-essential” stance and works as the safest default (preselected on the Classic engine; the New engine preselects nothing). You can switch the default to “Balanced” or “Personalized” if your policy allows it.

How a choice gets recorded (behavior controls)

The following behavior controls are configured on Configuration → Behavior in the portal. (On an unconnected WordPress site, only Accept on scroll, Accept on click and Reload page on accept exist, in WordPress admin → Compliance → Cookie Consent tab → Consent Behavior.)

  • Consent on Close — clicking the banner’s close icon registers the currently selected level. Classic engine only. The New engine ignores this setting; it still applies if you switch back to Classic.
  • Consent on Click — any click on the page registers the current level. Classic engine only. The New engine ignores this setting; it still applies if you switch back to Classic.
  • Consent on Scroll — scrolling beyond the Scroll Offset (0–500 px) registers the current level. Classic engine only. The New engine ignores this setting; it still applies if you switch back to Classic.
  • UI Blocking — lock the interface until the visitor picks a level (a strict, consent-first flow without forcing a particular option). Classic engine only. The New engine ignores this setting; it still applies if you switch back to Classic.
  • Reloading — reload the page after a choice or change when your stack needs it.

On a site using the New engine, the Admin Portal does not show the four Classic-only settings above. Their saved values are kept and apply again if you switch back to Classic.

These align the banner with your regional and policy needs without extra code.

Configured on Configuration → Behavior with Update consent and Update consent method (on an unconnected WordPress site: Cookie Consent tab → Consent Behavior → Enable Update consent and Update consent method):

  • Automatic — turn it on to show a floating widget; visitors can reopen the banner anytime and change their choice.
  • Manual — hide the widget and wire your own control with data-hu-action="cookies-notice-revoke" .

In both cases, the banner applies the new state and (if configured) removes cookies set under the prior state.

Add and label links to your Privacy Policy and, where relevant, Do Not Sell/Share. On the Classic engine, choose targets (same tab/new tab). Turning a link off hides it in every language. Geolocation can show/hide these per region (more below): when Geolocation is on, a region rule that sets its own Privacy Policy or Do Not Sell setting overrides the switch for visitors in that region. On the New engine this also holds while script blocking is off (the plugin’s Script blocking engine setting is off, a WordPress admin is logged in, or a Free site is over its visit limit; on an over-limit Free site only for visitors whose country is already known): the matching region rule still decides, and the switch alone decides only where no rule applies or the rule does not set that link (Privacy Policy or Do Not Sell). Nothing is blocked in those cases; the rule does not block or release any script.

Both link groups contain similar options:

  • Link Label – Text of the link
  • Link URL – Destination URL
  • Link Target – Same window or new window. Classic engine only: the New engine always opens these links in a new tab, and the Admin Portal does not show this choice on a New-engine site.

Geolocation (regional defaults)

Geolocation sets regional defaults before any choice: whether the banner shows, whether Update consent is available, whether Autoblocking starts strict, and which links appear. You can use the built-in rules (Managed) or set one rule per selected law, plus Other Regions, yourself (Manual). Consent Modes (Google/Meta/Microsoft) read the same state.

Global Privacy Control (GPC)

When enabled, Cookie Compliance honors the GPC browser signal as an opt-out boundary before interaction. By default the visitor sees no banner: a Private choice is recorded and a brief notice appears once (Show passive notice). You can choose Silent (no notice) or Show full banner instead; with the full banner the visitor can choose Private, Balanced, or Personalized, but marketing/personalization purposes stay off until the visitor explicitly opts in.

Turn on Consent Modes so platform tags adapt to the current consent state without custom code. Toggle Google Consent Mode in Configuration → Consent Signals (and enable others in their sections). After a choice, the banner updates the modes so tags degrade/upgrade correctly.

On a connected site, Configuration → Behavior stores exactly three durations, chosen from 1 month, 3 months, 6 months, 12 months, and 24 months. The duration sets how long the consent cookie remains valid.

The defaults above are designed around data-privacy regulations. The references below explain why each setting is shaped the way it is. This is background, not legal advice — the recommended defaults reflect best practice cited by privacy-law experts and do not constitute a legal opinion.

  • Accept / Reject / Customize (consent per purpose) — GDPR Recital 32 and Recital 42 expect consent to be requested per purpose, so visitors can accept or reject by category (essential, analytics, advertising). CCPA §1798.135 requires a way to opt out of the sale/sharing of personal information (a “Do Not Sell” link) or to opt in per category.
  • Revoke consent — GDPR Article 7 and Recital 32 require that consent be as easy to withdraw as to give; the banner must let a visitor change their choice at any time. CCPA does not mandate an in-banner withdrawal control.
  • Privacy Policy link — GDPR Article 13 and Article 14 require that an information page such as a privacy policy be accessible when consent is requested.
  • Do Not Sell / Share link — CCPA §1798.135 requires a clear opt-out of sale/sharing for U.S. (especially California) visitors, including for cross-context behavioral advertising.
  • Consent on Close / Click / Scroll, and UI Blocking — GDPR Article 4(11) and Recital 32 require an unambiguous, affirmative action; closing, clicking away, or scrolling is not affirmative consent, and Recital 32 also expects the site to remain accessible rather than gated behind a consent wall. Keep these auto-consent behaviors off under GDPR, UK PECR, LGPD, and POPIA — they are only appropriate in opt-out (e.g. U.S.) jurisdictions. See Consent on Click and Consent on Close for the per-setting guidance.

Still need help? Contact Us Contact Us