OCM: Allow AJO Journeys to Directly Consume Relational Tables Description

Enable Adobe Journey Optimizer (AJO) Journeys to natively query and consume data residing in relational tables.

Why is this feature important to you Siloing relational data strictly to Orchestrated Campaigns creates a disjointed architecture. Real-time journeys often need contextual data (like store inventory or loyalty tier lookups) that is best suited for relational storage.

How would you like the feature to work Allow AJO journey conditions and personalization syntax to securely reference and pull data from relational schemas linked to the primary profile.

Current Behaviour Relational tables are designed for OC only and cannot be directly consumed by AJO Journeys