> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/flagship-deprecated/use-cases/configuring-a-feature-toggleflag.md).

# Configuring a Feature Toggle/Flag

## 📖 Definition

A **Feature Toggle/Flag** lets you enable or disable a feature or a group of features depending on a specific audience.\
It allows you to easily and safely release your features.

## ⚙️ Configuration

To configure a Feature Toggle/Flag, apply the following steps:

1. From the dashboard, click **Create a use case.**
2. Select the **Feature Toggling** template.\
   ![Template.png](https://195542843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPLcJUpntQruhbI1jQ2kr%2Fuploads%2Fgit-blob-896066d513fcd80dff26b06b773f8ab7fd25703b%2Fc922da03992f6e18df159c1d4aeb60aa.png?alt=media)\
   \&#xNAN;**\[Basic information]**\\
3. Enter the **name** of your feature and its **description.**
4. Choose the **primary and secondary KPIs** you want to follow.
5. Click **Save and continue.**\
   \
   \&#xNAN;**\[Scenarios]**
6. Define your scenarios: **edit** the name of your first scenario.
7. Configure your **scenarios** by defining the group of users who will see each scenario (for more information, refer to the article about [Targeting](https://flagship.zendesk.com/hc/en-us/articles/360018565380) configuration) and by defining their **flag's** name, type (text, number, boolean, array, or object), and value.\
   ![scenarios.png](https://195542843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPLcJUpntQruhbI1jQ2kr%2Fuploads%2Fgit-blob-af08229aeca60a37fa77cbd71befcd1bd731ed88%2F0033f10dc45dd9c3665171ff252441aa.png?alt=media)\\

   | <p>⭐ Good to know</p><p>By default, one scenario appears. But you can ass as many as you want by clicking Add scenario.</p> |
   | --------------------------------------------------------------------------------------------------------------------------- |
8. Click **Save and continue.**\
   \
   \&#xNAN;**\[Overview]**
9. Check that every step has been configured correctly.
10. (Optional) Notify your teammates that the Feature Toggle/Flag is ready to go.

## 💡 Use case

Let’s say you have developed two new payment features: one for mobile devices and one for desktop. Before releasing them, you want to test them to early adopter users to see if the features fit the original need. In addition, you want to know what their usage rate would be.

In this case, you can create a Feature Toggling:

1. Create a **Feature Toggling** use case on your Flagship account.
2. Choose the **KPI** you want to follow. Here, you can select the **KPI** related to a click on the “*Proceed to checkout*” button. You need to have configured it in your codebase beforehand.
3. Select **conversion rate** as a sub KPI type.
4. In the **scenarios** step, define two scenarios: one that enables the feature on desktop and one on mobile devices. On each, configure the flag that will enable the new payment method:\
   ![mobile.png](https://195542843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPLcJUpntQruhbI1jQ2kr%2Fuploads%2Fgit-blob-9d51f2e3d9613c58a82c196e7d0eefcfc5e951f1%2F884948713da02e9621c6d3498408707d.png?alt=media)\
   ![desktop.png](https://195542843-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPLcJUpntQruhbI1jQ2kr%2Fuploads%2Fgit-blob-b30bd364b786effc518754f3091b03211565fe24%2F3bf6fba9417d549be669bd9c8560aaa2.png?alt=media)
5. Check the **overview** of your Feature Toggle.
6. Save and **activate your use case** via the dashboard.

**Need additional information?**

Submit your request at <product.feedback@abtasty.com>

Always happy to help!


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.abtasty.com/flagship-deprecated/use-cases/configuring-a-feature-toggleflag.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
