Consent orchestration

Honor every visitor's choiceenforced on the server.

CMP signals are read from your site, but consent is enforced server-side before events are stored or routed to destinations. No third-party pixel scripts required.

See the platform

Server gate

Banner choice
Analytics granted · Marketing denied
Server enforces
Before storage or destination routing
Destinations
Only consented routes fire
GA4Allowed
Meta CAPIBlocked

Per-category enforcement

Analytics and marketing consent are separate

A visitor can grant analytics but deny marketing. Intently evaluates each category independently before storing events or firing destinations.

✓OneTrust, Cookiebot, CookieYes, Google Consent Mode, TCF v2
✓Required, optional, or none — per-account consent mode
✓Privacy controls for IP, geolocation, and fingerprinting

Server-side consentCookiebot detected

AnalyticsGranted

Routes to: GA4, Segment

MarketingDenied

Routes to: Meta, TikTok

PreferencesGranted

Routes to: Personalization

How it works

From banner click to destination delivery

CMP on your site

Your existing banner captures the visitor's choice.

Intently reads signals

The SDK maps consent into analytics, marketing, and preferences.

Server enforces policy

Events are stored and routed only when consent allows.

Destinations respect choice

GA4 needs analytics consent. Meta needs marketing consent.

Supported CMPs

Works with the banners you already run

OneTrust

Active group detection

Cookiebot

Statistics & marketing flags

CookieYes

Category API

Google Consent Mode

storage grants

IAB TCF v2

Purpose consents

Custom

Manual consent API

See consent enforcement live

Blocked events in the debug overlay. Consent skips never become delivery-log rows — only dispatched sends are logged.

“No single stack gives ad buyers complete first-party capture, nine inspectable attribution models, CRM + spend ROAS, delivery proof with match quality, and AI that cites the math — in one pipeline you can audit end to end.”

See the platform