Here are the main steps to configure a new event:
In the top menu, click on the Events tab. The list of events is displayed. Refer to this page for more information on the interface.
Click Add to create a new event. The event configuration pane opens on the right side of the screen. Enter a name for your event. You can also add a description.
Do not use spaces or special characters. Do not use more than 30 characters.
In the Event ID type field, select the event type you want to use.
Rule-based events: this type of event does not generate an eventID. In the Event ID condition field, you simply define a rule which will be used by the system to identify the relevant events that will trigger your journeys. This rule can be based on any field available in the event payload, for example the profile’s location or the number of items added to the profile’s cart.
System-generated events: this type requires an eventID. This eventID field is automatically generated when creating the event and added to the payload preview. The system pushing the event should not generate an ID, it should pass the one available in the payload preview. See this section.
Read more on event 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) Journey Orchestration expects to receive. You will then be able to use this information in your journey. See this page.
When you select the System Generated type, only schemas that have the eventID type mixin are available. When you select the Rule Based type, all Experience Event schemas are available.
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 Journey Orchestration.
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 page.
Define the key: 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, Journey Orchestration 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 page.
For system-generated events, you can add a condition. This step is optional. This allows the system to only process the events that meet the condition. The condition can only be based on information contained in the event. See this page.
The event is now configured and ready to be dropped into a journey. Additional configuration steps are required to receive events. See this page.