Reads and processes information that was provided by another journey
Cross-session messages allow journeys to share info and create dependent flows. Before this step can be executed, another journey must create the message using the Create Cross-Session Message step and make the message ID available to this journey. This step uses the message ID to look up the message, read its content, mark it as processed, and write response data to the message.
Once this step is completed, any journey that's waiting for the message to be processed (using the Wait for Cross-Session Message step) will resume their flow and can access the additional response data. However, if the message has expired or has already been processed, the journey is aborted.
| Field | Description |
|---|---|
| Cross-session message reply fields | A list of fields for the message response, which can be used by subsequent journey steps and any journey waiting for the message to be processed. The key is a parameter name and the value is an expression that yields the parameter value at runtime. |
| Output variable | Name of the variable used to store the content of the processed message, which can be used in subsequent journey steps. Default is cross_session_message. It contains the message content (user_params) and message metadata (system_params). |
| Message ID | Expression yielding the message ID for this step, identifying the message to read and process. |
| Delete cross-session message after consumption | Determines whether to delete the message immediately after it's processed or wait until it expires. Default is No. |
This step can be configured to record step input and output data, or a custom payload, which is then surfaced in journey events in Journey Analytics for diagnostic purposes. For details, see Additional data reporting.
Assume the user runs a journey on a desktop device, and then that journey initiates a cross-device handoff to a mobile device. Now when running a journey on the mobile device, the journey can extracts a cross-session message, performs actions, and then processes the cross-session message using the Process Cross-Session Message step. See Cross-device face authentication as an example of the flow leveraging cross-session messages.
