Configuring the event

In our scenario, we need to receive an event each time a person walks near a beacon positioned next to the spa. The technical user needs to configure the event the system will listen to in our journey.

For additional information on event configuration, refer to this page.

  1. In the top menu, click the Events tab and click Add to create a new event.

  2. We enter the name without spaces or special characters: “SpaBeacon”.

  3. We then select the schema and define the payload expected for this event. We select the fields needed from the XDM normalized model. We need the Experience Cloud ID to identify the person in the Real-time Customer Profile database: endUserIDs > experience > mcid > id. An ID is automatically generated for this event. This ID is stored in the eventID field (experience > campaign > orchestration > eventID). The system pushing the event should not generate an ID, it should use the one available in the payload preview. In our use case, this ID is used to identify the beacon location. Each time a person walks near the spa beacon, an event will be sent containing this specific event ID. This allows the system to know which beacon triggered the event sending.


    The list of fields varies from one schema to another. According to the schema definition, some fields may be mandatory and pre-selected.

  4. We need to select a namespace. A namespace is preselected based on schema properties. You can keep the one preselected. For more information on namespaces, see this page.

  5. A key is preselected based on schema properties and the namespace selected. You can keep it.

  6. Click Save.

  7. Click the View Payload icon to preview the payload expected by the system and share it with to the person responsible for the event sending. This payload will need to be configured in the postback of the Mobile Services administration console.

    The event is ready to be used in your journey. You now need to configure the mobile application so that it can send the expected payload to the Streaming Ingestion APIs endpoint. See this page.

On this page