# Targeting configuration
## 📖 Definition
The targeting step enables you to make your feature visible to one or several groups of users with shared characteristics.\
To define your targeting, you can either configure feature targeting for:
* All users: target all the visitors landing on your feature.
* Users by ID: target the users belonging to a specific ID.
* Targeting by key: target the users matching a specific key.
Using the Decision API directly, or one of our SDK (in API or Bucketing mode), you can target your users via different criteria depending on the package you have subscribed to.\
These criteria are also called *User Context keys* and are useful to target users, but also to filter reporting of your feature when analyzing its results.
## ⚙️ Configuration
For targeting by key, you need to define a User Context key. To do so, you can either use an existing key, by selecting ***Key*** from the first dropdown list and its matching value in the ***Select a value*** field; or create a new key and define its value.\
\
To configure a new User Context key, click ‘Add a criterion’ and select ***Key*** in the first dropdown list and 'Add new' in the ***Select a value*** field.
There are two types of User Context keys:
* Technical keys (for example device, system, geolocation, version).
* Behavioral keys (for example VIP, Early Adopter, Buyer, Viewer, DefaultUser, age, name).
| ⭐ Good to know
You can also create targeting keys in the Persona screen or when calling the Decision API with new context keys.
|
| -------------------------------------------------------------------------------------------------------------------------------------------- |
To send these criteria through one of our SDKs or our Decision API, refer to the [Developer Portal](https://developers.flagship.io).
| 🚩 Heads up
Once you have retrieved data from your various experiments or feature management use cases, you can use the reporting to filter according to the user context keys that you have configured in the step targeting (see screenshot).
|
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
## 💡 Use case
For example, you may need to deploy your feature progressively to different groups of users. Let’s say you want to test your feature internally first, then make it visible only to your early adopters and finally to all your users.\
To do so, you can first push a user context key that you would call **“userType”:“internal”**, then change it to **“userType”:“earlyAdopter”** and finally to **“All users”**.
**Need additional information?**
Submit your request at
Always happy to help!
---
# Agent Instructions: 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.abtasty.com/flagship-deprecated/steps-configuration/targeting-configuration.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.