> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/audience-and-activation/build-your-audiences/segment-reference/segment-types/experiment-groups-segment.md).
# Experiment groups segment
The test and control segments an experiment produces.
## What it is
An **Experiment group** segment is one of the groups produced when an experiment splits a source segment. Creating an experiment on a segment creates as many segments as the experiment has groups, and they appear in the segments list with the type `Experiment group`.
An experiment may have between 1 and 10 test groups, with or without a control group, and must end up with at least two groups in total.
The experiment itself - when to run one, how to configure randomisation, how the groups are named, how to read the result - is documented in the **Measurement & Attribution** section, under *Set up an A/B test*. This page covers only what the resulting objects are, as segments.
## Finding them
All segments created from experiments can be found from the segments menu with the filter `Segment type = Experiment groups`. See [The segments list](/audience-and-activation/build-your-audiences/segment-reference/segment-capabilities.md#the-segments-list).
## What this segment type does not decide
* **Its own population.** The group holds whatever the experiment's randomisation and addressability step gave it. A group smaller than you expected is an experiment question, not a segment question - see *Read and interpret your experiment results* in the **Measurement & Attribution** section.
## Related pages
Partition segment
The random split that simple randomisation draws on.
---
# 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://docs.mediarithmics.io/audience-and-activation/build-your-audiences/segment-reference/segment-types/experiment-groups-segment.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.