Providing to recipients the capability to unsubscribe from receiving communications from a brand is a legal requirement, as well as ensuring this choice is honored. Learn more about the applicable legislation in the Experience Platform documentation.
Why is it important?
When sending messages from journeys or campaigns, you must always ensure that customers can unsubscribe from future communications. Once unsubscribed, the profiles are automatically removed from the audience of future marketing messages.
While Journey Optimizer provides ways of managing opt-out in emails and SMS messages, push notifications do not require any action on your side, as recipients can unsubscribe through their devices themselves. For example, upon downloading or when using your app, they can select to stop notifications. Similarly, they can change the notification settings through the mobile operating system.
Learn how to manage opt-out in Journey Optimizer email and SMS messages in these sections:
In Journey Optimizer, consent is handled by the Experience Platform Consent schema. By default, the value for the consent field is empty and treated as consent to receive your communications. You can modify this default value while onboarding to one of the possible values listed here.
Your customers can also opt out from being presented personalized contents. Once a profile has opted out from personalization, you need to ensure that their data is not used for personalization and you must replace any personalized content with a fallback variant.
When leveraging offers, personalization preferences are not automatically implemented in decision scopes used from a decisioning API request or edge decisioning API request. In this case, you need to manually enforce personalization consent. To do so, follow the steps below.
Decision scopes used in Journey Optimizer authored channels satisfy this requirement from the journey or campaign they belong to.
Create an Adobe Experience Platform segment using a profile attribute such as: “Consents to Personalization = True” to target users who have consented to personalization.
When creating a decision, add a decision scope and define an eligibility constraint based on this segment for each evaluation criteria collection that contains personalized offers.
Create a fallback offer that does not include personalized content.
Assign the non-personalized fallback offer to the decision.
Review and save the decision.
If a user has:
consented for personalization, the decision scope will determine the best offer for that profile.
not consented for personalization, the corresponding profile will not be eligible for any of the offers that are in the evaluation criteria and will therefore receive the non-personalized fallback offer.
Consent for having profile data used in data modeling is not supported yet in Journey Optimizer.