Resolution order
At every event the SDK resolves consent in this order; the first rule that applies wins and its name is sent as consentSource, so your consent log in the console says *why* a session was or was not identified.
| Order | Rule | `consentSource` |
|---|---|---|
| 1 | navigator.globalPrivacyControl === true → **always false**, even if your code says true | gpc |
| 2 | reveal.setConsent(bool) was called by your code | override |
| 3 | The consent option (true/false, or a function read at every event) | config |
| 4 | A consent manager detected on the page (table below) | cookieyes cookiebot onetrust klaro tcf gcm |
| 5 | Nothing configured, no CMP: false on EU/EEA/UK/CH-looking pages (timezone or <html lang>), true elsewhere | default |
The regional default is a safety net, not a legal determination. Sites in scope of the GDPR or ePrivacy should run a consent manager (detected automatically) or pass consent explicitly.
Consent managers detected automatically
Detection is read-only (the SDK never writes to your CMP) and re-evaluated every second and on the CMP's own events, so a visitor who accepts after the page loaded is picked up within a second: the identify() and track() events held meanwhile are released, the next pageviews carry the full URL and referrer. A later withdrawal is honoured the same way.
| CMP | What is read | Counts as consent when |
|---|---|---|
| CookieYes | getCkyConsent() or the cookieyes-consent cookie | category analytics is accepted (action:yes + analytics:yes) |
| Cookiebot | Cookiebot.consent | statistics is true (after hasResponse) |
| OneTrust | OnetrustActiveGroups | contains C0002 (Performance/Analytics) |
| Klaro | klaro.getManager().consents | a service named prynt is accepted, else the first service named like *analytics*/*statistics* |
| IAB TCF 2.2 | __tcfapi('addEventListener', 2, …) | purposes **1** (store/access information) **and 7** (measure performance) are consented, on tcloaded / useractioncomplete; gdprApplies:false counts as consent |
| Google Consent Mode | dataLayer entries consent default/update | the latest analytics_storage is granted (works with GTM and with gtag directly) |
Before the visitor decides (banner still open) the CMP counts as *no consent*. A different category or CMP? Pass consent: () => … and the function wins over detection.
const client = PryntReveal.reveal({
publicKey: 'pk_live_YOUR_PUBLIC_KEY',
// 1. nothing: GPC → CMP auto-detect → EU/UK/CH heuristic
// 2. a boolean you already know:
consent: true,
// 3. a function read at every event (any CMP):
consent: () => window.myCmp.isAllowed('analytics'),
});
// 4. later, from your banner's callback:
client.setConsent(true); // releases the identify()/track() events held meanwhile Global Privacy Control
When the browser sends GPC (Firefox, Brave, DuckDuckGo, Chrome with the setting or an extension), Reveal treats the visit as *no consent* no matter what the page, the CMP or your code say. diagnose().gpc reports it and the batch says consentSource: "gpc". This is not configurable, on purpose.
What is sent without consent
pageviewevents with origin + path and the page title — no query string, referrer, UTM, click ids, ESP tokens, visitor id or identity.- No
engagementevents;identify()/track()are held in memory (the last 60) and sent if consent arrives later on the same page. - Form submissions are ignored, unless you set
forms: { requireConsent: false }— then the submission itself is the first-party consent, theformevent is sent on its own with the form id asconsentRef, and nothing else is unlocked. Only use it when the form says so.
Company identification still works on the minimal pageview (it is based on the network, not on the person); the console's consent settings (Settings → Consent) decide whether identity-level data is accepted at all for each website.
Server-side consent controls
- Every change of consent state is recorded with its source per session, so you can show a DPO *when* and *through what* a visitor consented.
- Country rules and URL rules on each website let you force explicit consent for some countries and exclude paths (login areas, customer portals) from collection entirely.
- Visitors can opt out platform-wide at /legal/reveal-opt-out; the suppression applies immediately on every site that uses Prynt.
Last updated 2026-11-03 · Limits · Visitor opt-out