> 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/segments/templates.md).

# Segment Templates

Save and reuse segment definitions with segment templates.

Segment templates let you reuse a segment definition when creating new segments. They are useful for standard audiences, recurring campaign criteria, and shared segmentation patterns.

## Create a segment template

You can create a segment template in either of the following ways:

* Build or open a segment in the Visual Builder, then select **Save as template**.
* Open the **Templates** area, choose **Segments**, and create a template from there.

When creating a template, provide a clear name and description so that other users can understand when to reuse it.

## Manage a segment template

From the Templates area, you can update a segment template's name and description. Keep template names specific to the audience or use case they represent.

## Create a segment from a template

When creating a segment, choose a segment template instead of selecting a parent model directly. DinMo opens the template definition in the Segment Builder, where you can review and adapt it before saving the new segment.

{% hint style="info" %}
Creating a segment from a template does not modify the original template.
{% endhint %}

For the general concept and future template types, see [Templates](/core-concepts.md#templates).


---

# 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/segments/templates.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.