# Funnel Chart

The **Funnel Chart** component in **Lowcoder** is purpose-built to illustrate **step-by-step drop-off** in a process — like how users move through a sales or signup funnel. Its tapered shape clearly conveys **decreasing values**, helping identify bottlenecks and optimize flow efficiency.

#### Use Case Highlights

* **Sales Funnel:** Leads → Qualified → Proposal → Closed
* **Marketing Pipeline:** Visitors → Signups → Activations
* **Process Efficiency:** Applications received → Reviewed → Approved

#### Data Format Example

Each step in the funnel requires a **label** and a **numerical value**:

```json
[
  { "stage": "Visited Site", "value": 1000 },
  { "stage": "Signed Up", "value": 400 },
  { "stage": "Subscribed", "value": 180 }
]
```

#### Key Features

* **Automatic Sorting:** Values are typically displayed in descending order (largest at the top)
* **Visual Ratio:** Width of each segment is proportional to its value
* **Color Coding:** Customize segment colors to visually separate steps

***

#### Customisation & Tips

* Apply **tooltips** to show percentages or absolute values on hover
* Combine with **Bar/Line charts** for a broader picture of performance
* Use **ECharts JSON config** to enable label alignment, orientation, and segment gaps

### Component Playground

{% embed url="<https://app.lowcoder.cloud/playground/funnelChart/1>" %}

### Component Auto-Docs

{% embed url="<https://app.lowcoder.cloud/components/funnelChart>" %}


---

# Agent Instructions: 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:

```
GET https://docs.lowcoder.cloud/lowcoder-documentation/build-applications/app-editor/visual-components/dashboard-and-reporting/charts-and-graphs/funnel-chart.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.