Build on it
PlannedOne core, several front doors.
CMS integrations install the runtime early, connect the site token and surface health in the admin — without forking the product logic per platform, which is how integrations drift apart.
CMS Integrations
- Site token connection
- Early runtime insertion
- Admin health surface
- Shared core API
How it helps
What you get with CMS Integrations
Same core, thin adapters
A platform integration handles installation and admin surface, not a second copy of the consent engine.
Early insertion
The runtime has to load before the tags it governs, which is most of what a platform integration is for.
Status where the admin looks
Health and scan results visible inside the CMS, rather than only in a dashboard nobody has open.
Developer & Platform
The rest of Developer & Platform
SDK, API, webhooks, CMS integrations and native website-builder support.
JavaScript SDK
Read the state, subscribe to changes, open preferences and gate your own code.
Learn moreREST API
Versioned endpoints for sites, scans, trackers, manifests, policies and integrations.
Learn moreWebhooks
Signed events for scans, discovered trackers, published policies and failing health checks.
Learn moreWebsite Builders
Components declare their privacy impact; the Consent Manifest is generated at build time.
Learn moreAgency Management
Client organizations, reusable policies, roles, fleet reporting and site handover.
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