> For the complete documentation index, see [llms.txt](https://closingdealz.gitbook.io/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://closingdealz.gitbook.io/product-docs/features/analytics/overview.md).

# Overview

### **Overview**

The **Overview Analytics** page in **ClosingDealz** provides a **high-level summary** of your key sales and performance metrics. It allows you to track essential sales data, monitor trends, and analyze individual or team-wide performance over a selected period.

With **custom date selection, team member filtering, and dynamic charts**, this page ensures that you always have a clear snapshot of your sales pipeline and progress.

***

### **Key Features**

**Custom Date Range** – Set a specific time frame to analyze performance over days, weeks, or months.\
**User Selection** – Filter metrics by individual team members or view overall team performance.\
**Real-Time Metrics** – Instantly updated data reflecting the latest deal movements.\
**Customizable Charts** – Select from various metrics and toggle cumulative mode for progressive tracking.

***

### **Available Metrics (Displayed as Tiles)**

The Overview page displays **key performance indicators (KPIs)**, including:

* **Value Closed** – The total revenue generated from closed deals.
* **Value Lost** – The total value of lost deals.
* **Average Deal Size** – The average value of all closed deals.
* **Close Rate** – The percentage of closed deals out of total lost and closed deals.
* **Created Leads** – The total number of leads created.
* **Created Deals** – The total number of deals created.
* **Closed Deals** – The total number of deals successfully closed.
* **Lost Deals** – The total number of deals lost.

***

### **Chart Visualization**

The interactive **chart** allows users to visualize trends over time for selected metrics.

* **Chart Metric Selection** – Choose from:
  * Value Closed
  * Value Lost
  * Average Deal Size
  * Close Rate
  * Created Leads
  * Created Deals
  * Closed Deals
  * Lost Deals
* **Cumulative Toggle** – Enable cumulative mode to display a progressive total over time instead of daily values.

***

### **How to Use the Overview Page**

1. **Set the Date Range** – Select the period for which you want to view metrics.
2. **Choose a Team Member** – View performance for a specific user or analyze overall team stats.
3. **Review Key Metrics** – Analyze the summary metrics displayed at the top.
4. **Use the Chart for Trends** – Select a metric from the dropdown and toggle cumulative mode if needed.

***

### **Why Use Overview Analytics?**

* **Track Performance at a Glance** – Get a quick summary of sales trends.
* **Measure Individual vs. Team Output** – Compare team-wide stats with individual performance.
* **Identify Growth Opportunities** – Use historical trends to optimize your sales strategy.

The **Overview Analytics** page is designed to **simplify reporting and decision-making**, helping you stay on top of your business with **data-driven insights**.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://closingdealz.gitbook.io/product-docs/features/analytics/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.