Segment Match data governance

In this video, I’m going to go through the data governance capabilities of Segment Match.

As part of the Segment Match service, we’re integrated with AEP’s dual framework to provide governance capabilities that allows organizations to restrict what data can and cannot be used within the service. To access those capabilities, we’ll go over to the policy section within Experience Platform.

Here you can see that there’s a new default policy specifically for Segment Match.

Enabling this policy will mean that any data that has the C11 label applied to it will be restricted for use within the Segment Match service.

Now that we’ve successfully enabled it, let’s quickly take a look at our datasets. Clicking into the Luma Retail dataset and going to the Data governance tab, we can see here that this entire dataset has the C11 label applied to it. Again, this label indicates that the data should not be used within the Segment Match service.

Now let’s navigate over to Segment Match.

Now we’ll create a feed, and we’ll select a segment that specifically uses that dataset to demonstrate the data governance capabilities. So we’ll go to Create feed to initiate that process.

We’ll enter in our configurations.

And then we’ll go ahead and select the Healthy Brews Loyalty Gold Member segment. This segment uses the Luma Retail dataset that we were viewing earlier.

Here we’ll select a partner to share this feed with, and we’ll see our configurations here. Now when we click finish, you’ll see that we get a data governance policy violation.

This tells us that the Healthy Brews Loyalty segment uses the Luma Retail Loyalty Members dataset, which, again, we’ve labeled with that C11 label. Because of that, Segment Match automatically detects that this segment should not be used within the service and prevents users from completing the flow. This allows organizations to control what data can and cannot be used within the Segment Match service. -