# Configuring a Personalization

## 📖 Definition

A **Personalization** enables you to create several scenarios to display the right content to the right audience at the right time, while tracking their performance over time.

## ⚙️ Configuration

To configure a Personalization, apply the following steps:

1. 1. From the dashboard, click **Create a use case.**
   2. Select the **Personalization** templat&#x65;**.**\
      ![Template.png](/files/pVrkEg9QHoMWMxFTGUxk)\
      \
      \&#xNAN;**\[Basic information]**
   3. Enter the **name** of your feature and its **description.**
   4. (Optional) 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. Define the **targeted users.**
   8. Configure your **scenarios** by defining their **flag's** name, type (text, number, boolean, array, or object), and value.\
      ![Perso.png](/files/nRzPVwwgKp7kO4tQwhvk)\\
   9. Click on **Add scenario** and repeat **steps 6, 7 and 8.**\\
   10. Click **Save and continue.**\
       \
       \&#xNAN;**\[Allocation]**
   11. If needed, change the percentage of traffic allocated to the control variation for each scenario. By default, for each scenario, 5% is allocated to the control variation.\
       \
       ![allocation.png](/files/K2BEiS6YIILgKbubJxfh)\
       \\

       | <p>⭐ Good to know</p><p>We recommend keeping a small portion of traffic on your control variation, as this allows you to verify that the scenario you implemented doesn’t have a negative impact on the performance of the default version of your feature.</p> |
       | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   12. Click **Save and continue.**\
       \
       \&#xNAN;**\[Overview]**
   13. Check that every step has been configured correctly.
   14. (Optional) Notify your teammates that the personalization is ready to go.

## 💡 Use case

Let’s say you want to personalize the user experience of your VIPs and new users on mobile and desktop by showing them different discount codes.

To do so:

1. Create a **Personalization** use case on your Flagship account.
2. Choose the **KPI** you want to follow. Here, you can select the **conversion rate** generated by your scenarios.
3. Create four scenarios named:
4. 1. VIP users on mobile
   2. VIP users on desktop
   3. New users on mobile
   4. New users on desktop
5. Define the **targeted users** and the **flag** (with its value) that will activate each discount code for **each scenario**. Here is an example with the discount code for VIP users on mobile:\
   ![Perso\_case.png](/files/ZYD21suSDjrMfRUILAXF)\\
6. Set the **traffic percentage to 95% for each scenario and to 5% for the control variation** (to keep an eye on a small part of your targeted traffic).\
   ![Perso\_allocation.png](/files/RH2V4aykTklrPu0X2T24)\\
7. Save and **activate your use case** via the dashboard.
8.

**Need additional information?**

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

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/use-cases/configuring-a-personalization.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.
