Manage Privacy requests in Campaign

Depending on the nature of your business and the jurisdictions it operates under, your data operations may be subject to legal privacy regulations. These regulations often give your customers the right to request access to the data you collect from them, and the right to request the deletion of that stored data. These customer requests for their personal data are referred to as “Privacy requests” throughout the documentation.

Adobe offers Data Controllers the tools to create and process Privacy requests for data stored in Campaign. However, it is your responsibility as a Data Controller to verify the identity of the Data Subject making the request, and to confirm that the data returned to the requester is about the Data Subject. Learn more on personal data and the different entities that manage data in Adobe Campaign Classic v7 documentation.

To manage Privacy request in Campaign, you must first define a namespace. You are then able to create and manage Privacy requests. To perform privacy requests, use the Adobe Privacy Service integration. Privacy requests pushed from the Privacy Service to all Adobe Experience Cloud solutions are automatically handled by Campaign via a dedicated workflow. Learn more

Learn about the Right to Access and the Right to be Forgotten (delete request) in Adobe Campaign Classic v7 documentation.

Define a namespace

Before creating a Privacy request, you must define the namespace to use. The namespace is the key which is used to identify the Data Subject in the database.

Currently Adobe Campaign does not support importing namespaces from the Experience Platform Identity Namespace service. Therefore, once you have created a namespace on the Identity Namespace service, you must create manually the corresponding namespace in the Adobe Campaign interface. To do this, follow the steps below.

1. Create a namespace on the Identity Namespace service.

2. When listing the identity namespaces available for your organization, you get the namespace following details, for example:

   {
           "updateTime": 1632903236731,
           "code": "lumanamespace",
           "status": "ACTIVE",
           "description": "new namespace for Luma privacy requests",
           "id": 10998717,
           "createTime": 1632903236731,
           "idType": "Email",
           "namespaceType": "Custom",
           "name": "Luma Namespace",
           "custom": true
   }
   

3. In Adobe Campaign, browse to Administration > Platform > Namespaces and select New.

   

4. Enter a Label.

5. Fill in the new namespace details to match the namespace that you created on the Identitiy Namespace service:

   • the AEC Namespace ID must match the “id” attribute
   • the Internal name must match the “code” attribute
   • the Reconciliation key must match the “idType” attribute

   

   The Reconciliation key field will be used to identify the Data Subject in the Adobe Campaign database.

6. Select a target mapping to specify how the namespace will be reconciled in Adobe Campaign.

   NOTE

   If you need to use several target mappings, create one namespace per target mapping.

7. Save your changes.

You can now create Privacy requests based on your new namespace. If you use several namespaces, create one Privacy request per namespace for the same reconciliation value.

Create a Privacy request

The Adobe Experience Platform Privacy Service integration allows you to automate your Privacy requests in a multi-solution context through a single JSON API call. Adobe Campaign automatically handles the requests pushed from the Privacy Service through a dedicated workflow.

Refer to the Experience Platform Privacy Service documentation to learn how to create Privacy requests from the Privacy Core Service.

Each Privacy Service job is split into multiple Privacy requests in Adobe Campaign based on how many namespaces are being used, one request corresponding to one namespace.

Also, one job can be run on multiple instances. Therefore, multiple files are created for one job. For example, if a request has two namespaces and is running on three instances, then a total of six files are sent. One file per namespace and instance.

The pattern for a file name is: <InstanceName>-<NamespaceId>-<ReconciliationKey>.xml

• InstanceName: Campaign instance name
• NamespaceId: Identity Service Namespace ID of the namespace used
• Reconciliation key: Encoded reconciliation key

Tables searched when processing requests

When performing a Delete or Access Privacy request, Adobe Campaign searches all the Data Subject’s data based on the Reconciliation value in all the tables that have a link to the recipient table (own type).

The list of built-in tables taken into account when performing Privacy requests are:

• Recipients (recipient)
• Recipient delivery log (broadLogRcp)
• Recipient tracking log (trackingLogRcp)
• Archived event delivery log (broadLogEventHisto)
• Recipient list content (rcpGrpRel)
• Visitor offer proposition (propositionVisitor)
• Visitors (visitor)
• Subscription history (subHisto)
• Subscriptions (subscription)
• Recipient offer proposition (propositionRcp)

If you created custom tables that have a link to the recipient table (own type), they will also be taken into account. For example, if you have a transaction table linked to the recipient table and a transaction details table linked to the transaction table, they will be both taken into account.

Privacy request statuses

You can find below the different statuses for Privacy requests in Adobe Campaign and how to interpret them:

• New / Retry pending: in progress, the workflow has not processed the request yet.
• Processing / Retry in progress: the workflow is processing the request.
• Delete pending: the workflow has identified all the recipient data to delete.
• Delete in progress: the workflow is processing the deletion.
• Complete: the processing of the request has finished without an error.
• Error: the workflow has encountered an error. The reason is displayed in the list of Privacy requests in the Request status column. For example, Error data not found means that no recipient data matching the Data Subject’s Reconciliation value has been found in the database.

Related topics in Campaign Classic v7 documentation:

• Privacy and consent

• Getting started with Privacy Management

• Regulations on Privacy management (GDPR, CCPA, PDPA, and LGPD)

• Opt-out for the Sale of Personal Information (specific to CCPA)