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

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.

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. 

Hi Suhai, 

Please note that the ACO orchestration canvas can only access data available in the relational store, whereas datasets reside in the Data Lake and are not accessible in real time within the ACO wf canvas.

Regarding Lee’s reference to temporary tables in the demo:

• Temporary tables are used within workflows to store intermediate data across transitions between nodes
• This data is available only during workflow execution and can be previewed while the workflow runs
• Once the workflow execution ends, the temporary data is not persisted

In AJO/AEP, everything revolves around the profile schema , where as in ACO one can define appropriate schemas to support business logic and these can be temporary tables for a particular usecase.

If you can share more details about your use case, we’d be happy to discuss and explore suitable approaches.

Regards,

--Chakri (ACO PM).