Set Targeting

Learn how to define who participates in an A/B Test and how to build the rules.

Targeting lets you include only specific users in an A/B Test. You can use user properties, A/B Tests, Feature Flags, and targeting groups as conditions.

A/B Test participants are first subject to Traffic Allocation. Once traffic is allocated, they may be subject to Variation Distribution.

For the full process, see Variation Distribution Process.

Users subject to Override cannot be included in targeting. Cohort targeting is not supported in server-side SDK environments; it is only supported in client SDK environments.

Policy

Policy

When you can configure You can configure or change targeting from A/B Test creation through completion. Applicable statuses: Draft, Running, Paused, Completed

Policy

Default value If targeting is not configured, all users are eligible to participate in the A/B Test.

Policy

Environment You can configure it in the Production and Development environments.

Policy

Rules To restrict the target to specific users, at least one rule is required. You can configure up to 10 rules. Rules are combined with OR. Satisfying just one rule includes a user in the target.

Policy

Conditions A rule has one condition when created. You can add up to 10 conditions per rule. Conditions are combined with AND. All conditions must be satisfied to be included in the target.

Policy

Properties To use a property condition, you need a Hackle SDK integration that collects that property. A/B Tests and Feature Flags can also be used as conditions.

Structure of rules and conditions

Rules and conditions can be composed of the following combinations.

1. Property Key + Operator + Property Value

2. A/B Test (Feature Flag) + Operator + A/B Test Group (Feature Flag Status Value)

3. Targeting Group + Operator + User Group Key

Take the case where you collect the user's operating system under the osName property. To target Android users, build the following combination.

• Property Key: osName

• Operator: is one of

• Property Value: Android, android

The first combination you create becomes the first rule. Adding a combination to the same rule connects it with AND. Adding it as a new rule connects it with OR.

Choosing an operator

An operator defines the relationship between the property key and the property value. Choose the operator that matches the property value type.

Operator	Property Value Type	Selectable Number of Property Values
is one of	String	Multiple selection available
is not one of	String	Multiple selection available
starts with one of	String	Multiple selection available
does not start with one of	String	Multiple selection available
ends with one of	String	Multiple selection available
does not end with one of	String	Multiple selection available
contains one of	String	Multiple selection available
does not contain one of	String	Multiple selection available
=	Number	Multiple selection available
≠	Number	Multiple selection available
≥	Number	Single item selection
≤	Number	Single item selection
>	Number	Single item selection
<	Number	Single item selection
is true	Boolean	Not selectable (property value true is included in the operator)
is false	Boolean	Not selectable (property value false is included in the operator)
version =	Version	Single item selection
version ≠	Version	Single item selection
version >	Version	Single item selection
version ≥	Version	Single item selection
version <	Version	Single item selection
version ≤	Version	Single item selection

Example: users living in a metropolitan city

If residence is a String type, select is one of.

Then add Incheon, Daejeon, Daegu, Ulsan, Busan, and Gwangju as property values.

Configure in the Dashboard

1

Open targeting settings

At the top of the A/B Test detail page, select Set Targeting. The first condition of the first rule appears.

2

Enter the first condition

Select the property key, operator, and property value in order. Depending on the operator, you can enter one or multiple values.

3

Add a condition or a rule

Use + Add AND Condition to add a condition to the same rule. Use + Add Rule to add a new rule combined with OR.

Adding a condition narrows the target range. Adding a rule widens the target range.

Check the configuration status

No targeting configured

When there are no rules, all users are eligible to participate in the A/B Test.

In Draft status, you can see the target information, the Set Targeting button, and example rules.

1. Indicates that all users are targeted.

2. Use Set Targeting to configure rules.

3. An example of how rules appear once configured. These are not actual rules.

In statuses other than Draft, only whether all users are targeted is shown.

Indicates that all users are targeted.

Targeting configured

When there is at least one rule, the number of configured rules is shown. Rules are collapsed on the default view.

1. Shows the number of configured rules.

2. Indicates the rules are collapsed.

3. Use Set Targeting to change the rules.

4. Previews the first condition of the first rule.

Select the expand icon to see all rules.