> 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/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects/user-segment.md).

# UserSegment

The record that says a user belongs to an audience segment, and the information it carries.

## Your goal

Know what segment membership looks like on a user, so you can read it on a UserPoint and query it.

## Expected outcome

You can tell an audience segment apart from the UserSegments it produces, and you know which information each UserSegment carries.

## What a UserSegment is

An [audience segment](https://docs.mediarithmics.io/audience-and-activation/build-your-audiences/segment-reference.md#what-an-audience-segment-is) is a group of users. A **UserSegment** is the piece of information attached to a user to say they belong to that segment: a segment of 10,000 users means 10,000 UserSegments, one per user. A UserPoint carries one UserSegment per segment the user belongs to.

In the schema, this information is an object of type `UserSegment`, which holds:

* The segment identifier.
* The date the user entered the segment, which is the creation date of the UserSegment.
* The expiration date at which the user exits the segment. It is optional, and set only for some segment types.

## Segments themselves

How segments are built, and what each type does, is documented in:

* [Persisted segment](https://docs.mediarithmics.io/audience-and-activation/build-your-audiences/segment-reference.md#persisted-segment) explains why a segment can show a count before its UserSegments exist.
* [Segment types](https://docs.mediarithmics.io/audience-and-activation/build-your-audiences/segment-reference/segment-types.md) lists the types of segment and what each one decides.

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Import segments</strong></td><td>Add users to a segment, or remove them, from a file of identifiers.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/import-data-in-batch/import-segments.md">Import segments</a></td></tr><tr><td><strong>Schema definition</strong></td><td>The default objects, including <code>UserSegment</code>.</td><td><a href="https://docs.mediarithmics.io/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/schema-definition.md">Schema definition</a></td></tr></tbody></table>


---

# 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/setup-and-monitor/collect-and-manage-your-data/design-your-data-model-and-schema/understand-mediarithmics-standard-objects/user-segment.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 `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.
