c15t is the stronger fit when your developers need native web components and control of the consent engine and backend. You can review consent behaviour with the application features that depend on it.
consentmanager suits teams that need central operations across websites, apps and connected TVs. Its product also includes scans, experiments and customisation options.
<include src="../shared/comparisons/inth-hosting.mdx" />
| What you need | c15t | consentmanager |
|---|---|---|
| Integrate with a web application | Native framework components and reactive state | Website code, CMS plugins and developer APIs |
| Build a custom interface | Themes, component parts and headless APIs | Custom HTML and CSS on listed plans. CTV API supports custom interfaces |
| Choose the backend | Inth hosts the backend and stores records in its database. Self-hosting is optional | Managed platform with plan-dependent own-domain delivery |
| Control vendors | Declared category and vendor rules | Vendor and purpose settings, plus automatic script controls |
| Discover cookies | No automatic scanner in the packages | Cookie crawler and classification |
| Test banner designs | Presentation and theme experiments with fixed policy and policy text | Plan-dependent A/B tests and automatic design selection |
| Cover connected TVs | No bundled connected-TV SDK | HbbTV and CTV SDKs on listed plans |
| Manage teams and reports | Build around your chosen backend | Plan-dependent user roles, reports and exports |
Sources: consentmanager feature comparison and CTV API guide.
With c15t, privacy controls can live inside an account screen or feature. Use the framework components or create the markup with headless APIs.
Declare vendor choices with the integrations they control. Your team can check the code path from a visitor's action to the saved choice.
consentmanager also supports custom interfaces and developer APIs. c15t's advantage is the combined native web workflow and source code for the engine and backend.
An own-domain delivery option does not establish that you can deploy the entire record backend yourself. Check the exact hosting scope when you compare proposals.
Switch a category off. Its vendors wait.
42 of 42 running
Always loads and gets consent signals.
- Cloudflare Zaraz, always loads and gets consent signals
- Google Tag Manager, 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
- 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. To get JSON results for scripts and agents, read the automation guide.
Inth hosts the backend, the policy rules and the IAB CMP ID.