Data cycle

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.

For system-generated events, 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. For rule-based events, the system identifies the event using the eventID condition. These events are listened by Journey Orchestration and the corresponding journey is triggered.

On this page