Make sure a cookieless identity platform only starts collecting data once someone has actually said yes, not by default the moment its SDK loads.
Permutive builds an in-the-moment view of site visitors without relying on third-party cookies, which makes it attractive for publishers navigating cookie deprecation. But Permutive's default behavior, what it calls consent-by-default, assumes the data controller has already secured consent the instant its SDK loads. That default only works correctly if it's paired with a real mechanism gating collection behind an actual consent choice.
Ketch connects to Permutive to establish that mechanism and to handle deletion for identifiers Permutive has already collected.
Capabilities
The Ketch Permutive integration covers Consent Orchestration and Rights Orchestration (Right to Delete).
Establishes an opt-in/opt-out signal that gates data collection, ensuring collection only happens once a person is actually opted in, rather than relying on Permutive's consent-by-default assumption. This requires configuring Permutive's SDK in consent-by-token mode, which blocks collection until a consent token is actually transmitted.
Works differently from most integrations on this list: Ketch sends a server-side opt-out event to Permutive that can be configured to delete or suppress a person's Permutive ID, and that same event mechanism can be configured to fulfill Right to Delete requirements on the Permutive platform.
With Ketch, teams can
The gap
A cookieless identity platform that assumes consent by default is only as compliant as the mechanism gating it. Left unconnected, that creates a real risk:
Why Ketch
Permissioning infrastructure that governs Permutive the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Rather than accepting Permutive's default assumption of consent, Ketch configures the SDK into consent-by-token mode so collection genuinely waits for a real decision.
A server-side event reaches the Permutive ID directly, matching how Permutive's identifier system actually works rather than assuming a client-side identifier flow.
The California Attorney General reached a $1.55 million settlement with Healthline Media over sharing sensitive data with advertisers without valid consent, a reminder that any system that starts collecting before consent is confirmed creates real exposure.
Related reading
Integrations
Ketch ships connectors and SDKs so consent, rights, and policy flow into your CDPs, warehouses, ad platforms, and AI stack — without a custom data pipeline.
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Permutive yourself.
Get started in less than 5 min
