Skip to main content
Level 1
May 21, 2026 10:23 AM UTC
Question

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

  1. Scalar attributes (string/number/boolean) :These are visible in Read Audience activity under Add Attributes section
  1. Array attributes and Map attributes: These are not visible in Read Audience activity under Add Attributes section

Questions

  1. 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?

1 reply

Pulkit_Jain_
Adobe Employee
Adobe Employee
May 21, 2026 11:13 AM UTC

Arrays and map‑type attributes are not supported in Orchestrated Campaigns. In the Read Audience, Add Attributes panel, only scalar fields appear.
This is a documented guardrail:

“Only scalar attributes are supported; maps and arrays are not allowed.”
https://experienceleague.adobe.com/en/docs/journey-optimizer/using/campaigns/orchestrated-campaigns/guardrails

You can flatten arrays/maps into scalar fields or move repeated objects into relational child tables.

Translate