Pick OneTrust if consent is one part of a larger privacy programme run by a legal or privacy team. It scans your site for cookies, and separate OneTrust products cover more of that programme.
Pick c15t if your engineers own consent. The banner, the engine that decides what may run and the backend that stores records are all code your team can read, change and ship with the rest of the product. OneTrust has a headless API too, so either one lets you build your own UI. With c15t you can also change the engine and the backend.
<include src="../shared/comparisons/inth-hosting.mdx" />
c15t’s banner appears 602 ms sooner than OneTrust’s on desktop.
| What you need | c15t | OneTrust |
|---|---|---|
| Build application consent UI | Native components, themes and headless APIs | Web CMP UI and a headless Server-Side CMP API |
| Resolve consent on the server | Framework helpers and cached public policy | Server-Side CMP API |
| Read or change consent in code | Reactive framework state and actions | JavaScript methods and consent-change callbacks |
| Control vendor execution | Declared integrations, request rules and embeds | Automatic blocking, tag-manager integrations and script controls |
| Own the backend implementation | Apache-2.0 backend that you can deploy | OneTrust platform and APIs |
| Store consent records | Inth hosts the backend and stores records in its database. Self-hosting is optional | Consent transaction database |
| Scan authenticated or hidden pages | Not included in the c15t packages | Documented website scans |
| Compare banner layouts | Presentation experiments with your feature flags | A/B tests and template targeting |
| Run a wider privacy programme | No complete privacy operations suite in c15t | Separate OneTrust products extend the consent scope |
Sources: Cookie Consent, JavaScript methods and Server-Side CMP API.
c15t is Apache-2.0. Your developers can read it, patch it and pin versions like any other dependency. Consent changes can go through the same code review as the features that depend on them.
The banner and your app share one consent state. A privacy settings screen in your account area can read the same permissions that gate a video embed or your analytics. If the stock components don't fit, build your own on the headless APIs.
Switch a category off. Its vendors wait.
44 of 44 running
Always loads and gets consent signals.
- Cloudflare Zaraz, always loads and gets consent signals
- Google Tag Manager, always loads and gets consent signals
- Sentry, always loads and gets consent signals
- Google Tag, always loads and gets consent signals
- Databuddy, always loads and gets consent signals
- Mixpanel, always loads and gets consent signals
- PostHog, always loads and gets consent signals
- Microsoft UET, always loads and gets consent signals
- Ahrefs Analytics
- Adobe Analytics
- Amplitude
- Cloudflare Web Analytics
- Microsoft Clarity
- Fathom Analytics
- Heap
- Matomo Analytics
- OneDollarStats
- Hotjar
- Hightouch
- LogRocket
- Plausible Analytics
- Promptwatch
- Pirsch
- RudderStack
- Segment
- Rybbit Analytics
- Umami Analytics
- Vercel Analytics
- Vercel Speed Insights
- Klaviyo
- Clearbit
- Meta Pixel
- OpenAI Pixel
- Pinterest Tag
- Reddit Pixel
- TikTok Pixel
- LinkedIn Insight Tag
- Snapchat Pixel
- X Pixel
- YouTube
- Crisp
- Front Chat
- Intercom
- Google Maps
Import each helper from @c15t/integrations.
Paste this line into your agent. It reads the setup brief and does each step.
The setup brief is at /SKILL.md. For the docs, agents can read /llms.txt and /llms-full.txt, or use the MCP server at with no sign-in.
The CLI plans the setup. You check the plan, then apply it.
To do each step yourself, read the quickstart for your framework. To get JSON results for scripts and agents, read the automation guide.
Inth hosts the backend, the policy rules and the IAB CMP ID.