The payload definition allows you to choose the information the system expects to receive from the event in your journey and the key to identify which person is associated to the event. The payload is based on the Experience Cloud XDM field definition. For more information on XDM, refer to this page.
Select an XDM schema from the list and click on the Payload field or on the Edit icon.
All the fields defined in the schema are displayed. The list of fields varies from one schema to another. You can search for a specific field or use the filters to display all nodes and fields or only the selected fields. According to the schema definition, some fields may be mandatory and pre-selected. You cannot unselect them. All fields that are mandatory for the event to be received properly by Journey Orchestration are selected by default.
Make sure that you have added the “orchestration” mixin to the XDM schema. This will ensure that your schema contains all the required information to work with Journey Orchestration.
Select the fields you expect to receive from the event. These are the fields which the business user will leverage in the journey. They must also include the key that will be used to identify the person associated to the event (see this page).
For system-generated events, the eventID field is automatically added in the list of fields selected so that Journey Orchestration can identify the event. The system pushing the event should not generate an ID, it should use the one available in the payload preview. See this page.
When you’re done selecting the needed fields, click Save or press Enter.
The number of selected fields appears in the Payload field.