c15t is the stronger fit when your team wants native consent components across web frameworks and control of the backend. You can change the interface and engine with the product that uses them.
CookieFirst combines hosted consent, scans and cookie-policy tools. Its React package and public API also support custom application flows.
<include src="../shared/comparisons/inth-hosting.mdx" />
| What you need | c15t | CookieFirst |
|---|---|---|
| Use native web integration | React, Next.js, Vue, Nuxt, Svelte, SvelteKit, Astro and TanStack Start | Official React component, browser script and platform integrations |
| Build a custom interface | Themes, component parts and headless APIs | Public consent API and a stealth mode without the supplied banner |
| Let visitors choose services | Category and individual vendor state | Category or service consent, under the configured policy |
| Control vendor code | Declared rules for scripts, requests and embeds | Third-party script settings and Autoblock |
| Choose the record service | Inth hosts the backend and stores records in its database. Self-hosting is optional | Hosted consent logs and plan-dependent audit trails |
| Discover cookies | No automatic scanner in the packages | Cookie scans |
| Generate a cookie policy | Not included | Cookie-policy generator |
| Handle withdrawal | Page reload by default, with optional cleanup | API clears consent, records the change and reloads the page |
Sources: CookieFirst platform, React setup and public API.
CookieFirst supports more than a standard banner. Its API exposes accepted categories and services. Stealth mode renders no consent interface. Its docs mark only the preference-centre methods as unavailable in that mode, so test whether its consent methods cover the custom controls you need.
Its service methods follow the selected policy. Under a category policy, a service action applies to the relevant category. Check that setting before you compare individual choices.
c15t combines native framework components, vendor state and a backend you can deploy. Your team can change the system from the interface through to record storage.
That combination is the reason to choose c15t when consent is part of the product's code and release process.
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.