在此頁面上：使用 Adobe Experience Platform Privacy Service 來提交和管理 Adobe Journey Optimizer 的資料存取和刪除請求，以便您履行資料主體權利並自動遵守隱私權法規。
Adobe Experience Platform Privacy Service 提供 RESTful API 和使用者介面，幫助您管理客戶資料請求。 透過 Privacy Service，您可以提交請求，以存取及刪除 Adobe CX Enterprise 應用程式中的個人客戶資料，協助自動遵循法律和組織的隱私權法規。
可以從 請求 功能表建立並管理隱私權請求 。
如需隱私服務以及如何建立和管理隱私請求的詳細資訊，請參閱 Adobe Experience Platform 文件。
管理您可傳送至 Adobe Journey Optimizer 的個別資料隱私請求 data-privacy-requests
您可以透過兩種方式，提交個別請求以存取和刪除 Adobe Journey Optimizer 中消費者資料：
Privacy Service 支援兩種類型的請求：資料存取和資料刪除。
對於存取請求，從 UI 指定「Adobe Journey Optimizer」(或「CJM」作為 API 的產品程式碼)。
對於刪除請求，除「Adobe Journey Optimizer」請求外，您還必須向 三個上游服務 提交刪除請求，以防止 Journey Optimizer 重新插入已刪除的資料。 如果未指定這些上游服務，「Adobe Journey Optimizer」請求將維持在「處理」狀態，直到建立上游服務的刪除請求為止。
這三種上游服務為：
- 設定檔 (產品代碼：「profileService」)
- AEP 資料湖 (產品代碼：「AdobeCloudPlatform」)
- 身分 (產品代碼：「identity」)
NOTE
本指南僅涵蓋向 Adobe Journey Optimizer 提出隱私請求的方法。
對於刪除及存取請求，您需要呼叫這些個別系統，以確保每個系統都能處理請求。 向 Adobe Journey Optimizer 提出隱私請求並不會移除所有這些系統的資料。
建立存取與刪除請求
先決條件
若要請求存取及刪除 Adobe Journey Optimizer 的資料，您必須：
- Adobe 組織 ID
- 您要對其採取動作之人員的身分識別碼以及對應名稱空間。如需 Adobe Journey Optimizer 與 Experience Platform 身分命名空間的詳細資訊，請參閱身分命名空間概觀。
IMPORTANT
提交隱私請求時，請務必指定「'Adobe Journey Optimizer」作為目標產品名稱，並指定與需要存取或移除的設定檔資料相關聯的所有身分識別命名空間 (例如「電子郵件」、「ECID」或「忠實客戶 ID」)。 尤其是對於刪除請求，如果您未明確包含產品名稱和所有適用的命名空間，就不會從 Adobe Journey Optimizer 中移除資料。
Journey Optimizer 用於 API 請求的必填欄位值
"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 存取請求範例：
從 UI：
使用 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 刪除請求範例：
從 UI：
使用 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
}
]
}
}
}
]
}
AI Knowledge Reference
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.
recommendation-more-help
journey-optimizer-help