Skip to main content
ShrutiJa17
Level 1
July 24, 2026
Question

Subject: Can AJO Decisioning generate offers without pulling data from a 3rd party source in AEP?

  • July 24, 2026
  • 3 replies
  • 43 views

Hi all,

I'm trying to understand a specific aspect of AJO's decisioning capability. Does AJO's decisioning engine have the ability to generate/select offers purely on its own — using only internal AJO/AEP configuration (like offer eligibility rules, priorities, and constraints) — without needing to pull any profile or event data from an external/3rd party source into AEP?

    3 replies

    SatheeskannaK
    Adobe Champion, Community Advisor, UG Leader
    SatheeskannaKAdobe Champion, Community Advisor, UG Leader
    Adobe Champion, Community Advisor, UG Leader
    July 24, 2026

    ​@ShrutiJa17 Yes, that’s fully supported, and it’s actually one of the core use cases for AJO offer decisioning.

    • The decision engine can select offers using purely self-contained configurations.
    • Eligibility and decision rules can be built entirely on static logic or constraints that do not reference any profile attributes.
    • Priority values can be set per offer to break ties when multiple offers qualify.
    • Capping is tracked internally by the decision engine by counting presentations and impressions independently.
    • Configurations are assembled into a decision policy for the engine to pick the best eligible offer at runtime.
    • This self-contained pattern is valid and supported across journeys, campaigns, etc.
    • External and profile data, such as AEP profile attributes, audiences, or experience events, are completely optional for personalization.
    • Joining external AEP datasets for dynamic rules or ranking formulas is an optional enhancement rather than a prerequisite.
    • Profile, event, and third-party data enrich decisioning but are not dependencies for the decisioning engine to operate.

    https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/experience-decisioning/experience-decisioning-landing-page

    Thanks, Sathees
    ShrutiJa17Author
    Level 1
    September 10, 2026

    Hi @SatheeskannaK,

    Thanks for your reply. To clarify my question: by dynamic offer generation, I mean can the offer attribute values configured under Offers (Decision Management) in AJO be generated dynamically by the offer decision engine at runtime, without a developer having to manually set them up beforehand?

    Please let me know if this is possible using Offer Decisioning, or if there is another approach within Decision Management.

    I have attached a screenshot as an example of the values I am referring to get generated dynamically.

     

     

    SatheeskannaK
    Adobe Champion, Community Advisor, UG Leader
    SatheeskannaKAdobe Champion, Community Advisor, UG Leader
    Adobe Champion, Community Advisor, UG Leader
    September 10, 2026

    ​@ShrutiJa17 Got it. There are a few ways to do it.

    1. Bulk Populating via the Offer Library API (Traditional Approach)

    • What it does: Automates individual offer creation and attribute tracking by using scripts to push data into the central system rather than typing attributes inside the UI manually.
    • How it handles attributes: Attributes are mapped as key-value pairs inside a characteristics object under the standard _experience or custom tracking namespace.
    • Best use case: Ideal for bulk uploading large batches of hundreds of traditional promotions or content definitions directly from an external database or spreadsheet.
    • Documentation: Refer to the AJO Create a Personalized Offer API Guide and the broader Decision Management API Developer Guide.

    2. Passing Real-Time Contextual Attributes (In-Flight Data)

    • What it does: Pushes situational variables to the decision engine at the moment the offer is being requested.
    • How it handles attributes: Variables are not permanently stored on the offer record. Instead, they are passed temporarily in the API request body to evaluate eligibility rules or adjust scores instantly.
    • Best use case: High-velocity or hyper-local campaigns can track highly dynamic variables such as real-time weather conditions, fluctuating stock levels, device types, or live application shopping cart totals.
    • Documentation: See the AJO Hub Decisioning API Context Data Guide or the AJO Edge Decisioning API Context Data Guide for XDM-compliant mobile/web architectures.

    3. Dynamic Catalogs using Experience Decisioning (Modern Schema-Based Framework)

    • What it does: Migrates your technical strategy away from rigid key-value strings into an organized, unified catalog model where offers are treated as Decision Items.
    • How it handles attributes: In Experience Decisioning (AJO's modernized framework for managing scalable offers), traditional standalone offers are evolved into Decision Items. Instead of typing unstructured key-value strings into an offer record, offer attributes are directly managed via an AEP Schema tied to your central Item Catalog
    • Best use case: Enterprise systems syncing their dynamic external content repositories or Product Information Management (PIM) tables to build automated offer collections effortlessly.
    • Documentation: Review the AJO Decision Items Overview alongside the AJO Experience Decisioning API Reference Guide.

     

    Thanks, Sathees
    Terms & ConditionsAccessibility statement

    Loading footer...