Using Adobe Campaign Standard

If you have Adobe Campaign Standard, the following out-of-the-box action activities are available: Email, Push and SMS.

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.

You can use an event (also known as real-time) or profile transactional messaging template.

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.

Email and SMS:anchor-section_asc_51g_nhb:

For Email and SMS, the parameters are identical.

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.

Address

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.

Personalization Data

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.

Push:anchor-section_im3_hvf_nhb:

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.

Target

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:

@{Event_push._experience.campaign.message.profileSnapshot.pushNotificationTokens.first().token}

Personalization Data

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.