Any consent framework,
enforced server-side.
Not every organization uses OneTrust or Consentmo. Some run homegrown consent management. Others use regional CMPs, open-source frameworks, or niche solutions tailored to specific privacy regulations. The consent signal exists — it just needs somewhere to go.
Ingest Labs' flexible consent API accepts consent state from any CMP — via SDK, cookie, or server-side API. Map your consent categories to tag destinations, and every event is gated by the visitor's actual choice. Full server-side enforcement, regardless of how consent is collected.
Why Custom Consent + Ingest Labs
Privacy regulations are global but consent implementations are local. A Brazilian e-commerce company might use a LGPD-specific CMP. A European publisher might run a TCF-compliant framework built in-house. A healthcare platform might have a consent layer baked into their patient portal. None of these fit neatly into a pre-built integration — but they all produce a consent signal that needs to be enforced.
Ingest Labs doesn't require you to switch CMPs. Our consent API is protocol-agnostic: send us consent state as a cookie, a JavaScript SDK call, or a server-side API payload, and we'll gate every downstream tag accordingly. You define the categories, you define the mapping, and we enforce it.
The result is a consent architecture that works with your existing stack — not against it. Your CMP handles the banner and the user experience; Ingest Labs handles the enforcement and the audit trail. Every event carries its consent state, every blocked event is logged, and compliance isn't a banner-deep illusion.
Integration resources
Setup guide for the custom consent integration, including SDK methods, cookie schema, and API endpoints.
Contact for setup guide
IAB Transparency & Consent Framework — the industry standard for consent signaling that many CMPs implement.
Visit IAB TCFIAB TCF v2.2 technical specification — consent string format, vendor lists, and purpose definitions.
TCF specificationKey benefits
Server-side consent enforcement that works with any CMP — no vendor lock-in, no consent gaps.
- Accept consent state from any CMP via SDK, cookie, or server-side API — no vendor lock-in
- Define custom consent categories that match your CMP's taxonomy, not a pre-built template
- Gate every server-side tag destination by consent category — no events leak without permission
- Configure default behavior for events with no consent signal — strict mode, essential-only, or custom
- Full audit trail for every consent decision — blocked and forwarded events logged for compliance
- Works alongside existing CMP integrations — mix OneTrust, Consentmo, and custom signals in one pipeline
Frequently Asked Questions
What consent frameworks does the custom integration support?
Any of them. Ingest Labs accepts consent state via our JavaScript SDK, a server-side API, or a consent cookie with a documented schema. If your CMP can emit a consent decision — whether it's a homegrown solution, a regional provider, or an open-source framework like Klaro or CookieBot — Ingest Labs can read it.
How do I send consent state to Ingest Labs?
Three options: (1) Pass consent categories as properties on every event via the Ingest Labs JavaScript SDK. (2) Set a consent cookie with a JSON payload that Ingest Labs reads server-side. (3) Send consent state via the Ingest Labs server-side API alongside your event data. All three approaches are documented in the setup guide.
Can I define my own consent categories?
Yes. Unlike pre-built CMP integrations, the custom consent integration lets you define any category names you want — 'marketing', 'analytics', 'personalization', or whatever your CMP uses. You map each category to one or more tag destinations in the Ingest Labs dashboard.
What happens if no consent state is sent with an event?
You configure the default behavior in the Ingest Labs dashboard. Options include: block all tags (strict mode), allow only essential/functional tags, or apply a specific default consent set. Most privacy-conscious customers choose strict mode.
Is there an audit trail?
Yes. Every event includes the consent state at the time of collection. The Ingest Labs audit log shows which events were forwarded, which were blocked, and the consent categories that applied — regardless of which CMP or consent framework produced the signal.
How long does setup take?
It depends on your CMP. If your consent framework already emits a structured consent signal (cookie, JavaScript callback, or API payload), integration typically takes a few hours. The Ingest Labs team can help map your consent schema during onboarding.
Ingest Labs custom consent integration: Server-side consent enforcement for any CMP or consent framework. Accepts consent state via SDK, cookie, or API. Maps custom consent categories to tag destinations and enforces them in real time. Full audit trail for GDPR, CCPA, and global privacy compliance.
Your consent framework. Our server-side enforcement.
Map any consent signal to any tag destination — homegrown, regional, or niche CMP.