Add custom data to an SSO session to be used in subsequent journey executions within the same session
This step is used to add customizable key-value pairs to the SSO session information. These key-value pairs can be utilized in subsequent journey executions within the same session, ensuring continuous context between all SSO journey activations. This is particularly useful when the user logs in from different apps, as it allows relevant information to be maintained across all SSO journey activations.
This additional information will be accessible via the output variable of the SSO session validity step, which provides the entire session history.
| Field | Description |
|---|---|
| Session Enrichment Values | Custom key values that will be used in subsequent runs of the SSO journey. |
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.
Consider a journey that performs Device Validation, which generates an output variable called key_id that is associated with the device validation. By keeping the key_id as part of the session enrichment, it can be inspected during subsequent runs to ensure all SSO activity occurs in the context of the same device.