If you have Adobe Campaign Standard, the following out-of-the-box action activities are available: Email, Push and SMS.
For this, you need to configure the built-in action. Refer to this page.
For each of these channels, you select an Adobe Campaign Standard Transactional Messaging template. Indeed, Journey Orchestration is not a message sending solution. For the built-in email, SMS and push channels, we rely on Transactional Messaging to execute message sending. It means that if you want to use a certain message template in your journeys, you must publish it in Adobe Campaign Standard. Refer to this page to learn how to use this feature.
The Campaign Standard transactional message and its associated event must be published in order to be used in Journey Orchestration. If the event is published but the message is not, it will not be visible in the Journey Orchestration interface. If the message is published but its associated event is not, it will be visible in the Journey Orchestration interface but it will not be usable.
You can use an event (also known as real-time) or profile transactional messaging template.
When we send real-time transactional messages (rtEvent) or when we route messages with a third-party system thanks to a custom action, a specific setup is required for fatigue, block list or unsubscription management. For example, if an “unsubscribe” attribute is stored in the Adobe Experience Platform or in a third-party system, a condition will have to be added before the message sending to check this condition.
When you select a template, all the fields expected in the message payload are displayed in the activity configuration pane under Address and Personalization Data. You need to map each of these fields with the field you want to use, either from the event or from the data source. You can also use the advanced expression editor to pass a value manually, perform data manipulation on retrieved information (for example convert a string to uppercase) or use functions such as “if, then, else”. See this page.
For Email and SMS, the parameters are identical.
For email, if you’re using a profiles transactional template, the unsubscription mechanism is handled out-of-the-box by Campaign Standard. You simply add an Unsubscription link content block in the template (learn more). If you’re using an event-based template (rtEvent), you need to add, in the message, a link passing the person’s email in the URL parameter and pointing to an unsubscription landing page. You need to create this landing page and make sure the person’s decision to unsubscribe is transmitted to Adobe.
First, you need to choose a transactional messaging template. Refer to this page.
Two categories are available: Address and Personalization Data.
You can easily define where to retrieve the Address or the Personalization Data using the interface. You can browse through events and available data source’s fields. You can also use the advanced expression editor for more advanced use cases such as using a data source that requires the passing of parameters or performing manipulations. See this page.
This category is only visible if you select an “event” transactional message. For “profile” messages, the Address field is automatically retrieved from Adobe Campaign Standard by the system.
These are the fields the system requires to know where to send the message. For an email template, it’s the email address. For an SMS, it’s the mobile phone number.
You cannot pass a collection in personalization data. If the transactional email or SMS expects collections, it will not work. Also note that the personalization data has an expected format (example: string, decimal, etc.). You must be careful to respect these expected formats.
These are the fields expected by the Adobe Campaign Standard message. These fields can be used to personalize the message, apply conditional formatting, or pick a specific message variant.
Prior to using the push activity, your mobile app needs to be configured along with Campaign Standard to send push notifications. Use this article to take the necessary implementation steps for mobile.
First, you need to choose a mobile app from the drop-down list and a transactional message. See this page.
Two categories are available: Target and Personalization Data.
This category is only visible if you select an event message. For profile messages, the Target fields are automatically retrieved by the system using the reconciliation performed by Adobe Campaign Standard.
In this section, you need to define the Push platform. The drop-down list allows you to select Apple Push Notification Server (iOS) or Firebase Cloud Messaging (Android). You can alternatively select a specific field from an event or a data source, or define an advanced expression.
You also need to define the Registration Token. The expression depends on how the token is defined in the event payload or in other Journey Orchestration information. It can be a simple field or a more complex expression in case the token is defined in a collection for instance:
You cannot pass a collection in personalization data. If the transactional push expects collections, it will not work. Also note that the personalization data has an expected format (example: string, decimal, etc.). You must be careful to respect these expected formats.
These are the fields expected by the transactional template used in your Adobe Campaign Standard message. These fields can be used to personalize your message, apply conditional formatting, or pick a specific message variant.