Documentation
The model, before the menus.
Most of what is confusing about consent tooling is conceptual rather than procedural. These six ideas are what everything else is built from.
Consent Core
One engine behind every integration path. The banner, the runtime, the API and a native builder integration all read and write the same state, which is why they cannot disagree about what a visitor chose.
Categories and purposes
Categories are how choices are grouped for display; purposes are what the data is actually used for. Keeping them distinct is what lets one visible toggle map correctly to several downstream signals.
The Consent Manifest
The machine-readable map from service to vendor, purpose, execution rule, storage and signals. Generated from a scan plus your review, or compiled by a website builder from its components.
Policy packs
A versioned object holding the consent mode, default states, required controls, signal handling, renewal and disclosure rules for a region. Published policies are immutable.
Receipts and versions
A decision records the banner, policy and manifest versions in force at the time, so it stays interpretable after the site changes. Withdrawal appends a new event rather than editing the old one.
Fail-safe behaviour
Under an opt-in configuration, a runtime that cannot reach its configuration must not release restricted services. The failure path is specified and tested rather than incidental.
By module
Each module, and what it is responsible for.
The platform pages carry the detail. This is the one-line version of who owns which part of the model.
- Scan & Tracker IntelligenceSee the cookies, trackers, storage and services actually running on your site.
- Consent ExperienceBranded, accessible consent and preference experiences that belong on your site.
- Control & BlockingHold, gate or release services according to the visitor's actual choice.
- Signals & AdvertisingTranslate one visitor choice into the signals connected platforms understand.
- Consent LedgerVersioned evidence of what was shown, what was chosen and what was enforced.
- Policies & JurisdictionsServe different consent models and disclosures from one versioned policy engine.
- Privacy HealthContinuously test whether the site's real behaviour still matches its configuration.
- Developer & PlatformSDK, API, webhooks, CMS integrations and native website-builder support.
Step-by-step setup and administration documentation ships with the product console. This page covers the concepts a reader needs before any of those procedures make sense.
Know 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