c15t is the stronger fit when your developers need native web components and control of the consent backend. You can build privacy choices into the product and review their behaviour in code.
Sourcepoint suits publishers and teams with consent campaigns across websites, apps and connected TVs. It has developer APIs as well as managed operations.
Sourcepoint is part of Didomi after the announced acquisition. This guide covers Sourcepoint's product and docs. See the separate Didomi comparison for that product.
<include src="../shared/comparisons/inth-hosting.mdx" />
| What you need | c15t | Sourcepoint |
|---|---|---|
| Connect consent to a web product | Native framework components and reactive state | Web integration, SDKs and consent callbacks |
| Build the interface | Themes, component parts and headless APIs | Message builder, custom CSS and campaign flows |
| Control vendors | Declared category and vendor rules | Vendor lists, consent actions and third-party tag controls |
| Store consent history | Inth hosts the backend and stores records in its database. Self-hosting is optional | Managed history by vendor and legal basis |
| Discover vendor activity | No automatic scanner in the packages | Scans and separate compliance monitoring tools |
| Test consent designs | Presentation and theme experiments with fixed policy and policy text | Campaign reports and A/B tests |
| Cover connected TVs | No bundled connected-TV SDK | OTT and CTV support |
| Manage publisher campaigns | Build product flows in application code | Property groups and reusable campaign scenarios |
Sources: Sourcepoint CMP, third-party tag controls and consent callbacks.
c15t's framework adapters let your team connect product screens to shared consent state. Use headless APIs for your own markup and vendor controls for individual services.
Sourcepoint also supports custom code and callbacks when consent becomes available or a visitor takes an action. Its developer tools deserve credit in the comparison.
c15t's advantage is the combination of native web components and source code for both the engine and backend. Your team can change and deploy those parts together.
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.