▪️Query Builder

Comparison between 2 Properties

The Query Builder supports direct comparisons between properties when working with numeric and multi-currency fields. This allows for advanced conditions, such as evaluating whether the Casino Win amount is greater than the Casino Bet amount.

To enhance precision, a multiplier option is available - custom factors like 1.5×, 2×, etc... can be applied to scale values during comparison.

This feature is integrated across real-time evaluations, segment validations, and both campaign and segment builders, offering greater flexibility and control in targeting logic and automation workflows.

Whenever you select a numeric property in the Query builder you will notice an additional button appearing that will allow you to switch between the default (C) Constant and the (P) Comparison between 2 properties.

Some sections are in the process of migration (e.g. campaign) and the new comparison between 2 properties will not be available.

BO: Example of property to property comparison in Query Builder

Use case with User State condition

Let’s say you want to segment users who are profitable to your operation at a certain level. Traditionally, you might apply rigid conditions - like targeting users with a lifetime deposit amount above a fixed threshold. But this approach misses nuance.

For example:

• A user who deposited 1,000 EUR and withdrew 990 EUR isn’t highly profitable.

• A user who deposited 1,000 EUR and withdrew only 150 EUR is clearly more valuable.

Capturing this distinction with static filters would require creating dozens of segments based on deposit and withdrawal ranges which is a time-consuming process.

So the solution is to use comparison between 2 propoerties and apply a dynamic condition like:

Total Deposit Amount > 2 × Total Withdrawal Amount

BO: Example of prop to prop for user state condition

This instantly identifies users whose lifetime deposits are at least twice their withdrawals - regardless of the actual amounts. Examples:

• 500 EUR deposited vs. 200 EUR withdrawn

• 200 EUR deposited vs. 0 EUR withdrawn

All of these users would qualify under this rule, making your segmentation smarter, faster, and more meaningful.

Use case with Behavioral condition

Property to property comparison integrates smoothly with behavioral segmentation, allowing you to apply it to metrics such as minimum, maximum, and average values within those segments.

For example you can set a condition such as: Maximum Bet Amount ≤ 2 × Minimum Bet Amount

BO: Example of prop to prop for behavioral condition

This identifies users whose betting behavior shows little variation - where their highest bet is only twice (or less) their lowest. Such patterns may suggest low engagement or hesitation to place larger bets.

These users might not have discovered a game they truly enjoy. To boost engagement, consider offering targeted bonuses across a variety of games to encourage exploration and higher activity.