Pre-release notes e-release-notes

Adobe Journey Optimizer continuously delivers new features, enhancements to existing features, and bug fixes. All changes are consolidated at the end of each month in the release notes.

July '26 pre-release notes july-26-rn

The pre-release notes below are subject to change without prior notice until the release availability date. Links, screens and updated documentation are published once changes are live in production. While most changes are delivered on the release date, a few may roll out later.

See also Adobe Experience Platform Pre-release notes.

Release date: July 28, 2026

Loyalty july-26-loyalty

Journey Optimizer introduces Loyalty, a new capability in this release.

Loyalty Challenges

Loyalty Challenges turn loyalty initiatives into engaging, gamified experiences that motivate customers to take valuable actions, such as making purchases, writing reviews, engaging on social media, or referring friends.

Administrators can use the Loyalty admin menu to connect Journey Optimizer with your loyalty ecosystem, including reward fulfillment APIs, event definitions, product inventory, exclusions, and identity settings. Marketers can then design standard, streak, or sequential challenges, define tasks and rewards, deliver branded content cards and messages, and monitor performance with built-in reporting dashboards. Journey Optimizer generates the journeys that orchestrate each challenge in the background, so teams can focus on the customer experience and business goals.

Jira: DOCAC-14019

Onboarding july-26-onboarding

Journey Optimizer introduces the Onboarding Hub, a new capability in this release.

Onboarding Hub

Transitioning to Adobe Journey Optimizer from another marketing platform is now faster and simpler. The new onboarding hub features a migration workspace that lets you import your existing email content and journeys automatically, saving you from having to rebuild them from scratch.

This capability is only available for a set of organizations (Limited Availability). To gain access, contact your Adobe representative.

Jira: DOCAC-15180

Journeys july-26-journeys

The following capabilities and improvements have been added to journeys in this release.

Journey Arbitration - Formulas

You can now use formulas to automatically prioritize and arbitrate journeys based on customer profile attributes and contextual factors, ensuring customers enter the most relevant journeys.

Previously released in Limited Availability, this capability is now available to all customers (General Availability).

Jira: DOCAC-14719

Journey Arbitration - AI Models

You can now use AI models in your ranking formulas to automatically boost journey priority scores based on customer profile attributes and contextual factors, ensuring customers enter the most relevant journeys.

Previously released in Limited Availability, this capability is now available to all customers (General Availability).

Jira: DOCAC-14713

  • Document support of external audiences (comma-separated values and Federated Audience Composition) in Journey Simulation - Journey Simulation now supports External Audiences. When simulating journeys targeting comma-separated values or Federated Audience Composition audiences, you can mock enrichment attributes from those audiences directly through the UI form or a JSON import. The UI dynamically displays only the specific enrichment attributes used in your journey logic, enabling precise validation of decision branches and personalization rules prior to going live. (DOCAC-15074)

  • Start and end dates in the journey header - When start and/or end dates are configured on a live journey, they are now surfaced in the journey header next to the live status badge. The displayed label adapts based on whether each date is upcoming or has already passed. (DOCAC-14702)

Orchestrated campaigns july-26-oc

The following capabilities and improvements have been added to orchestrated campaigns in this release.

Quiet Hours support for orchestrated campaigns

You can now apply quiet hours to Orchestrated campaigns. Quiet hours let you define time-based exclusions to prevent messages from being sent during specific periods, helping you respect customer preferences and compliance requirements across campaign orchestration use cases.

Jira: DOCAC-14054

Action campaigns inbound channels simulation mode

You can now simulate inbound channel actions in Action campaigns before going live. Use simulation mode to test your configuration with simulated users and preview the rendered experience, including a generated URL and QR code, so you can validate rules, decisioning, and content rendering end-to-end.

This capability is only available for a set of organizations (Limited Availability). To gain access, contact your Adobe representative.

Jira: DOCAC-15166

  • Ability to Manage Profile Target Dimensions - You can now delete a Profile Target Dimension or edit and swap its configured identity namespace, providing greater control and flexibility over your data setups. (DOCAC-15018)

  • View Orchestrated Campaign Transitions permission - Added a new View Orchestrated Campaign Transitions permission to replace the legacy View File in Orchestrated Campaigns option. This change allows you to hide preview results within campaign transitions to support personally identifiable information compliance. (DOCAC-14924)

  • Support for Line - You can now add LINE actions directly into your Orchestrated campaigns. This new activity allows you to build and deliver highly personalized content, including text, stickers, images, videos, location data, and rich Flex Messages, to engage your customers seamlessly on the LINE platform. This capability is only available for a set of organizations (Limited Availability). To gain access, contact your Adobe representative. (DOCAC-14905)

  • New Orchestrated campaigns public APIs - New API specifications are now available for Orchestrated campaigns. These APIs allow you to programmatically create, manage, and trigger orchestrated campaigns, enabling deeper integration with external systems and automation pipelines. (DOCAC-14308)

  • Personalize email sender details per recipient and campaign - Orchestrated campaigns now support personalization of email header fields, including From name, From address, and Reply-To, using profile attributes or relational data. This allows sender details to reflect the relevant advisor, location, or branch for each recipient, rather than routing all sends through a single corporate address. Header values can be set at the channel level and overridden per campaign using contextual data for more precise control. (DOCAC-13761)

  • Target dimension simplification in Orchestrated campaigns - The active targeting dimension is now shown on the workflow canvas, so you can see which dimension is used by a channel activity. The multi-entity segmentation flow is simpler as you no longer need a separate “Change dimension” activity. Moreover, you can now choose explicitly whether messages are sent at the profile level or at a secondary dimension level. (DOCAC-13554)

Campaigns july-26-campaigns

The following capabilities and improvements have been added to campaigns in this release.

Personalized PDF attachment for transactional messaging in API Triggered campaigns

You can now attach up to five dynamic, personalized PDFs per email in API-triggered transactional campaigns by passing the file locations in the API payload. This enables industries like aviation to send boarding passes or travel confirmations, financial services to deliver individualized invoices or statements, and retail to include order receipts or return labels — each document tailored to the recipient at send time.

Personalized and static PDF attachments share the same quota; exceeding the fair usage limit requires the PDF attachment add-on. This feature is not available in journey or action campaigns.

Jira: DOCAC-15186

  • Folders for Campaigns - You can now organize your campaigns into folders to improve navigation and management in the interface. (DOCAC-15098)

  • Override the default execution field in campaigns - Previously available at the journey level, you can now override the default execution field set globally for your Email, SMS and WhatsApp deliveries in the campaign parameters. (DOCAC-14718)

  • Brand alignment score in Campaign dashboard - You can now assess your brand alignment score directly within your Campaign dashboard to ensure content stays on-brand. This allows you to verify guidelines at a glance without having to open the content designer. (DOCAC-14516)

Decisioning july-26-decisioning

The following improvements have been added to Decisioning in this release.

  • Decisioning rules and ranking formulas creation from natural language expression - You can now describe the Decisioning rule or ranking formula you want to create in plain language and let the AI Assistant generate it for you. This capability is available to customers with access to Adobe AI capabilities. (DOCAC-15231)

  • Decisioning rules and ranking formulas simulation - You can now simulate your Decisioning rules and ranking formulas directly from the rule or formula editor. Add manual test variants or generate them using AI, then run the expression against your test data to validate eligibility and review ranked results, all before deploying to production. Variants generation is available to customers with access to Adobe AI capabilities. (DOCAC-15227)

  • Dynamic offer attributes - Decision item custom attributes can now be personalized at delivery time using profile, contextual, and audience data. This removes the need to maintain duplicate offers for minor content variations, allowing marketers to manage fewer, more flexible decision items. (DOCAC-14899)

Content management july-26-content

The following improvements have been added to content management in this release.

  • Expression fragments support in <head> of email templates - Expression fragments can now be used in the <head> of email templates. This allows you to centralize styling or any custom code in a single fragment and reuse it across multiple templates. When a fragment is updated and republished, all emails built from templates referencing it automatically inherit the latest code — eliminating the need to manually update each email individually. (DOCAC-15257)

  • “AI Assistant” renamed to “Generate content” - AI Assistant has been renamed to Generate Content throughout Adobe Journey Optimizer. This update is limited to naming and terminology; no functional changes have been introduced. Navigation labels, buttons, menus, and dialogs for content generation, image generation, personalization expressions, and content experimentation have been renamed from “AI Assistant” to “Generate Content.” (DOCAC-15230)

  • Generate content with AEM Asset Essentials - Generated content now automatically fetches brand-approved images directly from your Adobe Experience Manager Assets when generating Emails, Web pages, and Push notifications. This eliminates the need to manually search the Assets or rely on generic AI fallbacks, ensuring every visual is perfectly accurate and brand-compliant. (DOCAC-14761)

Email channel july-26-email

The following capabilities have been added to the email channel in this release.

Modules in the Email Designer

The Email Designer now includes a library of ready-to-use layout modules — such as headers, product cards, information blocks, and footers — that you can drag and drop directly into your email canvas. Each module comes pre-configured with editable properties (image, title, text, button, links) and can be fully customized through the WYSIWYG interface, speeding up email creation without requiring you to build structures from scratch.

Jira: DOCAC-14877

Personalization july-26-personalization

The following improvements have been added to personalization in this release.

  • Manage domains for complete/base URL personalization - You can now create and manage approved domains for complete and base URL personalization directly from the Administration settings in Adobe Journey Optimizer, without having to contact Adobe Support. (DOCAC-15187)

  • New helper functions in personalization expressions - New helper functions are now available in personalization expressions:

    • appendQueryParams: Appends a query parameter to a URL, or replaces it if the key already exists.
    • dateBetween: Checks whether a date falls within a start and end date range (inclusive).
    • equalsAnyIgnoreCase: Returns true when a string matches any provided value, ignoring case.
    • getUrlFragment: Extracts the fragment portion of a URL (the part after #).
    • join: Concatenates array elements into a single string using a separator.
    • decode64: Decodes a Base64-encoded string. If the input is not valid Base64, the original input string is returned unchanged.

    The concat function has also been enhanced and now supports two or more arguments.

    In addition, the following Template Migration Functions are now available to assist with migrating existing templates to Journey Optimizer:

    • ampCompare: Compares two values using the specified comparison operator.
    • ampSubstr: Returns a portion of a string between the specified start and end indices.
    • compareTo: Compares two strings lexicographically.

    (DOCAC-15099)

Channels july-26-channels

The following capabilities and improvements have been added to channels in this release.

Custom outbound channel

Journey Optimizer now introduces Custom channels, a new capability that lets administrators bring any outbound HTTP-based messaging channel — such as WeChat, Kakao Talk, Messenger, or a proprietary provider — directly into Journey Optimizer through a no-code Channel Builder. Once configured, custom channels are available across Campaigns, Journeys, and Orchestrated Campaigns, with the same full set of capabilities as native channels: personalization with the expression editor, content experimentation, preview and proof, out-of-the-box reporting, and consent and governance enforcement. This fills the gap previously addressed by Custom Actions, which were limited to Journeys and lacked dedicated content authoring.

This capability is only available for a set of organizations (Limited Availability). To gain access, contact your Adobe representative.

Jira: DOCAC-11381

  • WhatsApp Channel: Support WhatsApp Flow templates - You can now send WhatsApp Flow templates in Adobe Journey Optimizer to deliver interactive multi-screen experiences like surveys and lead capture. Responses are captured upon submission and stored as raw JSON payloads in the new Journey Optimizer Channel Tracking Event Dataset. (DOCAC-15223)

  • Performance Add-on for throughput - Push - A new high throughput transactional messaging mode is available in API-triggered campaigns. This mode is designed for large-scale, real-time transactional messaging and supports up to 5,000 transactions per second with higher availability. Previously only available for the email channel, this capability is now also available for the push channel, for organizations that have purchased the Adobe High Throughput Transactional Messaging add-on offering. Contact your Adobe representative for more details. (DOCAC-14717)

Administration july-26-administration

The following capabilities have been added to administration in this release.

Web Application Firewall IP whitelisting

Adobe Journey Optimizer now supports Web Application Firewall IP whitelisting for landing pages, enabling organizations to enforce that all incoming requests are routed exclusively through their configured Web Application Firewall infrastructure. With this enhancement, customers can configure Journey Optimizer to reject any direct requests that bypass the Web Application Firewall layer, ensuring that security policies defined in tools such as Imperva are consistently applied.

This capability strengthens the security posture for enterprises with strict network access requirements, giving them full control over the traffic flow to their Journey Optimizer-hosted landing pages.

Jira: DOCAC-14814

recommendation-more-help
journey-optimizer-help