Outcome reasons explain why an Evaluation received a particular outcome. They provide more functionality than a tag by documenting the decision and passing context to later Workflows in a Journey.
How outcome reasons work
A tag is treated as an outcome reason when the tag has one or more outcomes configured under Global Settings > Outcomes.
Additional functionality
Explain an outcome
Outcome reasons appear in the Evaluation Summary, helping reviewers identify the signal or rule associated with the final decision without looking through the entire Workflow logic.
Pass context to a later Workflow
In a Journey, you can import an upstream outcome reason into a downstream Workflow and use it in threshold or outcome logic.
Configure the relevant outcome under Global Settings > Outcomes in the upstream Workflow.
Save the upstream Workflow as a new version.
In the downstream Workflow, select Add > Outcome Reason and import the reason.
Use the imported reason in the downstream logic, then save the applicable versions.
The upstream Workflow must return an outcome configured for that reason. If it returns a different outcome, the reason is not available downstream.
Return decision data
Outcome reasons appear in Evaluation summaries and can be returned in Journey application data. Your systems can use this information for reporting, audit trails, or downstream processing.
Configure an outcome reason
Open the Workflow version you want to edit.
Select the relevant tag and open Global Settings.
Under Outcomes, select each outcome for which the tag should be an outcome reason.
Select Apply, then save the Workflow as a new version.
Select every outcome under which the reason should be displayed or passed downstream.
Troubleshooting
If a reason does not appear, confirm that the tag is configured for the evaluation’s actual outcome and that you are reviewing the correct Workflow version. If it is unavailable downstream, confirm that the downstream Workflow imported it and that the Journey uses that version.