Channel messaging consent
Adobe Journey Optimizer B2B Edition reads per-person consent preferences stored in Adobe Experience Platform XDM profiles and enforces them at message delivery time, as part of the app’s governance controls. Persons who opted out of a channel are excluded from delivery before content is sent from the channel or downstream messaging provider.
The following sections describe how Journey Optimizer B2B Edition evaluates consent at message send time for each supported channel.
Email email
Journey Optimizer B2B Edition evaluates the following XDM attribute for email consent when sending messages on the email channel:
ynconsents.marketing.email.valKeep the following considerations in mind for email consent:
- Persons who opted out globally from email can receive emails marked as operational.
- Subscription-level preferences are not supported.
SMS sms
Journey Optimizer B2B Edition evaluates the following XDM attributes for SMS consent when sending messages through the SMS channel:
ynconsents.marketing.sms.valconsents.marketing.subscriptions.<senderID>consents.marketing.sms.subscriptions.<senderId>.subscribers.<phoneNumber>Keep the following considerations in mind for SMS consent:
- When a lead (person) record is opted out of SMS, the record is excluded entirely and is not passed to downstream SMS providers.
- When available, subscription-level consent is evaluated. Global opt-out is used as a fallback when subscription-level consent is unavailable.
- Persons opted out from SMS can still receive messages marked as operational.
- If multiple lead records share the same phone number, they share the same opt-in or opt-out status.
WhatsApp whatsapp
Journey Optimizer B2B Edition evaluates the following XDM attributes for WhatsApp consent when sending messages through a configured WhatsApp channel:
ynconsents.marketing.whatsApp.valconsents.idSpecific.Phone.<number>.marketing.whatsApp.valKeep the following considerations in mind for WhatsApp consent:
- If the global WhatsApp attribute value (
consents.marketing.whatsApp.val) is present, it is used for consent evaluation. - If the global attribute value is not present but a sender-specific entry is present, the sender-specific entry is used for consent evaluation.
- If no value is present for either attribute, the person is treated as opted out.
Not supported not-supported
The following consent-related features are not currently supported in Journey Optimizer B2B Edition:
- AEP Consent Policies
- Marketing Preferred attributes (
consents.marketing.preferred)