Adobe Experience Platform Privacy Service provides a user interface that allows you to view and create privacy requests for your organization. In this video, we’re going to walk through the different features of the UI, including how to create a privacy request. The Privacy Service UI can only be accessed by system administrators for your organization. If you are not a sysadmin, you’ll have to contact an existing sysadmin to grant you access through Adobe Admin Console. See the Admin Console documentation for more information on granting admin rights. Once we have system admin rights, we’ll navigate to the Experience Cloud homepage, then select Privacy UI. When we arrive on the dashboard, we can see an overview of the status of other requests that have been created previously. On the top right of the screen, we can switch the experience between different regulations and the dashboard updates to show only jobs under the selected regulation. The status report widget shows a graph of the total requests made over the last 7 days as well as the number of errors that were reported. If we hover over any point in this graph, we can see further details, and if we select that point, the list of jobs below filters to only those that were created on that date. To remove a filter from the list, select the X on the pill icon in the job requests section. Using the drop down menu next to the graph, we can extend the range to 14 days or 30 days. We can also select a custom range for specific dates up to a maximum of 60 days. We’ll get into looking at the details of individual jobs in a moment. For now, let’s create a new privacy request. On the top right of the page, we’ll use the drop down menu to select a specific regulation that we want to file the request under. In our case, we want to create a CCPA request. A privacy request can only be filed under a single regulation. Next, we’ll select Create Request. In the dialog that appears, we can start configuring our privacy requests. We’ll start with the job type. This can be either Delete, Access, or both. We’ll just select Delete for now. Next, we have to choose the experience called Products that will process the request. Since we’re making a request for data that is stored in Adobe Experience Platform, we’ll select both Data Lake and Profile from the list. Finally, we have to provide some customer identity information. Specifically, we have to choose a namespace type and enter a list of identity values. If you watched the video on Identity Data and Privacy Requests, you’ll remember that we have to use the identity types that are used by the specific products we are making this request for. Let’s start with the namespace type. The standard namespace type is supported for most Experience Cloud products and contains globally recognized identifier types like email, phone, ECID, and more. There are other namespace types that are accepted by specific Experience Cloud products. If we were making a request that involved a custom namespace defined in Adobe Analytics, for example, we could select Analytics here. However, the request builder in the UI is currently limited to only using a single namespace type. If we wanted to use multiple identity types, we would need to make separate requests for each type. In the Privacy Service API, however, different identity types can be combined in a single request. If we know how to format a JSON payload for a privacy request like in the API, we can select Upload JSON from the Dashboard and make our request that way instead. See the video on using the Privacy Service API for more information on how to format your JSON payloads. For now, we’ll just stick to the standard type in the request builder. Finally, we have to provide some ID values for the request. In our case, we know that the Experience Platform implementation uses customers’ email addresses as their primary identities, so we’ll choose the email namespace from the dropdown menu. We’ll add our comma separated list of email addresses, and then we’ll hit Create to send the request to Privacy Service. Based on how we configured our request, the system creates privacy jobs, one for each customer ID that we provided. These are listed under the Job Requests section on the dashboard, where we can see their ID, status, and request type. If we selected both access and delete when configuring our request earlier, Privacy Service would make separate jobs for each ID, one for access and one for delete. If we select a job ID from the list, we can see the status of each of the Experience Cloud products that are processing the request. When one of the processes completes, this screen will update with further details provided by the product in question. Keep in mind that some solutions will take longer than others to finish processing. For example, real-time customer profile can sometimes complete in less than 24 hours, while analytics can take anywhere between 5 and 10 days. Now, creating privacy requests in the UI like this is great if you are testing your implementation, but what if you want to automate the process of sending privacy requests in your application? In this case, you can integrate the Privacy Service API into your app or website to send the request for you. See the video tutorial on getting started with the Privacy Service API for more information. By watching this video, you’ve now been introduced to the capabilities offered by the Privacy Service UI. For more information on the different configuration options, particular to different Experience Cloud applications, please refer to the documentation. Thanks for watching.