Label inheritance for audience segments

All audience segments created by Adobe Experience Platform Segmentation Service inherit the usage labels of their corresponding datasets. This allows Experience Platform to provide automatic policy enforcement when activating segments to destinations.

In addition to inheriting dataset-level labels, segments inherit all field-level labels from their associated datasets by default. Therefore, you can more easily identify which attributes should be excluded from your segments and prevent them from inheriting labels from excluded fields.

For more information on how automatic enforcement works in Platform, see the overview on automatic policy enforcement.

Inheritance from Adobe Audience Manager Data Export Controls

Experience Platform has the ability to share segments with Adobe Audience Manager. Any Data Export Controls that have been applied to Audience Manager segments are translated to equivalent labels and marketing actions recognized by Experience Platform Data Governance.

For a reference on how specific Data Export Controls map to data usage labels in Platform, please refer to the Audience Manager documentation.

Managing data usage labels in Experience Platform

You can manage data usage labels using Experience Platform APIs or the user interface. Refer to the subsections below for details on each.

Using the UI

The Policies workspace in the Experience Platform UI allows you to view and manage core and custom labels for your organization. You can use the Schemas workspace to apply labels to your Experience Data Model (XDM) schemas, or learn how to create and manage custom labels in the **Policies UI by reading the data usage labels user guide instead.

IMPORTANT
Labels can no longer be applied to fields at the dataset level. This workflow has been deprecated in favour of applying labels at the schema level. Any labels previously applied at the dataset object level will still be supported through the Platform UI until 31st May 2024. To ensure that your labels are consistent across all schemas, any labels previously attached to fields at the dataset level must be migrated to the schema level by you over the coming year. See the section on migrating previously applied labels for instructions on how to do this.

Using APIs

The /labels endpoint in the Policy Service API allows you to programmatically manage data usage labels, including creating custom labels. Refer to the labels endpoint guide for more information.

The Dataset Service API is used to manage labels for dataset and fields. See the guide on managing dataset labels for more information.

Next steps

This document provided an introduction to data usage labels and their role within the Data Governance framework. Refer to the documentation linked to throughout this guide to lean more about how to manage labels in Experience Platform.

Previous pageEnd-to-end guide
Next pageLabels glossary

Experience Platform