# Configuration

In this section, we will guide you from the [Flagship platform](https://app.flagship.io/), to create a use case, define its KPI, its flags, and its criteria of targeting. [Learn more](/feature-experimentation-and-rollout.md)

It can be done in 6 steps:

## **1. Create a toggle use case in Flagship**

From the [Flagship platform](https://app.flagship.io/), we create a feature toggle with the name Login with Google and we define 3 KPI, submit-basic-login to capture the number of times a basic login is used, click-google-login and click-wechat-login. [Learn more](/feature-experimentation-and-rollout.md)

<figure><img src="/files/VZbeKdFl9McDD4iL2qjy" alt=""><figcaption><p>define kpis</p></figcaption></figure>

## **2. Set up your flags**

We define 3 flags, login-btn-color, login-with-google and login-with-wechat.

<figure><img src="/files/4F12emebJTDF7VQGGJQj" alt=""><figcaption><p>define flags</p></figcaption></figure>

## **3. Define your scenarios**

Here we define the value of each flags will have according to geographic zone of visitor

<figure><img src="/files/TJuAcYggAM8ikXVSYmoF" alt=""><figcaption><p>define scenarios</p></figcaption></figure>

## **4. Set up your targeting criteria for each scenario**

The targeting criteria will be like this:

* Scenario 1: will concern only users who are in Europe/America zone
* Scenario 2: for Asia geographic zone
* Scenario 3: for users who are outside of Europe/America and Asia zone

<figure><img src="/files/6pfJKKtlH2aXqe4hf4Mf" alt=""><figcaption><p>define targetings</p></figcaption></figure>

## **5. Switch on your use case**

Now your use case is created, the last step is to switch it on

<figure><img src="/files/IugDXr0hLxL7m3W1E1Re" alt=""><figcaption><p>switch on your use case</p></figcaption></figure>

## **6. Get your API\_KEY and ENV\_ID**

<figure><img src="/files/lveySydVodw0zyTx1MV4" alt=""><figcaption><p>get api configuration</p></figcaption></figure>


---

# 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/server-side/sdks/quickstart/configuration.md?ask=<question>
```

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.
