Array of Objects for event parameters follows the same principles as Array of Objects attributes, with one important difference: event parameters are insert-only.
1. The structure is defined in the panel first
The Array of Objects event parameter and its object keys (including sub-object keys, if any) must be created in the panel before data is sent. This ensures all incoming data follows a predefined structure.
2. Only registered parameters are accepted
Object data must be sent through the dedicated object_event_params field. Parameters that are not registered in the panel are ignored during ingestion, which prevents unexpected or inconsistent data from entering the system.
3. Segmentation runs on a consistent model
Segmentation runs directly on the objects stored inside each event.
Filters apply at the object level, not just at the event level
Multiple object keys can be evaluated together against the same object
"Number of Objects" logic allows you to define how many objects must meet the criteria
4. Event data is immutable
Unlike Array of Objects attributes, event parameters do not support patch actions. An event is a record of something that happened, so its Array of Objects value is written once at ingestion and is not updated afterward.
5. Data becomes segmentable in near real time
Array of Objects event parameters follow the same availability behavior as flat event parameters. Data is typically available for segmentation within seconds of ingestion.
Example Use Case: Multi-Item Purchase
Business Scenario
You want to:
Send all purchased items inside a single purchase event.
Keep item details such as price, category, and quantity connected to each other.
Segment users who purchased more than one item in a single transaction.
Segment users who purchased a specific category above a price threshold.
Now, refer to Create the Array of Objects Event Parameter to learn how to create it.