Journey Optimizer release cycle releases

Adobe Journey Optimizer is updated regularly to deliver new capabilities, improvements, and fixes. This page explains how the release cycle works and what each release phase means, so you can easily understand when features become available for your organization.

Continuous delivery model continuous-delivery-model

Adobe Journey Optimizer operates on a continuous delivery model, enabling a scalable, phased approach to feature deployment. This model allows Adobe to deliver innovation faster and ensure ongoing stability and performance during rollout.

NOTE
Because Adobe Journey Optimizer uses continuous delivery, new capabilities may appear progressively across organizations or regions.

As part of this model:

  • New functionality and improvements are deployed to production as soon as they are ready.

  • The Release Notes are updated between monthly releases with a Latest updates section, which announces new capabilities and improvements as they are being rolled out—so you stay informed in real time.

Release timing and cadence release-timing

Adobe Journey Optimizer typically follows a monthly release cadence, with deployments usually taking place during the last week of each month. Monthly release notes and related documentation are published on Tuesdays of the release week. Pre-release notes are published on Fridays before the release week.

TIP
At the end of each quarter, releases can be anticipated and rolled out up to two weeks before the end of the month to align with quarterly schedules or dependent product releases.

While the monthly release introduces the main set of new capabilities and fixes, the continuous delivery approach allows additional updates to be deployed between cycles when ready. Release notes are then updated accordingly in the Latest updates section, and the availability date is mentioned. All changes released during the month are consolidated in the monthly release notes at the release date.

Release paths release-paths

Features in Journey Optimizer follow different release paths depending on their complexity, dependencies, and scope. The platform uses several availability labels (Beta, Limited Availability, General Availability), but not every feature passes through all of them.

Common release paths include:

  • Direct to GA — Some new capabilities and improvements go straight to General Availability (GA).
  • LA → GA — Some features are first available to a limited audience (Limited Availability) before general rollout.
  • Beta → LA → GA — Larger or experimental capabilities progress through all phases for testing and validation.
  • Beta → GA — Certain stable Beta features can move directly to GA, without an intermediate LA phase.
TIP
If you’re interested in early access to features in Beta or Limited Availability, contact your Adobe representative to discuss participation options.

Availability labels availability-labels

Label
Purpose
Availability
Key Notes
Beta
Early testing and feedback collection.
Restricted to selected customers or organizations participating in Adobe’s Beta program.
- Not intended for production use.
- Functionality or design may change before GA.
- Feedback helps refine the final implementation.
Limited Availability (LA)
Controlled rollout for validation and monitoring.
Enabled only for selected customers or environments (for example, development sandboxes).
- Production-ready and fully supported.
- Used to validate performance and scalability before general release.
- Access requires Adobe approval.
General Availability (GA)
Broad release of fully supported functionality.
Enabled by default for all eligible organizations.
- Production-ready and fully supported.
- Licensing or entitlements may apply.
- May roll out progressively across regions.

Rollout and availability rollout

Even after a GA announcement, rollout may occur gradually across organizations or regions. If a new capability does not appear immediately in your environment, it will typically be available within a few days after release.

This gradual rollout helps Adobe monitor stability, performance, and user experience before completing deployment.

Staying informed staying-informed

To stay up to date:

  • Review the latest release notes for new and updated capabilities.
  • Check the Latest updates section between monthly releases for real-time deployments.
  • Monitor Pre-Release Notes (when available) for a preview of upcoming features.
  • Contact your Adobe representative for Beta or Limited Availability access or entitlement information.

You can subscribe to email and in-product alerts for Journey Optimizer product releases. To subscribe:

  1. Navigate to Adobe Experience Cloud Preferences
  2. Under Notifications, find Journey Optimizer
  3. Enable New releases In-app and email notifications

{width="70%"}

Frequently Asked Questions faq

You will find below Frequently Asked Questions about Adobe Journey Optimizer release cycle.

Need more details? Use the feedback options at the bottom of this page to raise your question, or connect with Adobe Journey Optimizer community.

When are Adobe Journey Optimizer releases scheduled?
Adobe Journey Optimizer typically releases updates during the last week of each month. At the end of each quarter, the release may be advanced by up to two weeks to align with cross-solution or platform-wide updates.
Why don't I see a new feature immediately after it's announced?
Some GA features are rolled out progressively to ensure platform stability and performance. If you don’t see a feature right away, it will appear once deployment is complete for your region or organization.
What's the difference between Beta, Limited Availability, and GA?
  • Beta: Early testing phase, limited access, feedback-based.
  • Limited Availability (LA): Controlled rollout for final validation.
  • General Availability (GA): Full release for all entitled customers.
Do all features go through Beta and Limited Availability?
No. Some features are released directly to GA or only to LA, depending on their nature and readiness.The release path is tailored to each capability to balance agility, quality, and stability.
How can I participate in Beta or Limited Availability programs?
Access is by invitation or request through your Adobe representative. Participation helps shape feature design and ensures your use cases are considered in the final release.
How often are the release notes updated?
Release notes are continuously updated. Beyond monthly releases, the Latest updates section is refreshed whenever new features or improvements are pushed to production.
recommendation-more-help
b22c9c5d-9208-48f4-b874-1cefb8df4d76