# Inth vs CookieConsent v3 CookieConsent v3 is a lightweight vanilla JavaScript plugin that keeps consent in the browser. Inth Consent runs it inside your application through c15t, with the records hosted for you. Which one fits depends on what your team wants to own. **Ask your coding agent** ```text Audit this codebase for CookieConsent v3 and estimate a move to Inth Consent, built on c15t. Find the CookieConsent v3 setup and any Consent Mode and tag manager wiring, list every analytics, advertising and chat tag, then report what c15t would replace, which consent category each tag needs, and what the page would stop loading before consent. Use https://c15t.com/docs/comparisons/cookieconsent-v3 and https://c15t.com/docs/integrations/overview. ``` [Talk to Inth](https://booking.inth.com/talk-with-inth) **Your privacy choices** Choose how this site uses cookies. You can accept, reject, or customise optional analytics and marketing. **Privacy settings** Choose which cookies and tracking technologies this site may use. - Strictly necessary: always on - Analytics: off - Marketing: off Expo · Zed · Infisical · Unkey · Chelsea Piers · Mario Testino · Roboto Studio · Cal.com · Mastra ## Which platform fits your team? Tick the needs that matter to your team and see which platform meets more of them. | Your needs | Inth Consent | CookieConsent v3 | | --- | --- | --- | | Consent state in your React and Next.js code | ✓ c15t packages expose consent state to your components and your server | – Vanilla JavaScript plugin; React and Next.js need your own wrappers | | Hosted consent records | ✓ Every saved choice, region and policy version in your Inth dashboard | – Up to your app if you need them | | Script, iframe and network blocking | ✓ Script loader, iframe blocker and network blocker tied to consent categories | – Callback-based loading and cookie cleanup | | Google Consent Mode v2 | ✓ Denied defaults and consent updates through the Google integrations | ✓ Consent Mode support documented | | Works without a backend | ✓ Offline mode runs in the browser; hosted records when you want them | ✓ Runs entirely in the browser | | Consent state in server rendering | ✓ Available through the c15t framework packages | – Client-side by default | | Free and open source | ✓ c15t is open source and Inth Consent has a free plan | ✓ Free, open-source plugin | Inth Consent: 7 of 7 needs. CookieConsent v3: 3 of 7 needs. [Talk to Inth](https://booking.inth.com/talk-with-inth) · [See pricing](/pricing#pricing) ## Keep every tag you already run. Inth Consent runs on c15t, which ships helpers for the analytics, advertising, chat and tag-manager tools you use today. Each one loads only when its consent category is granted, so consent is enforced in your implementation rather than by a script bolted on top. Your privacy choices Choose which optional cookies this example site can use. Necessary (Always on) · Functional · Analytics · Marketing Reject all · Accept all **Tag managers**: Google Tag Manager **Analytics**: Google Analytics 4 · Ahrefs · Adobe Analytics · Amplitude · Cloudflare · Microsoft Clarity · Databuddy · Rybbit · Fathom · Heap · Mixpanel · Hotjar · Hightouch · LogRocket · Matomo · PostHog · Promptwatch · Pirsch · RudderStack · Segment · Plausible · Umami · Vercel Analytics **Functional**: Crisp · Intercom · Google Maps · YouTube **Ads & pixels**: Google Ads · Meta Pixel · TikTok Pixel · LinkedIn Insight Tag · Snapchat Pixel · Reddit Pixel · X Pixel · Microsoft UET · Clearbit [Talk to Inth](https://booking.inth.com/talk-with-inth) [See all integrations](https://c15t.com/docs/integrations/overview) ## Consent belongs in your implementation plan Setup Storefront · storefront.example.test Connect Consent to your application Point c15t at this project, map your services to consent categories, then watch for the first consent to arrive. 4 of 4 complete Get the Consent runtime URL: Use this project’s hosted runtime URL when you configure c15t. Map services to consent categories: Decide which category each analytics, advertising and chat tag needs before it loads. Install c15t in your app: Install the package for JavaScript, React or Next.js and connect it to this project. Receive your first consent: Completes automatically when consent activity arrives from your application. You wire consent into the app once. After that it ships with your releases. Install c15t, tell it which [category each tag belongs to](https://c15t.com/docs/integrations/overview), and point it at your hosted project. That is the setup. With CookieConsent v3 the banner and its logic live in the browser, which is fine until your server or app code needs to know whether marketing consent was given. Either way, test it: accept, reject, change your mind, and check what actually loads. Inth Consent ## See consent in your dashboard. Consent overview Storefront · storefront.example.test 31 Aug – 6 Sept Consent activity All regions and devices · Last 7 days Prompt activity What happened after the prompt appeared. After the prompt Accept all Custom choice Reject / opt out No saved response Every saved choice, region and policy version in one place, so you can answer a regulator or a customer without exporting anything. [Talk to Inth](https://booking.inth.com/talk-with-inth) · [See pricing](/pricing#pricing) ## How Inth Consent and CookieConsent v3 compare Two ways to run website consent: application-owned packages, or a client-side JavaScript plugin. | Requirement | Inth Consent | CookieConsent v3 | | --- | --- | --- | | Primary shape | Application consent platform | Client-side JavaScript plugin | | Growth path | Banner, backend, policy packs, IAB TCF and app state | Banner and preference UI first | | Benchmark snapshot | Score 95; 89 ms in the c15t Next.js example | Not tested on CookieBench | [Talk to Inth](https://booking.inth.com/talk-with-inth) · [See pricing](/pricing) ## Compare the total consent cost Drag the slider to your monthly sessions. Inth Consent picks the cheapest published plan and adds usage at the published rate. CookieConsent v3 is free; hosting, records and upkeep are yours to run. | Plan | Monthly | Included requests | | --- | --- | --- | | Free | $0 | 5000 | | Starter | $20 | 25000 | | Pro | $50 | 100000 | Monthly sessions: 60000. Inth Consent: $50 / mo on Pro ($0.001 per request beyond included usage). CookieConsent v3: Free, open source. [See pricing](/pricing#pricing) · [Talk to Inth](https://booking.inth.com/talk-with-inth) ## Moving from CookieConsent v3? Bring your current setup and the tags you load. We’ll map the switch with you. If you want a head start, have your coding agent draft the plan. **Plan it with your coding agent** ```text Plan a migration from CookieConsent v3 to Inth Consent, built on c15t, for this codebase. Find the CookieConsent v3 setup and Consent Mode wiring, map every tag to a c15t integration and consent category, propose how to run c15t on a staging route while CookieConsent v3 stays live, and list what to verify before cutting over. Use https://c15t.com/docs/comparisons/cookieconsent-v3 and https://c15t.com/docs/integrations/overview. ``` [Talk to Inth](https://booking.inth.com/talk-with-inth) Consent overview Storefront · storefront.example.test 31 Aug – 6 Sept Consent activity All regions and devices · Last 7 days Prompt activity What happened after the prompt appeared. After the prompt Accept all Custom choice Reject / opt out No saved response ### Can we keep Google Ads, Analytics and Tag Manager? Both approaches support consent-aware Google integrations. Review category mappings, denied defaults and updates, then verify actual tag behaviour after each visitor choice. ### Can we migrate existing choices and records? Check the actual formats, identifiers, retention requirements and interpretation of each saved choice. Plan that work explicitly rather than assuming one platform can import another platform’s records. ### Where should we start? Define the consent layer you need to replace, map your integrations and compare the full cost and ownership model. Then test both implementations against the same visitor journeys.