Configure a unitary event configure-an-event

In the ADMINISTRATION menu section, select Configurations. In the Events section, click Manage. The list of events is displayed.

Click Create Event to create a new event. The event configuration pane opens on the right side of the screen.

Enter the name of your event. You can also add a description.

In the Type field, choose Unitary.

In the Event ID type field, select the event ID type you want to use: Rule Based or System Generated. Read more on event ID types in this section.

The number of journeys that use this event is displayed in the Used in field. You can click the View journeys icon to display the list of journeys using this event.

Define the schema and payload fields: this is where you select the event information (usually called a payload) journeys expects to receive. You will then be able to use this information in your journey. See this section.

For rule-based events, click inside the Event ID condition field. Using the simple expression editor, define the condition that will be used by the system to identify the events that will trigger your journey.

In our example, we wrote a condition based on the profile’s city. This means that whenever the system receives an event that matches this condition (City field and Paris value), it will pass it to journeys.

Add a namespace. This step is optional but recommended as adding a namespace allows you to leverage information stored in the Real-time Customer Profile Service. It defines the type of key the event has. See this section.

Define the profile identifier: choose a field from your payload fields or define a formula to identify the person associated to the event. This key is automatically setup (but can still be edited) if you select a namespace. Indeed, journeys picks the key that should correspond to the namespace (for example, if you select an email namespace, the email key will be selected). See this section.

Click Save.

The event is now configured and ready to be dropped into a journey. Additional configuration steps are required to receive events. See this page.

Select an XDM schema from the list and click on the Fields 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 journeys are selected by default.

Select the fields that 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 section).

When you’re done selecting the needed fields, click Ok or press Enter.

The number of selected fields appears in the Fields field.

Click inside the Profile identifier field, or on the pencil icon.

Select the field chosen as the key in the list of payload fields. You can also switch to the advanced expression editor to create more complex keys (for example, a concatenation of two fields of the events).

Click the View Payload icon to preview the payload expected by the system.

You can notice that the fields selected are displayed.

Check the preview to validate the payload definition.

Then, you can share the payload preview with to the person responsible for the event sending. This payload can help them design the setup of an event pushing to Journey Optimizer. See this page.