Decisioning | Community
Skip to main content
M
MarzenaRa
Level 2
February 12, 2026
Question

Decisioning

  • February 12, 2026
  • 1 reply
  • 21 views

Hi Adobe Community,

 

I’d like to ask for clarification regarding the new Decisioning functionality in Adobe Journey Optimizer:

 1. Is this new Decisioning capability intended to replace the existing (legacy) Offer Decisioning feature?

- If yes, do you already have a timeline for when the old functionality will be deprecated or disabled?

 

2. Or is the new Decisioning module meant to be an additional capability that will coexist with the existing one?

 

3. In the new Decisioning,, where can I configure Placements for web banners? In the legacy version, placements were clearly defined, but I’m not able to locate this option in the new interface. Any guidance or documentation references would be greatly appreciated.

 

 

Thank you! 

    1 reply

    arpan-garg
    Community Advisor
    arpan-gargCommunity Advisor
    Community Advisor
    February 12, 2026

    Hi ​@MarzenaRa ! Happy to jump in here and help clear up some of the confusion. The shift between these two modules is definitely one of the bigger changes in AJO recently.

    To answer your questions:

    1. Is it replacing the existing functionality - Yes, that’s the long-term plan. Experience Decisioning (ExD) is the new architecture and is considered the "path forward" for all customers. Timeline : There isn’t a hard "off switch" date yet for the legacy version, so don’t panic. It’s more of a gradual transition where customers move at their own pace. That said, the roadmap for the old Offer Decisioning is now very small, while almost all new development and features are going into ExD. We had the similar discussion with Adobe recently on the same topic because some features are not available in ExD and Adobe gave us an assurance that the offer decisioning feature is going to stay.
    2. Coexistence - It’s a bit of both right now. They coexist so you don't have to migrate everything overnight, but they are technically different frameworks. The big shift is that ExD uses an XDM-based catalog. This is actually a huge plus because it lets you use much richer data types for your eligibility rules and ranking, rather than being stuck with the more limited options in the old version.
    3. Where are placement configured ?This is usually the biggest "where did it go?" moment for people. In the new ExD interface, you won’t find a "Placements" menu because the rendering is now decoupled from the offer itself.  The Change: Instead of defining the placement on the offer item, you now set the rendering details (like how it looks) within the activation object—basically, inside the specific Campaign or Journey you're building.

    Hope my reply helps.

     

    Thanks,

    Arpan

      M
      MarzenaRaAuthor
      Level 2
      February 12, 2026

      You mentioned that placements no longer exist in the new Experience Decisioning interface and that rendering details now live inside the activation object (Campaign or Journey).

      My question is:
      What if I do not want to use Campaigns or Journeys to control offer delivery?

      My scenario is pure inbound:

      • My application calls AJO via API
      • It asks for the next‑best offer for a specific location (e.g., homepage banner, product banner, etc.)
      • The application renders the result on its own

      In the old Offer Decisioning, I could define multiple Placements for such inbound use cases.
      In the new Experience Decisioning, without a placement menu and without Campaign/Journey usage:

      How should I separate different inbound “locations” (e.g., homepage banner vs. account banner)?

      • Should I create multiple Collection  (one per location)?
      • Or is there another recommended pattern for inbound scenarios now that Placements are gone?

      I want to ensure my inbound application can still request and retrieve the correct offer per “placement-like” context, even if I am not using Campaigns or Journeys.

      Thanks in advance for the clarification!

      arpan-garg
      Community Advisor
      arpan-gargCommunity Advisor
      Community Advisor
      February 13, 2026

      Hi ​@MarzenaRa  - Your questions are valid, i also had the same concerns when transitioning from legacy ODE to experience decisioning.

      In short , you need a campaign or a journey with code based experience to request offers from experience decisioning. We can’t just use an API like the previous legacy ODE where we pass the decision scope and fetch the offer.

      On your question regarding multiple locations, you need to create different surface configuration one for each location and then create a code based experience using the surfaces.

       

      Thanks,

      Arpan

        Terms & ConditionsAccessibility statement

        Loading footer...