Release Notes

This page lists all the new features and improvements for Journey Optimizer. You can also consult the latest documentation updates page for more changes.

Adobe Journey Optimizer is built natively on Adobe Experience Platform and inherits from its latest innovations and improvements. Learn more about these changes in Adobe Experience Platform Release Notes.

Newsletter Sign up for the Adobe Journey Optimizer quarterly newsletter today, and receive the latest product updates, exciting stories, use cases, tips and more delivered directly to your inbox every quarter.

September 2022 Release

New capabilities

API-triggered campaigns

In addition to existing scheduled campaigns, you can now create API-triggered campaigns in Journey Optimizer and invoke them from an external system using APIs.

This allows you to cover various operational and transactional messaging needs like password resets, OTP token, among others.

For more information, refer to the detailed documentation.

Data Access Control

Through attribute-based access control, administrators can control access to specific objects based on certain attributes. These attributes can be metadata added to an object, such as labels. Starting this release, administrators can also define user roles that have access to only specific fields and/or objects, and data that correspond to those fields and/or objects.

The use of Attribute-based access control is currently restricted to selected customers, and will be deployed to all environments in a future release.

For more information, refer to the detailed documentation.

Data Governance and Privacy

With its Data Usage Labelling and Enforcement (DULE) governance framework, Journey Optimizer can now leverage Adobe Experience Platform governance policies to prevent sensitive fields from being exported to third-party systems through custom actions. If the system identifies a restricted field in the custom action parameters, an error is displayed preventing you from publishing the journey.

The use of Data Usage Labelling and Enforcement (DULE) is currently restricted to selected customers, and will be deployed to all environments in a future release.

For more information, refer to the detailed documentation.

Automated Consent Enforcement (Consent Policies)

Adobe Experience Platform allows you to easily adopt and enforce marketing policies to respect the consent preferences of your customers. Consent policies are defined in Adobe Experience Platform. In Journey Optimizer, you can apply these consent policies to your custom actions. For example you can define consent policies to exclude customers who have not consented to receive email, push or SMS communication.

Automated Consent Enforcement is currently only available for organizations that have purchased the Healthcare Shield add-on offering.

For more information, refer to the detailed documentation.

Permission Management

Journey Optimizer supports defining user roles and access policies to manage permissions for features and objects. Through Adobe Experience Cloud Permissions, you can create and manage roles, as well as assign the desired resource permissions for these roles. Permissions also allow you to manage the labels, sandboxes, and users associated with a specific role.

The use of Permissions is currently restricted to selected customers, and will be deployed to all environments in a future release.

For more information, refer to the detailed documentation.

Alerting and Monitoring

As a Journey Optimizer user, you can now access system alerts through the user interface to get notified when journeys don't work as expected. You can view the available alerts and subscribe to them. The first alert available with this release will warn you if a Read Segment activity has not processed any profile during the defined time frame. More will come now that this workflow is unlocked.

For more information, refer to the detailed documentation.



  • The Entity Dataset is now available as an out-of-the-box dataset in Adobe Journey Optimizer. This lookup dataset includes meta data to enrich the tracking and feedback datasets information. This will help you improve your reports and queries with more comprehensible data. Learn more
  • A new guardrail has been added to unitary journeys (starting with an event or a segment qualification) to prevent journeys from being erroneously triggered multiple times for the same event. Profile re-entrance will now be temporally blocked by default for 5 minutes. Learn more


  • When enabling or disabling the allowed list, a new warning now displays to detail the impacts of each action. Learn more
  • The user interface for creating channel surfaces, creating IP pools, managing the suppression list and the allowed list, and configuring the SMS channel has been updated.

Audit controls

  • With Journey Optimizer, you can identify actions performed by users in the system on various services and capabilities like campaigns, journeys, messages, landing pages etc. Audit log resources now include changes on various other actions, and are recorded automatically as the activity occurs. Learn more in this page.

Archiving support

  • The new Entity Dataset includes a Template field which enables you to export the format ad structure of the sent messages on all channels for archiving purpose. Learn more

Landing pages

  • You can now use contextual data coming from another page within the same landing page. For example, if you link a checkbox to a subscription list on the primary landing page, you can use that subscription list on the “thank you” subpage. Learn more

  • When configuring the primary page, you can now create additional data to enable storing information when the landing page is being submitted. Learn more

Other changes

  • Journey Burst Mode has been replaced by Campaign Rapid delivery mode. Learn more
  • To improve performance, Experience event field groups can no longer be used in journeys starting with a Read segment, a Segment qualification or a business event activity. This change only applies to new journeys. Existing ones will keep the current behaviour. Learn more
  • The 1 hour limitation for scheduled read segment journeys has been removed. These journeys can now be executed with no delay.

On this page