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

# Funnel

## Overview

Funnel measures how users move through a defined series of actions and where they drop off. Use it to quantify conversion rates and time‑to‑convert across onboarding, checkout or any multistep flow.

***

## Common Use Cases

* **Onboarding**: Sign‑up → Email Verify → First Action
* **Ecommerce**: Product View → Add to Cart → Checkout Started → Purchase
* **Marketing**: Ad Clicked → Landing Page View → Sign‑up
* **Upgrade funnel**: Free Trial → Key Feature Used → Paid Plan

***

## Interface Walkthrough

| Setting                  | Purpose                                                       |
| ------------------------ | ------------------------------------------------------------- |
| **Steps 1 → N**          | Each step is one or more events. Order matters.               |
| **Aggregate By**         | Count *Unique users* or *Unique sessions*.                    |
| **Conversion Window**    | Max time from first to last step (mins / hrs / days).         |
| **Date Range**           | Period in which Step 1 must occur.                            |
| **Measure time between** | Unit for the “average time” stats (seconds, minutes, hours…). |
| **Conversion calc.**     | *Overall* (versus Step 1) or *Step‑by‑step*.                  |
| **Global Filters**       | Narrow the cohort (e.g. Device = Mobile).                     |

***

## Quick Example (Step Checkout)

1. Steps: ① Product Viewed ② Add to Cart ③ Purchase
2. Aggregate By: *Unique sessions* | Window: *Within 3 days*
3. Date Range: *Last 30 days* | Time between: *hours*
4. Run → Chart shows counts, % drop‑off, and avg hours between steps.

   *Interpretation:* if big churn between Add to Cart and Purchase, improve checkout UX.


---

# 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://userflux.gitbook.io/userflux-docs/feature-guides/analytics/insights/funnel.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.