Rights Orchestration
Right to Access returns prospect or user information. Right to Delete removes the user or prospect object, without cascading to related objects.
Ketch and Salesforce Pardot
Manage list and global-level opt-out with a deterministic policy for conflicting signals, and know exactly which opt-out actions can't be undone through the platform's own API.
About Salesforce Pardot
Marketing Cloud Account Engagement, formerly Salesforce Pardot, aligns B2B marketing with sales goals. Preference management here spans two distinct levels: per-topic list membership and a global prospect-level opt-out flag, and Pardot's own API has a real, permanent limitation on one of them worth knowing before it happens.
Ketch connects to Pardot with both levels handled precisely, and the limitation stated plainly.
Capabilities
How Ketch works with Salesforce Pardot
The Ketch Salesforce Pardot integration covers Rights Orchestration (Right to Access, Right to Delete), Consent Orchestration, and Preference Orchestration.When a single request contains conflicting signals, for example a grant and a deny for the same list, Ketch applies a deny-wins policy: one denied entry is enough to opt the prospect out, regardless of any other signal in the same request, which avoids nondeterministic outcomes.
Consent Orchestration
Sets the `isDoNotEmail` and `isDoNotCall` properties directly based on a person's preferences.
Preference Orchestration
Operates at two levels. Per-topic subscription maps each Ketch topic to a Pardot Static List: an opt-in adds the prospect to the list with `optedOut` set to false, while an opt-out sets `optedOut` to true. One real limitation worth knowing clearly: list opt-out is irreversible through Pardot's own API. Once set to opted-out, it cannot be reversed programmatically; only manual re-subscription through Pardot itself can undo it. Global control works separately through the prospect-level `optedOut` flag, and re-subscribing at that global level only persists if the Account Engagement connector's Opted Out sync is specifically configured to "Use Pardot's value."
With Ketch, teams can
- Manage both per-topic list membership and global prospect-level opt-out, matching Pardot's own two-tier structure
- Rely on a deterministic deny-wins policy when a request contains conflicting signals
- Know upfront that list opt-out can't be reversed through the API, so re-subscription expectations are set accurately
The gap
The problem this integration solves
Pardot's own API has real, permanent behavior around list opt-out that a privacy program needs to plan around rather than discover after the fact:
01. Assuming a list opt-out can always be reversed programmatically, when it can't, risks a serious misunderstanding if a prospect wants to re-subscribe later
02. Conflicting consent signals within the same request need a deterministic resolution, or outcomes can vary unpredictably based on processing order
03. Global re-subscribe silently failing to persist, because the connector's sync setting isn't configured correctly, can create a false sense that someone has been re-subscribed when they haven't
Ketch resolves the first by stating the irreversibility plainly, the second with an explicit deny-wins policy, and the third by documenting the connector sync setting required for global re-subscribe to actually stick.
Why Ketch
Why teams choose Ketch for Salesforce Pardot privacy compliance
Permissioning infrastructure that governs Salesforce Pardot the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Honest about a real API limitation
List opt-out's irreversibility through Pardot's API is stated clearly, not glossed over.
A deterministic policy for conflicting signals
Deny-wins resolves ambiguous requests predictably, rather than leaving outcomes to processing order.
Backed by enforcement precedent
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 B2B marketing platforms carry real exposure when opt-out behavior isn't understood and applied accurately.
Questions about the Salesforce Pardot integration
Related reading
Expert insights for teams connecting Salesforce Pardot
Integrations
Pre-built APIs with 1,000+ systems, apps, and models
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.
See Salesforce Pardot permissioning running end to end
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Salesforce Pardot yourself.
Get Started Free
Get started in less than 5 min