To be able to create privacy access and delete requests, as required by GDPR or CCPA, a namespace must be used to identify the data subject within the Adobe Campaign database.
Learn to create namespaces for privacy requests.
In this video I will demonstrate how to create Namespaces for GDPR requests. Before creating GDPR requests you need to define the Namespace you will use. The Namespace is the key that will be used to identify the data subject in the Adobe Campaign database. If you use several Namespaces you will need to create one GDPR request per Namespace. Out of the box two Namespaces are available, email and mobile phone. If a different Namespace is required for example, a profile custom field you will need to create it.
To do this click on the Adobe Campaign logo, go to Administration and Namespaces.
You can see the two out of the box namespaces are listed here, email and mobile phone. We’re going to create a new one and I would like to create a Namespace for the customer I.D.
Add a label.
And if you want to use an existing Identity Service namespace choose Map from Identity Namespace Service and then choose the Namespace or the Identity Service from the dropdown in the Identity Service Namespaces. In this case however, we would like to create a new Namespace, so choose Create New, add the Identity Namespace Name when Identity Service namespace is not one namespace and campaign.
You need to specify how the Namespace will be reconciled in Campaign, for this select the Target Mapping and there are three available: Recipients, Real-time event and Subscription to an application. I’m going to choose Recipients.
Choose the Reconciliation Key, this is the field that will be used to identify the data subject in the Adobe Campaign database both out of the box as well as the extension fields are available. In this case I’m choosing an extension - the customer ID. Click Create and you can now create GDPR requests based on your new namespace on the customer ID. As a reminder, if you use several Namespaces you will need to create one GDPR request per Namespace. -