Post-session discussion: Experience League LIVE - Get to Know Campaign Orchestration in Adobe Journey Optimizer | Community
Skip to main content
HausmannS
Adobe Employee
Adobe Employee
March 12, 2026

Post-session discussion: Experience League LIVE - Get to Know Campaign Orchestration in Adobe Journey Optimizer

  • March 12, 2026
  • 2 replies
  • 22 views

Welcome! 👋
This Community thread is a space for everyone who watched (or is watching) this Experience League LIVE episode to connect, ask questions, and keep the conversation going. Share your takeaways, dive deeper into topics from the session, and help each other with real‑world tips and use cases. The Adobe team will be keeping an eye on the discussion and jumping in where helpful—so don’t be shy!

    2 replies

    HausmannS
    Adobe Employee
    HausmannSAdobe EmployeeAuthor
    Adobe Employee
    March 12, 2026

    We had some open questions from the show: 

    Does the TTL apply to record data as well of the system dataset? Since the TTL is for event data.

    Adobe Employee
    March 12, 2026

    There are two types of TTLs:

    Profile TTL:
    This applies only to time-series datasets (such as event data) and not to record-type datasets like entity or lookup datasets. Therefore, it does not apply to record (relational) data used in AJO Orchestrated Campaigns.

    Data Lake TTL:
    This is applicable to the AJO system out of the box (OOTB). Since some AJO tracking and feedback datasets are also used in AJO Orchestrated Campaigns, they will be affected. The default TTL for these datasets is 13 months.

    HausmannS
    Adobe Employee
    HausmannSAdobe EmployeeAuthor
    Adobe Employee
    March 12, 2026

    Questions regarding Lee’s demo:

    • For the series... are you using multiple email actions in the same orchestrated campaign?
    • For the email action content, were you using a combination of PQL for personalization and conditional content?
    • The example earlier was for customer with multiple mortgages, i suspect the relational schema might be used to loop the multiple mortgage products in one email.
    Adobe Employee
    March 12, 2026

    1. Are we using multiple email actions within the same orchestrated campaign?
    Yes, we do support and commonly use multiple email actions within a single orchestrated campaign. This is typically done when:

    • Different audience branches require distinct messaging.

    • There are sequential follow-ups (e.g., reminder emails).

    • Messaging varies based on decision splits within the workflow.

    However, if the goal is to deliver multiple pieces of dynamic content within a single communication touchpoint, we generally prefer handling that within one email action using personalization and conditional logic rather than creating multiple email actions unnecessarily.

     

    2. For the email action content, are we using a combination of PQL for personalization and conditional content?
    Yes. In orchestrated campaigns, it’s common to use:

    • PQL (Profile Query Language) for attribute-level personalization (e.g., name, product type, status) if you want to use profile XDM. Else, if you use relational schema elements, it is a simple (QL) editor used for conditional content. 

    • Conditional content blocks to dynamically render sections of the email based on profile or contextual and relational data based conditions.

    3. For the example of a customer with multiple mortgages — is a relational schema used to loop through multiple mortgage products in one email?
    Yes, that would typically be the case behind the scene.