Visibility Limitations of Map and Array Attributes in Orchestrated Campaign
Hi Team,
I have a question regarding the usage and limitations of array-type and map-type attributes in Orchestrated Campaigns (Adobe Journey Optimizer).
Context :
We are working with a Profile-enabled dataset that contains:
Array fields (e.g., list of addons, purchased items)
Map attributes (e.g., key-value structures like perDay)
Data is successfully ingested into AEP, and values are visible in Profile Viewer.
Observed behavior
- Scalar attributes (string/number/boolean) :These are visible in Read Audience activity under Add Attributes section
- Array attributes and Map attributes: These are not visible in Read Audience activity under Add Attributes section
Questions
- Map Attribute Support and Array usage:Are Map-type attributes and array objects are supported in Orchestrated Campaign?If not, is there a recommended pattern to expose/use them?