Configure journeys configure-journeys
In order to send messages with journeys, you need to configure Data Sources, Events and Actions.
Data Sources data-sources
The Data Source configuration allows you to define a connection to a system to retrieve additional information that will be used in your journeys. Learn more
Events events
Events allow you to trigger your journeys unitarily to send messages, in real-time, to the individual flowing into the journey.
In the event configuration, you configure the events expected in the journeys. The incoming events’ data is normalized following ۶Ƶ Experience Data Model (XDM). Events come from Streaming Ingestion APIs for authenticated and unauthenticated events (such as ۶Ƶ Mobile SDK events). Learn more
Actions actions
Journey Optimizer message capabilities are built-in: you only need to add a channel action activity to your journey. If you are using a third-party system to send your messages, you can create a custom action. Learn more
Browse through ۶Ƶ Experience Platform fields friendly-names-display
When defining event payload, field group payload and selecting fields in the expression editor, the display name is displayed in addition to the field name. This information is retrieved from the schema definition in the Experience Data Model.
If descriptors such as “xdm:alternateDisplayInfo” are provided while setting up schemas, the user-friendly names will replace display names. It is especially useful when working with “eVars” and generic fields. You can configure friendly name descriptors via an API call. For more information, see the Schema Registry developer guide.
If a friendly name is available, then the field will be displayed as <friendly-name>(<name>). If no friendly name is available, the display name will appear, for example <display-name>(<name>). If none of them are defined, only the technical name of the field will be displayed <name>.