> 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/implementation-guide/integrations-and-data-exchange/custom-fields/segmenting-on-custom-fields.md).

# Segmenting on Custom Fields

The segment condition builder has a dedicated **Custom Fields** tab, so you can target members by the data you've extended their profile with.

### Condition types

<table><thead><tr><th width="197.3125">Condition</th><th>What it does</th></tr></thead><tbody><tr><td><strong>Contains value</strong></td><td>Matches values stored in an array field (Multi select or a Subgroup field), with <strong>Contains any of</strong> / <strong>Contains all of</strong>.</td></tr><tr><td><strong>Range</strong></td><td>A numeric field between two values. The lower bound is inclusive and the upper bound is exclusive — <code>[from, to)</code>.</td></tr><tr><td><strong>Threshold</strong></td><td>A numeric comparison (greater than, greater or equal, less than, less or equal, equal to) against a single value.</td></tr><tr><td><strong>Compare fields</strong></td><td>Compares two numeric fields against a threshold. All four operators are shown — subtract, add, multiply, divide — but only <strong>Subtract</strong> is enabled initially; the rest are greyed out.</td></tr></tbody></table>

### Picking a field

The field picker lists group fields and subgroup fields in a single dropdown. Groups and subgroups appear as non-clickable headers — only simple fields can be selected. Once picked, the selected state shows the **full path** (group / subgroup / field name), since the same field name can exist in more than one group.

{% hint style="info" %}
For general segment-building steps, see the Segments documentation in this guide.
{% endhint %}


---

# 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 dynamically 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/implementation-guide/integrations-and-data-exchange/custom-fields/segmenting-on-custom-fields.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 `build a script that syncs our docs to a CMS` 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.