Work with consent policies consent-management

Your data may be subject to usage restrictions defined by your organization or by legal regulations. It is therefore important to ensure that your data operations within Journey Optimizer are compliant with data usage policies. These policies are Adobe Experience Platform rules defining which marketing actions you are allowed to perform on data.

One type of data usage policies available are consent policies. They allow you to easily adopt and enforce marketing policies to respect the consent preferences of your customers. Learn more on policy enforcement

Consent policies are currently only available for organizations that have purchased the Adobe Healthcare Shield or Privacy and Security Shield add-on offerings.

For example, you can create consent policies in Experience Platform to exclude customers who have not consented to receive email, push or SMS communications.

At the journey level, you can apply consent policies to your custom actions:

  • When configuring a custom action, you can define a channel and marketing action. Learn more
  • When adding the custom action in a journey, you can define an additional marketing action. Learn more

Important notes important-notes

In Journey Optimizer, consent can be leveraged in custom actions. If you want to use it with the build-in message capabilities, you need to use a condition activity to filter customers in your journey.

With consent management, two journey activities are analyzed:

  • Read audience: the retrieved audience is taken into account.
  • Custom action: consent management takes into account the attributes used (action parameters) as well as the marketing action(s) defined (required marketing action and additional marketing action).
  • Attributes that are part of a field group using the out-of-the-box Union Schema are not supported. These attributes will be hidden from the interface. You need to create another field group using a different schema.
  • Consent policies only apply when a marketing action (required or additional) is set at the custom action level.

All other activities used in a journey are not taken into account. If you start your journey with an Audience qualification, the audience is not taken into account.

In a journey, if a profile is excluded by a consent policy in a custom action, the message is not sent to him, but he continues the journey. The profile does not go to the timeout and error path when using a condition.

Before refreshing policies in a custom action positioned in a journey, make sure your journey has no error.

Configuring the custom action consent-custom-action

When configuring a custom action, two fields can be used for consent management.

The Channel field allows you to select the channel related to this custom action: Email, SMS, or Push notification. It prefills the Required marketing action field with the default marketing action for the selected channel. If you select other, no marketing action is defined by default.

The Required marketing action allows you to define the marketing action related to your custom action. For example, if you use that custom action to send emails, you can select Email targeting. When used in a journey, all consent policies associated with that marketing action are retrieved and leveraged. A default marketing action is selected, but you can click the down arrow to select any available marketing actions from the list.

For certain types of important communications, for example a transactional message sent to reset the client’s password, you may not want to apply a consent policy. You will then select None in the Required marketing action field.

The other steps for configuring a custom action are detailed in this section.

Building the journey consent-journey

When adding the custom action in a journey, several options allow you to manage consent. Click the Show read-only fields to display all parameters.

The Channel and Required marketing action, defined when configuring the custom action, are displayed at the top of the screen. You cannot modify these fields.

You can define an Additional marketing action to set the type of custom action. This allows you to define the purpose of the custom action in this journey. In addition to the required marketing action, which is usually specific to a channel, you can define an additional marketing action which is specific to the custom action in this particular journey. For example: a workout communication, a newsletter, a fitness communication, etc. Both the required marketing action and the additional marketing action apply.

Click the Refresh policies button, at the bottom of the screen, to update and check the list of policies taken into consideration for this custom action. This is for information purpose only, while building a journey. With live journeys, consent policies are retrieved and updated automatically every 6 hours.

The other steps for configuring a custom action in a journey are detailed in this section.