Orchestrate consent and fulfill access and deletion requests across every Salesforce cloud, from one connection.
Salesforce is a multi-tenant CRM platform built to manage sales, service, marketing, and operations from a single system. That also means Salesforce concentrates personal data across whichever clouds an organization runs: contact records, leads, cases, marketing preferences, and increasingly, Agentforce interactions. As Salesforce continues to unify its platform, more of that data now sits on shared, cross-cloud objects rather than staying siloed by cloud.
That shared architecture is exactly what makes a single privacy connection possible. Because Salesforce Data 360 gives cross-cloud objects like the Individual record a common home, Ketch connects once and applies to Sales, Service, Marketing, Commerce, Industries, and Agentforce data alike, rather than requiring a separate integration per cloud.
Capabilities
The Ketch Salesforce integration is powered by Salesforce Data 360 and connects through OAuth, which is what lets one connection reach across clouds instead of stopping at Sales Cloud. It supports two capabilities: Consent Orchestration and Rights Orchestration.
Maps Ketch's canonical privacy purposes (categories like analytics, behavioral advertising, or email marketing) onto the specific Salesforce fields that control those behaviors, so an opt-out captured in a Ketch experience is reflected as an actual field-level change on the person's Salesforce record, not just logged somewhere else.
Handles both directions of a data subject request: Right to Access returns the Salesforce objects and fields configured for that connection, and Right to Delete removes them, with configurable control over whether a deletion cascades to related records (like cases or opportunities tied to a contact) or stays scoped to the parent object alone.
With Ketch, teams can
The gap
Salesforce was built to run sales, service, and marketing operations, not to reconcile a person's consent state or fulfill their rights request across every cloud your org happens to be using. That mismatch shows up consistently:
Why Ketch
Permissioning infrastructure that governs Salesforce the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Ketch connects at the Data 360 layer that Salesforce itself is consolidating around, so the integration scales with an organization's Salesforce footprint instead of needing to be rebuilt cloud by cloud.
The California Privacy Protection Agency fined Honda $632,000 over asymmetrical opt-out processes and inconsistent enforcement of consumer choices, a reminder that a consent signal which doesn't propagate consistently across every system holding a person's data is a real regulatory exposure, not just an inconvenience.
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 Salesforce yourself.
Get started in less than 5 min
