---
title: Custom fields in Feature Experimentation
slug: feature-experimentation/docs/custom-fields-in-feature-experimentation
docTags: 
createdAt: 2026-08-05T20:40:00.000Z
---

- Optimizely Feature Experimentation

Custom fields add required or optional metadata to flags and rules, going beyond standard properties like name, key, and description. When you require collaborators to enter these fields when they create a flag or a rule, you add structure and accountability to your workflow.

Use custom fields to do the following:

- Capture domain-specific details such as Jira links, page names, or categories.
- Improve reporting and tracking across projects.
- Filter, sort, and group flags for quick access and better discoverability.

Custom fields make it easier to manage experiments and flags at scale.

## Benefits of custom fields

Custom fields provide the following benefits for managing and scaling experimentation programs:

- **Organization and clarity –** Categorize experiments and flags for easier management and improved discoverability through enhanced filtering.
- **Improved insights –** Use custom fields in dashboards and reports to analyze impact across multiple dimensions.
- **Scalability and efficiency –** Provide structured tagging to reduce duplicate experiments and minimize configuration errors in large organizations.
- **Enhanced collaboration –** Promote a unified approach to experimentation across teams and simplify experiment reviews with consistent metadata.

At the **rule** level, custom fields bring the same structure to the individual A/B tests, feature rollouts, and targeted deliveries within a flag's [ruleset](docId\:h1v5aDhM3KPn1_SyZ6e6W):

- **Experiment context and governance –** Capture details such as the hypothesis owner, Jira ticket, or test phase on each rule, so the reasoning behind your targeting and traffic decisions stays with the experiment.
- **Consistent organization of rules –** Categorize rules across a ruleset so teams can group and report on experiments, rollouts, and targeted deliveries in a uniform way.
- **Accountability at rule creation –** Require key metadata when collaborators create or edit a rule, reducing incomplete or inconsistent experiment setups.

## Create custom fields

1. Go to **Settings > Fields**.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/cBvfklG-L5Xn4YfJlnl3E_settings-fields-empty-custom-fields-tab.png)

2. Click **Create Custom Field**.
3. Enter a **Name** for the custom field and, optionally, a **Description**.
4. Select the **Make this field required** checkbox to require collaborators to enter a value when they create a flag through the [Feature Experimentation UI](docId\:j7bgkTxrI8VN_z2dOZu1R) or the [Create feature flags REST API](docId\:eH-UMm_rOn_GdGDGLV6__).
5. Select an option from the **Entities** drop-down list to choose whether the custom field applies at the **Flags** level or the **Rules** level. A custom field applies to one entity type, and you cannot change the entity type after you create the field. For details on configuring custom fields, see [Manage flags](docId\:j7bgkTxrI8VN_z2dOZu1R). 
6. Select the **Type** of custom field. The type controls what collaborators enter or select when they fill in the field on a flag.
   - **Label** – A predefined list of values. Select **Allow multi-select** to permit multiple selections.
   - **Text** – Free-form text. Set a **Character Limit** to restrict the number of characters allowed.
   - **Numerical** – A number within a range you define. Set the range, specify decimal places, and choose whether to format thousands with a comma separator.
   - **Link** – Any URL.
   - **Boolean** – A `true` or `false` selection.

::Image[]{src="https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/9dNbZ5V-32J8-pGQoh3N5_create-custom-field-create-custom-field-dialog.png" size="60" isUploading="false" width="1297" height="1206" darkWidth="1297" darkHeight="1206" showCaption="false"}

7. Click **Create Custom Field** to save the field.

## Edit custom fields

Go to **Settings > Fields**.

The **Fields** page lists all custom fields. Use the search bar to find a field by name or key. Filter by **Type** or **Status** using the drop-down lists.

Click **More options (...) > Edit** for the field you want to edit.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/0gqN3ehM9UgZ5aSutPwBG_settings-fields-edit-custom-field-menu-option.png)

Make the necessary changes and click **Save**.

:::hint{type="info"}
You can only edit the **Name** and **Description** of a custom field.
:::

## Archive custom fields

Archive a custom field to remove it from the list of custom fields.

:::hint{type="info"}
Optimizely Feature Experimentation retains your custom field data so you can [unarchive](docId\:FR469ek790vzzg2Pwpuev) it later.
:::

1. Go to **Settings > Fields**.
2. Click **More options** **(...)** for the field.
3. Click **Archive**.

## Unarchive custom fields

To unarchive a field, complete the following steps:

1. Go to **Settings > Fields**.
2. Select **Archived** for the **Status**.
3. Click **More options** **(...)** for the field.
4. Click **Unarchive**.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/7SqOyRjovAVv8iE-jbtr2_settings-fields-unarchive-custom-field-menu-option.png)

## Custom fields on rules

When a custom field applies at the **Rules** level, it displays in the **Custom Fields** section of the rule. Collaborators enter values when they create or edit a rule.

- Required fields are set by your project administrators and must be completed before you can save the rule.
- Optional fields can be added or edited at any time.
- Rules support the same field types as flags: **Label**, **Text**, **Numerical**, **Link**, and **Boolean**.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/RQ4_qyeMsfmU9QKDkW2td_ruleset-custom-fields-required-custom-field-on-rule.png)

## Custom fields on the Flags Dashboard

To display the custom fields you [created in the previous step](docId\:FR469ek790vzzg2Pwpuev), on the [Custom Flags Dashboard](docId\:uK1k1V4L8vrVFgur_AY_u) complete the following steps:

1. Go to **Flags**.
2. Click **Show/Hide Columns**.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/n2vyF5kL9U7dj-XBaigKF_flags-all-flags-show-hide-columns-button-on-flags-list.png)

3. Click the **Column** tab.
4. Select your custom fields.
5. Click **Close** or anywhere outside the **Table Options** section to save your selection.

Feature Experimentation displays the custom fields you select in a column.

![](https://api.archbee.com/api/optimize/BrbvVORKJ5iIeSMZye5kI/CovpTvcSH1fXN8hn4pHUw_flags-all-flags-custom-field-column-in-flags-list.png)

After they are displayed, you can use custom field columns to filter and sort flags on the dashboard. For details on setting custom field values, see [Update custom fields](docId\:j7bgkTxrI8VN_z2dOZu1R). For details on what Feature Experimentation displays on the **Flags Dashboard**, see [Custom Flags Dashboard](docId\:uK1k1V4L8vrVFgur_AY_u).