> For the complete documentation index, see [llms.txt](https://docs.reflag.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reflag.com/product-handbook/concepts/targeting-rules.md). # Targeting rules ### Definition Targeting rules are entities used in Reflag to describe the target audience of a given [feature](/product-handbook/concepts/feature.md). 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](/product-handbook/concepts/filter.md) 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. Reflag expects the evaluation context to contains the following data: * User's `ID` as a minimum, * Any other [user attributes](/product-handbook/concepts/user.md#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](/product-handbook/concepts/company.md#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. Reflag reports these missing context fields using [feature events](/product-handbook/concepts/feature-events.md). Reflag SDKs will also generate warnings in these cases making it easy to find these situations in your application. ### Next steps * Learn about [filters](/product-handbook/concepts/filter.md), * Learn how to [setup feature access rules](/product-handbook/feature-rollouts/feature-targeting-rules.md) within Reflag UI. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.reflag.com/product-handbook/concepts/targeting-rules.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.