Variable-to-variable comparisons in Journeys

Business problem

The current Journeys "Apply condition" action only allows comparing a variable against a static, hardcoded value. This prevents dynamic decision-making and identity validation within workflows when logic depends on two distinct data points.

Wished result

The ability to compare two different variables against each other within Journeys conditions. This would enable use cases such as verifying if a user-provided email matches a system-stored profile or comparing current input against historical data patterns.