Segment Conditions

Defining who is eligible for a rule

Overview

This condition restricts the operation of a rule based on defined segments. Only activity done, transactions made, or goals that are satisfied, by the specified eligible segments will cause the rule to successfully be evaluated. For example, if a sales rule specifies that only UK vendors are eligible, sales made by US vendors will not qualify, and the rule will not execute.

To use segment eligibility conditions, you'll need to create segments.

How Segments Interact in Eligibility Conditions

Segment Eligibility allows you to tailor program or rule impact to specific groups of users. Here, we will explore in-depth examples of how Segment Eligibility works for a single segment, multiple segments, and excluded segments.

Single Segment Eligibility

Imagine your program is designed to incentivize your "Power Drivers" — drivers who have completed more than 500 trips. The eligibility criteria for your program would be: User is in: ‘Power Drivers. Now, only the drivers in this segment would be affected by the rules within your program.

Multiple Segment Eligibility

Now, suppose you have two segments: "NYC Drivers" and "Top Drivers" and you want your program to target only the drivers who belong to both of these segments. In this case, you would set up a segment eligibility condition specifying 'User is in” ‘NYC Drivers' AND ‘Top Drivers.'

This uses "AND" logic — only users who belong to both segments ("NYC Drivers" AND "Top Drivers") would be affected by the rules within your program.

Additionally, suppose you want to expand the program to also include "Philly Drivers," but you don't require these drivers to be part of the "Top Drivers" segment. In this case, you would add a separate segment eligibility condition: 'User is in: Philly Drivers.'

Any additional segment eligibility conditions use "OR" logic — users who belong to the segment "NYC Drivers" AND "Top Drivers", OR users who belong to the segment "Philly Drivers" would be affected by the rules within your program.

Excluded Segment Eligibility

Suppose you want to exclude a certain group from your program — for example, drivers who have received complaints, named "Reported Drivers". In this case, you would add a segment eligibility condition: 'User is not in: Reported Drivers.'

Now, any driver who is part of the "Reported Drivers" segment would not be affected by the rules within your program, regardless of their membership in other eligible segments.

Combination of Multiple and Excluded Segment Eligibility

Finally, you can combine these conditions to create more complex eligibility criteria. Suppose you want your program to apply to "NYC Drivers" and "Top Drivers" but exclude any of those drivers who were in the "Reported Drivers" segment.

In this case, you would set up the conditions as follows: 'User is in: NYC Drivers' AND 'User is in: Top Drivers' AND 'User is not in: Reported Drivers.' This would ensure that only top drivers in NYC, who have not been reported, are affected by the rules within your program.

Interaction of Program and Rule-level Segment Eligibility

If you have specified segment eligibility at both the program and rule level for a rule within a given program:

1. Segments at the rule level add further restrictions to segments at the program level.

• Eg. If program eligibility is 'NYC_drivers' and rule eligibility is 'Pro_drivers', the only users eligible for this rule will be NYC drivers who are also Pro Drivers.

• Eg. if program eligibility is 'NYC_drivers' and rule eligibility is not in 'NYC_drivers', no drivers will be eligible for the rule, because it will evaluate NYC drivers who are not NYC drivers.

1. Segments at the program level take precedence.

• Eg. if program eligibility is 'NYC_drivers' and rule eligibility is 'Pro_drivers' OR 'Chicago_drivers', no Chicago Drivers will qualify because they are not in NYC Drivers at the program level.