Adobe Experience Platform Data Governance provides a user interface that allows you to create and manage data usage policies. This document provides an overview of the actions that you can perform in the Policies workspace in the Experience Platform user interface.
All data usage policies (including core policies provided by Adobe) are disabled by default. In order for an individual policy to be considered for enforcement, you must manually enable that policy. See the section on enabling policies for steps on how to do this in the UI.
This guide requires a working understanding of the following Experience Platform concepts:
In the Experience Platform UI, select Policies to open the Policies workspace. In the Browse tab, you can see a list of available policies, including their associated labels, marketing actions, and status.
If you have access to consent policies, select the Consent policies toggle to view them in the Browse tab.
Select a listed policy to view its description and type. If a custom policy is selected, additional controls are displayed to edit, delete, or enable/disable the policy.
To create a new custom data usage policy, select Create policy in the top-right corner of the Browse tab in the Policies workspace.
Depending on whether you are part of the beta for consent policies, one of the following occurs:
The Create policy workflow appears. Start by providing a name and a description for the new policy.
Next, select the data usage labels that the policy will be based on. When selecting multiple labels, you are given the option to choose whether the data should contain all the labels or just one of them in order for the policy to apply. Select Next when finished.
The Select marketing actions step appears. Choose the appropriate marketing actions from the provided list, then select Next to continue.
When selecting multiple marketing actions, the policy interprets them as an “OR” rule. In other words, the policy applies if any of the selected marketing actions are performed.
The Review step appears, allowing you to review the details of the new policy before creating it. Once you are satisfied, select Finish to create the policy.
The Browse tab reappears, which now lists the newly created policy in “Draft” status. To enable the policy, see the next section.
Consent policies are currently only available for organizations that have purchased Healthcare Shield.
If you chose to create a consent policy, a new screen appears that allows you to configure the new policy.
In order to make use of consent policies, you must have consent attributes present in your profile data. See the guide on consent processing in Experience Platform for detailed steps on how to include the required attributes in your union schema.
Consent policies are comprised of two logical components:
Under the If section, select the marketing actions and/or data usage labels that should trigger this policy. Select View all and Select labels to view the full lists of available marketing actions and labels, respectively.
Once you have added at least one condition, you can select Add condition to continue adding further conditions as necessary, choosing the appropriate condition type from the dropdown.
If you select more than one condition, you can use the icon that appears between them to switch the conditional relationship between “AND” and “OR”.
Under the Then section, select at least one consent attribute from the union schema. This is the attribute that must be present in order for profiles to be included in the action governed by this policy. You can choose one of the provided options from the list, or select View all to choose the attribute directly from the union schema.
When selecting the consent attribute, choose the values for the attribute that you want this policy to check for.
After you have selected at least one consent attribute, the Policy properties panel updates to show the estimated number of profiles that would be allowed under this policy, including the percentage of the total profile store. This estimation automatically updates as you adjust the policy configuration.
To add further consent attributes to the policy, select Add result.
You can continue adding and adjusting conditions and consent attributes to the policy as needed. When you are satisfied with the configuration, provide a name and optional description for the policy before selecting Save.
The consent policy is now created, and its status is set to Disabled by default. To enable the policy right away, select the Status toggle in the right rail.
After you have created and enabled a consent policy, you can preview how it affects your consented audiences when activating segments to destinations. See the section on consent policy evaluation for more information.
All data usage policies (including core policies provided by Adobe) are disabled by default. For an individual policy to be considered for enforcement, you must manually enable that policy through the API or UI.
You can enable or disable policies from the Browse tab in the Policies workspace. Select a custom policy from the list to display its details on the right. Under Status, select the toggle button to enable or disable the policy.
In the Policies workspace, select the Marketing actions tab to view a list of available marketing actions defined by Adobe and your own organization.
To create a new custom marketing action, select Create marketing action in the top-right corner of the Marketing actions tab in the Policies workspace.
The Create marketing action dialog appears. Enter a name and description for the marketing action, then select Create.
The newly created action appears in the Marketing actions tab. You can now use the marketing action when creating new data usage policies.
Only custom marketing actions defined by your organization can be edited. Marketing actions defined by Adobe cannot be changed or deleted.
In the Policies workspace, select the Marketing actions tab to view a list of available marketing actions defined by Adobe and your own organization. Select a custom marketing action from the list, then used the provided fields in the right-hand section to edit the marketing action’s details.
If the marketing action is not being used by any existing usage policies, you can delete it by selecting Delete marketing action.
Attempting to delete a marketing action that is being used by an existing policy causes an error message to appear, indicating that the delete attempt failed.
This document provided an overview of how to manage data usage policies in Experience Platform UI. For steps on how to manage policies using the Policy Service API, see the developer guide. For information on how to enforce data usage policies, see the policy enforcement overview.
The following video provides a demonstration of how to work with usage policies in the Experience Platform UI: