AJO - Decision Management vs Experience Decisioning | Community
Skip to main content
A
AKP3
Level 3
April 22, 2024
Solved

AJO - Decision Management vs Experience Decisioning

  • April 22, 2024
  • 2 replies
  • 1404 views

Hi,

 

Can you help understand the key difference between AJO Decision Management and Experience Decisioning  feature. It looks like using both you can manage offers. Is the Experience Decisioning only for Code based Experience?

 

 

    Best answer by Rehan_Shirwani

    This post focuses on the naming conventions/changes (rather than functionality) to avoid confusions:

    Just a heads up about some (fairly recent) changes in naming (in both the menu interface on the left of the application, and also the documentation; latter may lead to broken links).

    The traditional/legacy AJO 'Offer Decisioning' is now called 'Decision Management':

    https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/offer-decisioning/get-started-decision/get-started-decision-landing-page

    (although I see OP has already taken this into account)
    It was also earlier known as ODE (Offer Decisioning Engine, ODS (Offer Decisioning System I believe?), and ‘Hub’ decisioning, in case you see those terms mentioned in earlier documentations.
     


    The newer 'Experience Decisioning' is now called just 'Decisioning' in the menu (as this is the main decisioning engine moving forward):

    https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/gs-experience-decisioning
    This is often abbreviated to EXD (Experience Decisioning) too.

    As of writing (2026), the menu sections are named as follows:

     

     

    2 replies

    ezhil_raja
    ezhil_raja
    Level 4
    June 9, 2025

    Experience decisioning is Adobe's next-generation decision framework and is a broader concept that kind of encompasses offer decisioning as well within the larger context of personalized experiences. You can try content experiments before targeting, and there is decision policy and strategy sequence that can be configured to rank and deliver real time offers based on audience, context data and decision rules.

     

    As of now experience decisioning decision policies are available for use in code-based experience campaigns only.

      R
      Adobe Employee
      Rehan_ShirwaniAdobe EmployeeAccepted solution
      Adobe Employee
      November 21, 2025

      This post focuses on the naming conventions/changes (rather than functionality) to avoid confusions:

      Just a heads up about some (fairly recent) changes in naming (in both the menu interface on the left of the application, and also the documentation; latter may lead to broken links).

      The traditional/legacy AJO 'Offer Decisioning' is now called 'Decision Management':

      https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/offer-decisioning/get-started-decision/get-started-decision-landing-page

      (although I see OP has already taken this into account)
      It was also earlier known as ODE (Offer Decisioning Engine, ODS (Offer Decisioning System I believe?), and ‘Hub’ decisioning, in case you see those terms mentioned in earlier documentations.
       


      The newer 'Experience Decisioning' is now called just 'Decisioning' in the menu (as this is the main decisioning engine moving forward):

      https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/gs-experience-decisioning
      This is often abbreviated to EXD (Experience Decisioning) too.

      As of writing (2026), the menu sections are named as follows:

       

       

        Terms & ConditionsAccessibility statement

        Loading footer...