> For the complete documentation index, see [llms.txt](https://help.openloyalty.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.openloyalty.io/members-and-activity/members/custom-fields.md).
# Custom Fields
This article explains how custom fields can be created and used in your loyalty program.
The **Custom Fields** feature allows you to extend member profiles (and other modules) with additional information specific to your program needs. These fields make it possible to capture structured data beyond the default attributes, helping you personalize campaigns, segment members more precisely, or store business-specific identifiers.
***
### Key Functionalities
* 𧩠**Custom fields per module** β **Custom fields** opens a module picker: **Members**, **Campaigns βΊ Direct**, **Campaigns βΊ Automation**, **Campaigns βΊ Referral**, **Leaderboards**, **Challenges**, **Rewards** and **Fortune wheels**. Each module has its own schema editor.
* ποΈ **Groups** β fields are organised into groups. A group can also include a **subgroup**: a repeatable record that stores its own set of fields and can be filled in several times per member. Subgroups can't be nested.
* π οΈ **Define field properties**:
* **Type** β **String**, **Single select**, **Multi select**, **Number**, **Boolean** or **Date**.
* **Set as Required** β make the field mandatory when creating or editing a member.
* **Predefined values** β use a **Single select** or **Multi select** field, whose options come from a collection.
* π€ **Visibility** β a member's values are shown on the member profile, under a menu item named after the group.
{% hint style="warning" %}
A module's schema can hold up to **25 fields**. The counter at the bottom of the editor shows how many are used (for example, **1 / 25 fields used**).
{% endhint %}
***
### Creating a Custom Field
{% stepper %}
{% step %}
Navigate to **Configuration β Custom Fields**.
{% endstep %}
{% step %}
Select the module (for member fields, **Members**). The schema editor shows the module's groups and their fields. Click **Add group** to create a group, or use **Add field** inside an existing group.
{% endstep %}
{% step %}
Click **Add field** and pick the field type: **Subgroup**, **String**, **Single select**, **Multi select**, **Number**, **Boolean** or **Date**.
{% endstep %}
{% step %}
Enter the field **Name**. The **System code** is generated from the name. Optionally add a **Description**.
{% endstep %}
{% step %}
(Optional) Switch on **Set as Required**.
{% endstep %}
{% step %}
For a **Single select** or **Multi select** field, select the **Collection** its options come from.
{% endstep %}
{% step %}
Click **Next step**, then confirm on the summary.
{% endstep %}
{% endstepper %}
***
### Managing Custom Fields
* **Edit a field** β open the module's schema editor and expand the field's card in its group.
* **Fields have no status** β there is no Active/Inactive switch for a field.
***
### Editing Members with Custom Fields
When creating or editing a member profile, custom fields are listed under the name of their group, for example **Retail Profile βΊ Preferred Channel**. Required fields are displayed as mandatory inputs.
Administrators must complete all required fields before saving changes to the profile.
***
### Displaying Custom Fields in Single Member View
A member's custom field values are shown on a profile menu item named after each group (here **Retail Profile**). Here you can see:
* The **field name** (e.g., Preferred Channel).
* The **value** selected or entered for that member (e.g., βonlineβ).
***
### Example Use Cases
* π¦ **Supplier or partner code** β track which supplier a member is linked to.
* πͺ **Favorite store** β capture the memberβs preferred location for redemptions or pickups.
* π·οΈ **Customer category** β e.g., B2B vs. B2C, VIP status, or special program flags.
---
# 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://help.openloyalty.io/members-and-activity/members/custom-fields.md?ask=&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.