> For the complete documentation index, see [llms.txt](https://docs.dinmo.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dinmo.io/guides/get-started-with-dinmo/create-and-activate-segments-on-dinmo/create-your-first-segment.md).

# Create your first Segment

A segment is a sub part of a model, which can be activated to destination platforms.

On DinMo, you need to create a segment in order to sync data to a destination platform.

To create a new segment, follow this setup sequence:

1. First, navigate to the Segment page and click on **“New segment”** on the upper right<br>

   <figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2Fgit-blob-9c177738fd4385d4ce8f930f43a2792ee19baf04%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>
2. Select the segment type you wish to create. It can either be a user segment, an event segment, or a custom segment.
3. Select your parent model of the segment, then put as many filters as you wish to create the target segment. Refer to [this page](/segments/visual-builder.md) for more information on the visual builder features.\ <br>

   <figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2Fgit-blob-343896b1aaf59e2279b14bf3b2d2d9875993c6a1%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>
4. Preview the data, and hit Continue if you are satisfied with your segment.<br>
5. Name your segment, add a short description to simplify the navigation.\ <br>

   <figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2Fgit-blob-b62bb06d63e1dea3432844945161566e993a2466%2Fimage.png?alt=media" alt=""><figcaption></figcaption></figure>
6. Hit "Create".

## Review segment insights

After creating a user segment, open its overview to review how its size and daily turnover change over time.

Use the **1d**, **7d**, **14d**, or **30d** selector to choose the reporting period. The insight metrics and chart update to match the selected range.

<figure><img src="https://3204318043-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxzBTp1t4OfqV67nXkVse%2Fuploads%2FbCcVhuZJcyE7QEJLY0TX%2F121-075436d0772d61ced013861a67d55dd0cf6ce14c.png?alt=media&amp;token=643ceda6-1c69-471a-ba95-31e691c2a21a" alt=""><figcaption></figcaption></figure>

The chart begins on the first date in the selected range that contains data. A recorded value of zero is displayed; missing dates before the first observation are omitted.

Congrats, you’ve created your first segment! You are now ready to sync it to your preferred destination platforms.


---

# 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.dinmo.io/guides/get-started-with-dinmo/create-and-activate-segments-on-dinmo/create-your-first-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.
