Communicate
PlannedSome visitors have already answered.
A visitor's browser can carry an opt-out signal. DotCensus detects it and passes it to the policy engine, which decides what it means under the policy you configured for that region — rather than the runtime assuming one universal legal effect.
Global Privacy Control
- Signal detection
- Policy-decided effect
- Recorded in receipts
- Reported in analytics
How it helps
What you get with Global Privacy Control
Detection is not interpretation
The runtime reports the signal; the configured policy decides its effect. Those are different jobs and conflating them produces wrong behaviour in some regions.
Recorded in the receipt
A decision influenced by a browser signal records that, so the evidence explains itself later.
Visible to you
How often the signal arrives is reportable, because it changes what your consent rates mean.
Signals & Advertising
The rest of Signals & Advertising
Translate one visitor choice into the signals connected platforms understand.
Google Consent Mode
Map categories to Google's documented consent types, in basic or advanced deployment.
Learn moreGoogle Tag Manager
Consent initialization, triggers and diagnostics for GTM-managed tags.
Learn moreIAB TCF
Built as a versioned adapter targeting the current v2.4 web model.
Learn moreGlobal Privacy Protocol
Encode and expose GPP strings for the jurisdictions you configure.
Learn moreMicrosoft UET
Adapter for Microsoft UET consent handling.
Learn moreKnow what runs before you ask visitors to trust it.
Start with a scan of what your website loads today. The list is usually longer than the team expects, and that is the useful part.
No code to install for a scan Public pages only DotCensus runs on DotCensus