Targeting rules

Definition

Targeting rules are entities used in Bucket to describe the target audience of a given feature. The target audience refers to the users that can interact with the feature within your application. Additionally, each targeting rule contains a value that is used for the target audience.

Filters

Targeting rules are essentially a collection filters that are matched against a specific evaluation context. The first rule with a filter matching the context is selected, and its value used as result. In the case of feature access it can either be true , indicating that the feature is accessible. If no rules match the context, a value of false is used — feature not accessible.

Evaluation context

The evaluation context refers simply to a collection of key — value pairs that are passed to the rules' filters. Bucket expects the evaluation context to contains the following data:

• User's ID as a minimum,

• Any other user attributes that might be used by the filters in the rules,

• Company's ID is necessary in the vast majority of cases, though it's not mandatory,

• Any other company attributes that might be used by the filters in the rules,

• A collection of "other" attributes that can be used by the feature access targeting rules.

The exact structure of the data will vary by the SDK in use.

Missing context fields

During the evaluation of targeting rules against a context it might happen that context is missing some details that the rules require. In such cases, those rules are discarded from evaluation as it would be unsafe to do otherwise.

Bucket reports these missing context fields using feature events. Bucket SDKs will also generate warnings in these cases making it easy to find these situations in your application.

Next steps

• Learn about filters,

• Learn how to setup feature access rules within Bucket UI.