Rights Orchestration
Right to Delete creates an actual Adobe privacy job, visible and verifiable on the Privacy UI tab inside Adobe Experience Cloud.
Ketch and Adobe Target
Register a real, trackable deletion job inside Adobe's own systems for A/B testing and personalization data, verifiable in Adobe's own Privacy Service UI.
About Adobe Target
Adobe Target runs A/B tests, multivariate tests, and personalized content variations across websites and apps, which means visitor behavior data feeds directly into which experience a person actually sees. Deletion against that kind of data benefits from Adobe's own privacy infrastructure, the same one used across other connected Adobe products.
Ketch connects to Adobe Target through Adobe's own Privacy Service and consent APIs to provide that.
Capabilities
How Ketch works with Adobe Target
The Ketch Adobe Target integration covers Consent Orchestration and Rights Orchestration (Right to Deletion).The privacy job can be configured to run across one or more connected Adobe products at once, using a comma-separated list of Adobe's own product identifiers, so a single deletion request can extend beyond Adobe Target to cover other connected Adobe surfaces.
Consent Orchestration
Sets Adobe's own consent signal, mapping the canonical purposes analytics, data brokering, and personalization onto Adobe's own `collect`, `share`, and `preferences` consent categories.
With Ketch, teams can
- Register real, Adobe-native privacy jobs for deletion requests, checkable directly in Adobe's own Privacy Service UI
- Map Ketch's canonical consent purposes directly onto Adobe's own consent signal categories
- Extend a single privacy job across multiple connected Adobe products, including Target alongside Audience Manager, CDP, Commerce, Campaign, or Marketo Measure
The gap
The problem this integration solves
Personalization and experimentation data connected into a broader Adobe ecosystem needs deletion that reaches further than just the testing platform itself:
01. A deletion request that doesn't use Adobe's actual privacy job mechanism has no reliable way to verify inside Adobe's own systems that it was actually registered and processed
02. Consent signals that don't map to Adobe's own `collect`/`share`/`preferences` categories won't be recognized correctly by Adobe's downstream systems
03. Handling deletion separately for Target and any other connected Adobe products adds unnecessary manual overhead
Ketch resolves this by working through Adobe's own privacy job and consent signal APIs directly, so the request is genuinely native to Adobe's systems and can extend across every connected Adobe product from one job.
Why Ketch
Why teams choose Ketch for Adobe Target privacy compliance
Permissioning infrastructure that governs Adobe Target the same way it governs every other system in your stack — not a one-off connector bolted onto a banner.
Verifiable inside Adobe's own systems
Deletion requests create a real Adobe privacy job, checkable directly in the Privacy UI tab on Adobe Experience Cloud.
Extends across the Adobe ecosystem
A single privacy job can cover Adobe Target and other connected Adobe products together.
Backed by enforcement precedent
The California Privacy Protection Agency fined Honda $632,000 over improperly configured data sharing with ad-tech partners, a reminder that personalization platforms carry real exposure when consent signals aren't mapped correctly.
Questions about the Adobe Target integration
Related reading
Expert insights for teams connecting Adobe Target
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 Adobe Target permissioning running end to end
Book a demo to walk through rights, consent, and preference orchestration on your stack — or start free and connect Adobe Target yourself.
Get Started Free
Get started in less than 5 min