Bucket glossary

Discover Bucket’s feature management, product, and technical terms and get their definitions in our glossary.

Targeting rules

Targeting rules decide which users will be served which features

Targeting rules can have one or multiple conditions. A target rule condition always contains:

  • A segment or context attribute that defines the scope of the targeting rule
  • An operator defining the differentiating characteristics of the segment or context attribute
  • A value that you specify to identify the segment or context attribute

Buckets targeting rules are designed for B2B contexts. By using targeting rules you can dynamically enable specific features for specific users based on the company they are part of or in the context that they are using your application. 

Targeting rules are matched against:

  • Company attributes:Examples of user attributes include Company ID, Company name, and Company industry.  
  • User attributes: Examples of user attributes include User ID, Email, and User Role.
  • Segment: Target existing segments created in the Companies tab that don’t use First seen, Last seen, or Feature metrics filters.
  • Feature targeting: Re-use targeting rules from another feature. You can choose to include or exclude companies that are targeted by another feature.
  • Other context: Used to specify a certain context your user is in that doesn't necessarily relate to company or user attributes. , like an eventID.
    • For example, a CRM application only wants to enable a live chat feature when a user is in the context of a specific event in the application.

Related to: Features

A single snippet to rollout and analyze

Get started in minutes.

Documentation