> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/enterprise-analytics/introduction-to-segmentation-report.md).
# Introduction to Segmentation Report
A Segmentation Report is one of the two report types available inside Enterprise Analytics on DoubleTick. It is designed to help businesses **analyze performance metrics over a selected time period, with the ability to slice and filter that data by different dimensions** such as team members, WhatsApp numbers, or reporting managers.
Think of a Segmentation Report as your day-to-day performance lens. It answers questions like:
How many new chats did we receive this week?
How quickly are agents responding?
Which templates are being read?
How are calls being handled across the team?
You define what you want to measure, set a time period, and the report gives you a structured view of that data — broken down in a way that is most useful to your business.
***
#### **How is a Segmentation Report different from a Funnel Report?**
A Segmentation Report focuses on **measuring and monitoring metrics** over time. It is built for ongoing performance tracking — you use it to understand trends, evaluate team activity, and surface issues as they develop.
A Funnel Report, on the other hand, focuses on **tracking a sequence of steps and measuring conversion at each stage**. It is built for understanding how customers move through a defined process and where they drop off.
If you want to know how your team is performing day to day, use a Segmentation Report. If you want to understand how customers are progressing through a specific flow, use a Funnel Report.
---
# 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://learn.doubletick.io/enterprise-analytics/introduction-to-segmentation-report.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.
