> 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/overlap-analysis.md).
# Overlap Analysis
Overview
The Segment Overlap Analysis feature helps you identify the common population between two segments. This is crucial for two primary reasons:
* **Optimizing Activation Budgets**: Prevent unnecessary spending by avoiding targeting highly similar populations with separate campaigns.
* **Analyzing Rule Similarities**: Understand if different segmentation rules unintentionally capture the same audience, revealing hidden correlations.
{% hint style="warning" %}
Segments should **share the same parent model** to be eligible for overlap analysis.
{% endhint %}
You can see overlaps in different places: directly in the segment builder or once the segments have already been created.
## How to see Overlaps
### Directly in the Segment Builder
* Open the **Segment Builder**.
* Select or create a segment.
* Click on the *Overlap* tab.
* **Select comparison segment**: A list of segments with the same parent model will appear. Select the segment you want to compare.
* **View the overlap Analysis**: DinMo will generate a visual representation showing the overlap between the two populations.
### Once the Segments have been created
* **Navigate to your segment**: go to the Segments section in DinMo and click on the segment you want to analyze.
* **Access overlap analysis**: In the segment Analysis tab, click on the "Overlap" button.
* **Select comparison segment**: A list of segments with the same parent model will appear. Select the segment you want to compare.
* **View the overlap Analysis**: DinMo will generate a visual representation showing the overlap between the two populations.
---
# 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/overlap-analysis.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.
