Data Governance

In order to apply governance and access controls to the data within Adobe Experience Platform you need to first classify the data using labels.

Labels can be applied to individual fields in a schema or to an entire dataset. For access controls you can also apply labels to objects like Audiences and Journeys and Campaigns in Journey Optimizer. There are a number of Adobe defined labels which can be applied, or you can add your own custom labels.

First let's add an identity label to the email field in your CRM schema. Click on Schemas in the left navigation and open the Profile schema you created during the previous Schemas Exercise. Click on the Labels tab to configure labels.

Search for email and select the PersonalEmail and the Email fields to label. Then click to Apply access and data governance labels.

Select to apply the I1 label which classifies the fields as containing personally identifiable information. Click save.

You should now be able to see the label applied to those fields:



In this exercise you'll create a governance policy to restrict PII data from being exported to third party destinations. Click on the Policies menu under Privacy in the left hand navigation.

Again you'll see a number of default Policies which Adobe has defined. These are all disabled by default.

Click on the create policy button and choose Data governance policy, then click Continue.

Name your policy as {your last name} - no PII to third parties, eg. gillies - no PII to third parties

This policy is going to restrict data in fields labelled I1 OR I2, so select the I1 and I2 labels from the list. Change the setting on the right to Contains any of the labels. Then click Next.

We now need to define when the policy should be applied. We do this through the Marketing Actions which are applied to our Destinations. Select the Export to Third Party marketing action from the list. Click Next.

You can now see a summary of your policy. Click Finish to create your policy.

By default your policy will be disabled, you need to enable it before it will take effect. If there are any existing violations to the policy you will not be able to enable it until the violations are resolved.