Use the Action activity add-a-message-in-a-journey

Journey Optimizer comes with a new generic Action activity that allows to configure a single built-in channel action, and also multiple inbound activities.

The Action activity offers:

  • A simplified native action configuration within the journey canvas.
  • The capacity to create multi-action inbound action groups.
  • The ability to add optimization to any built-in channel action.

To add a built-in channel action to your journey, use the Action activity. This unified activity consolidates all channel actions (Email, Push, SMS, In-app, Web, Code-based experience, and Content Card) into a single activity type, replacing the previous individual channel activities.

IMPORTANT
All native channels being now accessible through the Action activity, legacy native channel activities will be deprecated with the March release. Existing journeys that include legacy actions will continue to function as is—no migration is required.

You can also set up custom actions to send your messages in Journey Optimizer. Learn more

Add a built-in channel action to a journey add-action

To add a built-in channel action to your journey using the Action activity, follow the steps below.

For more information on the channels available in journeys, refer to the table in this section: Channels in journeys & campaigns.

  1. Start your journey with an Event or a Read Audience activity.

  2. From the Actions section of the palette, drag and drop an Action activity into the canvas.

  3. Select the built-in channel activity you want to leverage in your journey.

    Action type dropdown showing channel action and custom action options

  4. Add a label to your action and select Configure action.

    Action activity configuration pane with label and description fields {width="80%"}

  5. You are directed to the Actions tab of the journey action configuration screen.

    Select the configuration to use for the selected channel.

    Actions tab in Administration menu showing custom and Adobe actions

  6. If you selected an inbound channel, you can add multiple actions. Learn more

  7. Configure your activity according to the selected channel. Detailed configuration guidelines are available in the links below.

    note note
    NOTE
    • Each inbound experience action comes with a 3-days Wait activity. Learn more

    • For emails and push notifications, you can enable Send-Time Optimization. Learn more

  8. Depending on the activity, you can display advanced parameters specific to the selected channel, and override some default values such as the execution address. Learn more

    note note
    NOTE
    If the advanced parameters are hidden, click the Show read-only fields button on top of the right pane.
  9. Use the Optimization section to run content experiments, leverage targeting rules, or use advanced combinations of both experimentation and targeting.

    These different options and the steps to follow are detailed in this section.

  10. Use the Languages section to create content in multiple languages within your journey action. To do so, click the Add languages button and select the desired Language settings.

    Detailed information on how to set up and use multilingual capabilities are available in this section.

Additional settings are available depending on the selected communication channel. Expand the sections below for more information.

Apply capping rules (Email, Push, SMS)

In the Business rules drop-down list, select a rule set to apply capping rules to your journey action.

Leveraging channel rule sets allows you to set frequency capping by communication type to prevent overloading customers with similar messages.

Learn how to work with rule sets

Track engagement (Email, SMS).

Use the Action tracking section to track how your recipients react to your email or SMS deliveries.

Tracking results are accessible from the journey report once the journey has been executed.

Learn more about journey reports

Enable Rapid delivery mode (Push).

Rapid delivery mode is a Journey Optimizer add-on that allows very fast push message sending in large volumes though campaigns.

Rapid delivery is used when delay in message delivery is business-critical, when you want to send an urgent push alert on mobile phones, for example a breaking news to users who have installed your news channel app.

Learn how to enable Rapid delivery mode for Push notifications on this page.

For more information on performances when using Rapid delivery mode, refer to Adobe Journey Optimizer product description.

Assign priority scores (Web, In-app, Code-based)

In the Conflict management section, you can assign a priority score to the journey action, allowing you to prioritize an inbound action when there are multiple journey actions or campaigns using the same channel configuration.

By default, the priority score for the action is inherited from the overall priority score for the journey.

Learn how to assign priority scores to channel actions

Set additional delivery rules (Content cards)

For content card journeys, you can enable additional delivery rules to choose the event(s) and criteria which trigger your message.

Learn how to create content cards

Define triggers (In-app)

For in-app messages, you can use the Edit triggers button to choose the event(s) and criteria which trigger your message.

Learn how to create an In-app message

Add multiple inbound actions multi-action

To simplify your journey orchestration, you can define several inbound actions inside a single journey action.

NOTE
This capacity is only available for inbound channels. Currently outbound channels such as Email are not supported.

This capacity enables you to deliver various Code-based experiences, In-app messages, Content Cards or Web actions to different locations at the same time, without the need to create multiple journey actions. It makes the deployment of your journey easier and allows for smoother reporting, with all the data consolidated into one single journey.

For example, you can send a code-based experience to multiple endpoints with slightly different contents. To do this, create multiple code-based actions within the same journey action, each with a different endpoint configuration.

To define several inbound actions in a single journey action node, follow the steps below.

  1. Start your journey with an Event or a Read Audience activity.

  2. From the Actions section of the palette, drag and drop an Action activity into the canvas.

  3. Select Multi action as the action type.

    Multi-action activity in journey palette under Orchestration

  4. Add a label if needed and select Configure action.

    Multi-action configuration pane with label and description fields {width="60%"}

  5. You are directed to the Actions tab of the journey action configuration screen.

    Multi-action configuration showing list of actions to execute {width="70%"}

  6. Select an inbound action (Code-based experience, In-app message, Content Card or Web) from the Actions section.

  7. Select the channel configuration and define a specific content for that action.

  8. Use the Add action button to select another inbound action from the drop-down list.

    Add action button to include additional actions in multi-action activity {width="80%"}

  9. Proceed similarly to add more actions. You can add up to 10 inbound actions in a journey action group.

Once the journey is live, all actions are activated simultaneously.

Update a live content update-live-content

You can update the content of a built-in channel action in a live journey.

Any changes made to the content are not reflected in the journey until you save the action’s properties. Learn more

To do this, open your live journey, select the channel activity and click Edit content.

Edit channel activity button in live journey

However, you cannot change the attributes used in personalization, whether they are profile attributes or contextual data (from event or journey properties).

  • If you modified contextual data, the following error message will be displayed: ERR_AUTHORING_JOURNEYVERSION_201

  • If you modified profile attributes, the following error message will be displayed: ERR_AUTHORING_JOURNEYVERSION_202

Note that for the In-app activity, any changes can be made to the content while the journey is live, but In-app triggers cannot be modified.

Send with custom actions recommendation

Instead of using the built-in message capabilities, you can use custom actions to configure connection of a third-party system to send messages or API calls.

recommendation-more-help
b22c9c5d-9208-48f4-b874-1cefb8df4d76