An event is linked to a person. It relates to the behavior of a person (for example, a person bought a product, visited a shop, exited a website, etc.) or something happening linked to a person (for example, a person reached 10 000 loyalty points). This is what Journey Orchestration will listen to in journeys to orchestrate the best next actions.
This configuration is mandatory , as Journey Orchestration is designed to listen to events, and always performed by a technical user .
The event configuration allows you to define the information Journey Orchestration will receive as events. You can use several events (in different steps of a journey) and several journeys can use the same event.
If you edit an event used in a draft or live journey, you can only change the name, the description or add payload fields. We strictly limit the edition of draft or live journeys to avoid breaking journeys.
Events are POST API calls. Events are sent to the Adobe Experience Platform through Streaming Ingestion APIs. The URL destination of events sent through transactional messaging APIs is called an “inlet”. The payload of events follows XDM formatting.
The payload contains information required by Streaming Ingestion APIs to work (in the header) and the information required by Journey Orchestration to work (the event ID, part of the payload body) and information to be used in journeys (in the body, for example, the amount of an abandoned cart). There are two modes for the streaming ingestion, authenticated and unauthenticated. For details on Streaming Ingestion APIs, refer to this link .
After arriving through Streaming Ingestion APIs, events flow into an internal service called Pipeline and then in the Adobe Experience Platform. If the event schema has the Real-time Customer Profile Service flag enabled and a dataset ID that also has the Real-time Customer Profile flag, it flows into the Real-time Customer Profile Service.
The Pipeline filters events which have a payload containing Journey Orchestration eventIDs (see the event creation process below) provided by Journey Orchestration and contained in event payload. These events are listened by Journey Orchestration and the corresponding journey is triggered.
Creating a new event
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. See User interface 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.Do not use spaces or special characters. Do not use more than 30 characters.
- Add a description to your event. This step is optional.
- 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 Defining the payload fields .
- 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.
- 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 Selecting the namespace .
- 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 Defining the event key .
- 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 Adding a condition .
- Click Save .The event is now configured and ready to be dropped into a journey. Additional configuration steps are required to receive events. See Additional steps to send events to Journey Orchestration .