> For the complete documentation index, see [llms.txt](https://docs.caraml.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.caraml.dev/user-guides/01_getting_started-1/16_viewing_custom_segmenters.md).

# Viewing Custom Segmenters

Once the segmenter has been created, you will be able to view the segmenter's configuration on the list page. ![View Segmenter](/files/w5wVKzluA0YRS0nG7B1P)

## Navigate to Segmenter Details

1. Click on the row that contains the segmenter.
2. You will now be able to see the Segmenter Details View. ![View Segmenter Details](/files/mwCu8Atg8rx2Ci4WexHn) At the top row, you will be able to see your segmenter name.

### Configuration

The Configuration tab displays the selected segmenter's details, configured when creating or editing a segmenter.

1. General Info: General settings of the segmenter.
2. Activity: Activity details of segmenter.
3. Options: Options of segmenter.
4. Treatment Request Fields: Experiment variables to be supplied in the `FetchTreatment` request.
5. Constraints: Constraints of segmenter.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.caraml.dev/user-guides/01_getting_started-1/16_viewing_custom_segmenters.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.