On this page: Use the Adobe Experience Platform Privacy Service to submit and manage data access and deletion requests for Adobe Journey Optimizer, so you can fulfill data subject rights and automate compliance with privacy regulations.
Adobe Experience Platform Privacy Service provides a RESTful API and user interface to help you manage customer data requests. With Privacy Service, you can submit requests to access and delete personal customer data from Adobe CX Enterprise applications, facilitating automated compliance with legal and organizational privacy regulations.
Privacy requests can be created and managed from the Requests menu.
For more information on Privacy Service and how to create and manage privacy requests, refer to the Adobe Experience Platform documentation.
Manage individual data privacy requests that you can send to Adobe Journey Optimizer data-privacy-requests
You can submit individual requests to access and delete consumer data from Adobe Journey Optimizer in two ways:
- Through the Privacy Service UI. Learn more
- Through the Privacy Service API. Learn more
Privacy Service supports two types of requests: data access and data deletion.
For access requests, specify “Adobe Journey Optimizer” from the UI (or “CJM” as a product code in the API).
For delete requests, in addition to the “Adobe Journey Optimizer” request, you must also submit delete requests to three upstream services to prevent Journey Optimizer from reinjecting the deleted data. If these upstream services are not specified, the “Adobe Journey Optimizer” request will remain in the “processing” state until delete requests for the upstream services are created.
The three upstream services are:
- Profile (product code: “profileService”)
- AEP Data Lake (product code: “AdobeCloudPlatform”)
- Identity (product code: “identity”)
Create access and delete requests
Prerequisites
To make requests to Access and Delete data for Adobe Journey Optimizer, you must have:
- an Adobe organization ID
- an Identity identifier of the person you want to act on and the corresponding namespace(s).For more information about identity namespaces in Adobe Journey Optimizer and Experience Platform, see the identity namespace overview.
Required field values in Journey Optimizer for API requests
"companyContexts":
"namespace": imsOrgID
"value": <Your Adobe Organization ID Value>
"users":
"action": either access or delete
"userIDs":
"namespace": e.g. email, aaid, ecid, etc.
"type": standard
"value": <Data Subject's Identity Identifier>
"include":
CJM (which is the Adobe product code for Adobe Journey Optimizer)
profileService (product code for Profile)
AdobeCloudPlatform (product code for AEP Data Lake)
identity (product code for Identity)
"regulation":
gdpr, ccpa, pdpa, lgpd_bra, or nzpa_nzl (which is the privacy regulation that applies to the request)
GDPR Access request example:
From the UI:
Through the API:
// JSON Request
{
"companyContexts":[
{
"namespace":"imsOrgID",
"value":"745F37C35E4B776E0A49421B@AdobeOrg"
}
],
"users":[
{
"action":[
"access"
],
"userIDs":[
{
"namespace":"ecid",
"value":"38400000-8cf0-11bd-b23e-10b96e40000d",
"type":"standard"
},
{
"namespace":"email",
"value":"johndoe4@gmail.com",
"type":"standard"
}
]
}
],
"include":[
"CJM"
],
"regulation":"gdpr"
}
// JSON Response
{
"requestId": "17163122360480365RX-705",
"totalRecords": 1,
"jobs": [
{
"jobId": "e709b1f4-1796-11ef-b422-eddd0aebc40d",
"customer": {
"user": {
"key": "John Doe",
"action": [
"access"
],
"userIDs": [
{
"namespace": "ecid",
"value": "38400000-8cf0-11bd-b23e-10b96e40000d",
"type": "standard",
"namespaceId": 4,
"isDeletedClientSide": false
},
{
"namespace": "email",
"value": "johndoe4@gmail.com",
"type": "standard",
"namespaceId": 6,
"isDeletedClientSide": false
}
]
}
}
}
]
}
GDPR Delete request example:
From the UI:
Through the API:
// JSON Request
{
"companyContexts": [
{
"namespace": "imsOrgID",
"value": "745F37C35E4B776E0A49421B@AdobeOrg"
}
],
"users": [
{
"action": [
"delete"
],
"userIDs": [
{
"namespace": "ecid",
"value": "38400000-8cf0-11bd-b23e-10b96e40000d",
"type": "standard"
},
{
"namespace": "email",
"value": "johndoe4@gmail.com",
"type": "standard"
}
]
}
],
"include": [
"CJM", "profileService", "AdobeCloudPlatform", "identity"
],
"regulation": "gdpr"
}
// JSON Response
{
"requestId": "17163122360480365RX-705",
"totalRecords": 1,
"jobs": [
{
"jobId": "e709b1f4-1796-11ef-b422-eddd0aebc40d",
"customer": {
"user": {
"key": "John Doe",
"action": [
"delete"
],
"userIDs": [
{
"namespace": "ecid",
"value": "38400000-8cf0-11bd-b23e-10b96e40000d",
"type": "standard",
"namespaceId": 4,
"isDeletedClientSide": false
},
{
"namespace": "email",
"value": "johndoe4@gmail.com",
"type": "standard",
"namespaceId": 6,
"isDeletedClientSide": false
}
]
}
}
}
]
}
This section contains structured knowledge intended to support interpretation, retrieval, and question answering related to this topic.
For complete understanding, this information should be combined with the documentation on this page. Neither source is intended to stand alone; the page describes the feature, while this section provides additional context that helps disambiguate terminology, intent, applicability, and constraints.
- TL;DR: This page explains how to use the Adobe Experience Platform Privacy Service to submit and manage data access and deletion requests for Adobe Journey Optimizer so you can fulfill data subject rights and automate compliance with privacy regulations.
Intents:
- Understand how Privacy Service manages data access and deletion requests
- Submit privacy requests through the Privacy Service UI or API
- Identify the product code and upstream services required for delete requests
- Understand the prerequisites and required field values for requests
- Know which privacy regulations can be specified on a request
Glossary:
- Privacy Service: Adobe Experience Platform service that provides a RESTful API and user interface to manage customer requests to access and delete personal customer data (product-specific)
- Privacy request: a data access or data deletion request submitted for Adobe Journey Optimizer, created and managed from the Requests menu (product-specific)
- CJM: the Adobe product code for Adobe Journey Optimizer, used in the API
includefield (product-specific) - Upstream services: Profile (
profileService), AEP Data Lake (AdobeCloudPlatform), and Identity (identity), to which delete requests must also be submitted to prevent Journey Optimizer from reinjecting the deleted data (product-specific) - Requests: the menu from which privacy requests can be created and managed (product-specific)
Guardrails:
- Privacy Service supports two types of requests: data access and data deletion
- For access requests, specify “Adobe Journey Optimizer” from the UI, or “CJM” as the product code in the API
- For delete requests, in addition to the “Adobe Journey Optimizer” request you must also submit delete requests to three upstream services — Profile (
profileService), AEP Data Lake (AdobeCloudPlatform), and Identity (identity) — otherwise the “Adobe Journey Optimizer” request remains in the “processing” state - For delete requests, if you do not explicitly include the product name and all applicable namespaces, data is not removed from Adobe Journey Optimizer
- Making a privacy request to Adobe Journey Optimizer will not remove data from all these systems; each system must be called individually
- Prerequisites: an Adobe organization ID, and an identity identifier of the person to act on with the corresponding namespace(s)
- The regulation value must be one of:
gdpr,ccpa,pdpa,lgpd_bra, ornzpa_nzl
Terminology:
- Canonical name: Privacy request — variants: data access request, data deletion request
- Synonyms: “Adobe Journey Optimizer” (product name in the UI) = “CJM” (product code in the API)
- Do not confuse: “data access” request ≠ “data deletion” request
- Do not confuse: “Adobe Journey Optimizer” request ≠ the three upstream services (Profile, AEP Data Lake, Identity) that delete requests must also target
FAQ:
- Q: What are the two types of privacy requests? — Data access and data deletion.
- Q: What product code represents Adobe Journey Optimizer in the API? — CJM.
- Q: Why must delete requests also target upstream services? — To prevent Journey Optimizer from reinjecting the deleted data; otherwise the request remains in the “processing” state.
- Q: Which upstream services must be included in a delete request? — Profile (
profileService), AEP Data Lake (AdobeCloudPlatform), and Identity (identity). - Q: Which regulations can be specified? —
gdpr,ccpa,pdpa,lgpd_bra, ornzpa_nzl. - Q: Does a privacy request to Adobe Journey Optimizer remove data from all systems? — No, each system must be called individually to make sure the request is handled.