Consent Mode — Loading Personyze Under a Consent Manager

Personyze must not touch a visitor’s device before they consent. There are two ways to guarantee that, and you want one of them — set it under Tracker settings → Consent & privacy in the panel. Under both, nothing is stored and no request is sent before consent.

Choosing how Personyze waits for consent — Two ways to wait for consent — your consent manager blocks the snippet, or the snippet loads and holds itself until you say the visitor agreed. Click to enlarge.

The two modes

Hold the snippet (default, recommended) — your consent manager blocks the Personyze script exactly as it blocks your other tags, until the visitor accepts. Nothing to configure in Personyze; you just tag the snippet (below).
Load, then wait (consent mode) — the script loads but does nothing until you call grant(). Personalization then appears the instant the visitor accepts, with no download to wait for. Choose this when you’d rather have Personyze already loaded than block it.

What “does nothing” means, precisely. Before consent resolves: no cookie read, no cookie written, no storage access, no network request. The hold sits above the opt-out check — because reading a cookie to decide whether to run is itself access to the visitor’s device.

Default mode — tag the snippet for your consent manager

Cookiebot, OneTrust, Usercentrics and similar tools already hold every third-party script until the visitor consents. Tag the Personyze snippet with the category your policy puts it under — usually statistics — and the consent manager won’t run it until then. No Personyze cookie is set and no data is collected while it’s held. The panel’s Consent & privacy drawer has copy-ready snippets for Cookiebot, OneTrust, Usercentrics, and Google Tag Manager.

Consent mode — “Load, then wait”

The Consent handling drawer with Load, then wait selected — Load, then wait: the snippet loads inert; you grant consent from your consent manager’s callback. The drawer ships copy-ready adapters. Click to enlarge.

Turning it on is two steps — and skipping the second takes your site dark:

Tracker settings → Consent & privacy → pick Load, then wait. This is an account setting.
Re-copy the tracking code from Get tracking code and deploy it. The snippet now carries an extra argument to setup() that puts the library in consent mode.

Step 2 is not optional. The server refuses hits that didn’t come from a released consent hold, so between step 1 and step 2 the account is not tracked and not personalized. The panel warns you before saving. Re-deploy the snippet as part of the same change.

Wire your consent manager

From your consent manager’s callback, call one of:

_S_T.consent.grant();   // consent covers personalization — run normally
_S_T.consent.deny();    // it does not — stay off

Call it again whenever the visitor changes their mind; calling grant() twice is harmless. The Consent & privacy drawer ships copy-ready adapters for IAB TCF v2.2 (__tcfapi) and Google Consent Mode v2 — take those rather than retyping them.

There’s deliberately no single “is there consent?” helper. Which purposes count as permission to personalize is your reading of your own policy — a default buried in the library would be Personyze deciding it for you.

If the consent manager never answers

If neither grant() nor deny() is ever called — a consent manager that fails to load — Personyze gives up after a timeout (3 seconds by default) and stays off. It’s a safety net for a broken CMP, not a delay: a returning visitor’s consent manager answers from its own storage within a frame or two.

If a visitor withdraws consent

From your consent manager’s revoke callback, call the opt-out API — it stops tracking and rolls back personalization already rendered on the page:

personyze.system.off();   // stop & roll back
personyze.system.on();    // re-enable
personyze.system.is_on();  // current state

Two things to know

The page renders unpersonalized while waiting for consent. Personyze won’t hide it — hiding the page would hide the consent banner the visitor has to answer. So the hide-on-load snippet variant is unavailable under consent mode, and the panel stops offering it.
Consent mode is not a substitute for a consent manager. It’s how Personyze waits for one.

Personyze client-side cookies — what’s stored, including the stat_track_off opt-out cookie.
GDPR compliance & opt-out — the off() / on() / is_on() API.
Set the mode in the panel under Tracker settings → Consent & privacy.