In this lesson, you will apply the data governance framework to the data you’ve ingested into your sandbox.
Adobe Experience Platform Data Governance allows you to manage customer data and ensure compliance with regulations, restrictions, and policies applicable to data use. It plays a key role within Experience Platform at various levels, including controlling usage of data.
Before you begin the exercises, watch these short videos about data governance:
Luma makes a promise to members of their Loyalty program, that Loyalty data will not be shared with any third parties. We will implement this scenario in the rest of the lesson.
The first step in the data governance process, is to apply governance labels to your data. Before we do that, let’s take a quick look at what labels are available:
There are many out-of-the-box labels, plus you can create your own via the Create label button. There are three main types: Contract labels, Identity labels, and Sensitive labels that correspond to common reasons data might be restricted. Each of the labels has a Friendly Name and a short Name which is just an abbreviation of the type and a number. For example, the C1 label is for “No third-party export” which is what we need for our Loyalty policy.
Now it’s time to label the data whose usage we want to restrict:
Luma Loyalty Dataset
Now that our data is labeled, we can create a policy.
You can create your own policies by selecting the Create policy button. This opens a wizard which allows you can combine multiple labels and marketing action restrictions.
Enforcement of governance policies is obviously a key component to the framework. Enforcement happens downstream when data is activated and sent out of Platform, especially with the Real-time Customer Data Platform, which you may or may not be licensing. Either way, it’s out of the scope of this tutorial. But so you’re not left hanging, you can learn more about how policies are enforced in this video, which I’ve queued up to the relevant portion. It will also show you what happens when a policy is violated.
Now let’s move on to query service.