> ## Documentation Index > Fetch the complete documentation index at: https://learn.kubit.ai/llms.txt > Use this file to discover all available pages before exploring further. # Funnel report > Measure how users, sessions, traces or spans move through an ordered sequence of events in a Kubit Funnel report, and where they drop off. A Funnel report measures how subjects (users, sessions, traces or spans) move through an ordered sequence of events, and where they drop off. This page covers the subject, the three modes, steps and their options, and extended time. It ends with how to ask the Kubit MCP server for a funnel. ## When to use | Use case | Example | | - | - | | Conversion optimization | Measure drop-off from product page to add to cart to checkout to purchase, to find where buyers abandon | | Onboarding analysis | Track sign-up, email verification, profile setup and first action, to find the onboarding step that loses the most users | | Feature adoption | See how many users who see a feature go on to use it again: feature impression, first use, second use | | Content or search quality | Measure search, result click and content engagement, to see whether search results lead to engagement | | Support resolution | Track ticket opened, agent assigned, first response and resolution, to measure support speed | | AI agent evaluation | Measure prompt, intent classification, tool call and successful response, to find the stage of an AI workflow that fails most often | Pick the mode by the question you're asking: | You want to know | Mode | | - | - | | What percentage makes it through each step | **Conversion** | | How many attempts it takes before a subject converts, such as searches before a purchase | **Frequency** | | How long each transition takes, such as sign-up to first purchase | **Time to Convert** | ![Funnel report builder with Subject set to User, Mode set to Conversion, and three steps joined by Sequence, next to a bar chart of four execute\_tool steps converting from 100% to 94.8%.](https://mintcdn.com/kubit/9i8QHxqek50tMBGy/images/reports/funnel/funnel-report.png?fit=max\&auto=format\&n=9i8QHxqek50tMBGy\&q=85\&s=bb6dcff8d2903c1ed707533f31e1c558) ## Subject The subject is the entity that moves through the funnel. It sets the unit each step counts. ### How it works Every step counts the distinct subjects that completed the step's event. | Subject | Each step answers | Identified by | | - | - | - | | **User** | How many unique users reached this step? | User ID | | **Trace** | How many unique traces reached this step? | Trace ID | | **Session** | How many unique sessions reached this step? | Session ID | | **Span** | How many unique spans reached this step? | Span ID | Pick the subject that matches the level of detail you need. Use **User** to count the people who complete a workflow, or **Trace** to count the requests that make it through each stage. ### Subject and step order Each subject supports its own set of step orders (**Sequence**, **Exact** and **Any**, described in [Step order](#step-order)). When you change the subject, the order options change to match. ## Modes A Funnel report has three modes: **Conversion**, **Frequency** and **Time to Convert** (shown as **TTC** in the report builder). ### Conversion Conversion mode answers "How do subjects convert through each step?". It's the default. The chart shows a bar per step with the percentage of subjects that entered the funnel and completed that step. You can show absolute numbers and conversion rates, either step to step or relative to the first step. | Feature | Supported | | - | - | | Time granularity | Day, Week, Month, Quarter, Year, All Time | | Comparison | Yes | | Breakdown | Yes | | Cluster mode | Yes | | Bounce rate labels | Yes | ### Frequency Frequency mode answers "How many times did subjects trigger an event before moving to the next step?". The X axis shows frequency buckets, such as `1 time`, `2–5 times` and `6+ times`, instead of dates. | Feature | Supported | | - | - | | Time granularity | All Time only | | Comparison | No | | Breakdown | Yes | | Cluster mode | No | | Step selection | Pick the step transition to show | A funnel with N steps has N-1 transitions, and Frequency mode makes one measure per transition. You pick which one to show. [Frequency mode](https://learn.kubit.ai/product-analytics/reports/funnel/frequency-mode.md) lists its constraints. ### Time to Convert Time to Convert mode answers "How long does it take subjects to move between steps?". The chart shows time buckets, with the average and median time to convert drawn on top. You can show one step transition, or the whole funnel from first step to last. | Feature | Supported | | - | - | | Time granularity | All Time only | | Comparison | No | | Breakdown | Yes | | Cluster mode | No | | Conversion window | **Required** | | Statistics | Average and median | [Time to Convert](https://learn.kubit.ai/product-analytics/reports/funnel/time-to-convert.md) explains the buckets and constraints. ### Mode quick reference | | Conversion | Frequency | Time to Convert | | - | - | - | - | | X axis | Calendar dates | Frequency buckets | Time buckets | | Comparison | Yes | No | No | | Time granularity | Any | All Time only | All Time only | | Conversion window | Optional | Optional | **Required** | | Statistics overlay | No | No | Average and median | ## Steps Steps are the events a subject has to complete, in order, to move through the funnel. ### Define a step | Part | What it does | Required | | - | - | - | | **Event conditions** | One or more events that satisfy the step. With several events in one step, any of them counts (OR). | **Yes** | | **Filters** | Property filters that narrow which event occurrences count, such as `country = "US"` | Optional | | **Step name** | A custom label. Without one, steps are named `s1`, `s2` and so on. | Optional | ### Step limits | Constraint | Value | | - | - | | Minimum steps | **2** | | Maximum steps | **10** | A funnel always keeps at least 2 steps. With only 2 steps left, removing a step clears it instead of deleting it. ### Step order The order between each pair of steps sets how strictly the sequence is checked. Which orders you can pick depends on the [subject](#subject). | Order | What it checks | | - | - | | **Sequence** | The steps happen in order. Other events can happen in between. | | **Exact** | The steps happen in order, with no other tracked events in between. | | **Any** | All steps happened, in any order. | ### Duplicate a step **Duplicate Step** copies a step, with its event conditions and filters, and inserts the copy right after it. It's available while the funnel has fewer than 10 steps. ### Exclude events An excluded event is a negative condition. If the subject triggers an excluded event between the previous step and this one, the subject drops out of the funnel at this step. For example: users who viewed a product and then purchased, without viewing the returns policy page in between. | Constraint | Value | | - | - | | Excluded events per step | **5** at most | **Availability:** excluded events work only on the first step, or when the order before the step is **Sequence**. Changing that order to **Any** or **Exact** removes the step's excluded events. ### Conversion window A conversion window sets how long a subject has to complete a step after the previous one. A subject that takes longer counts as dropped off. Set it as a number and a time unit, such as `24 hours`, `7 days` or `2 weeks`. For example: users have to add to cart within 1 hour of viewing the product page. | Constraint | Value | | - | - | | Available on | Every step except the first | | Needs | An order other than **Any** before the step | | Required for | Time to Convert mode | ### Add, remove and reorder steps | Action | How | | - | - | | Add | Click **Add step** to add an empty step at the end, up to 10 steps | | Remove | Use the step's remove action. With only 2 steps left, the step is cleared instead. | | Reorder | Drag a step to a new position. Reordering always resets the first step's conversion window. | ## Extended time Extended time moves the end of the analysis window past the selected date range, so later steps have time to happen. Without it, a funnel counts only events inside the date range. A subject that starts the funnel near the end of the range may not have time to finish later steps, which makes conversion at later steps look lower than it is. ### How it works Events that complete later steps count even when they happen after the date range ends. Only subjects that entered the funnel inside the date range are included. For example, with a date range of January 1 to 31 and 7 days of extended time, events through February 7 count toward completing the funnel, but only users who entered in January are counted. [Funnel tips](https://learn.kubit.ai/product-analytics/reports/funnel/tips.md#extend-the-time-window) shows where to set it. ## Prompt Kubit through the MCP server With the Kubit MCP server connected, you describe the steps and what you want to learn, and the server builds the funnel. A good funnel prompt names: | Part | When to include it | | - | - | | Steps | Always. Separate them with `→` or "then". | | Subject | When it isn't **User** (trace, session or span) | | Mode | When it isn't **Conversion** (frequency or time to convert) | | Date range | Always | | Breakdown | When you want to split the funnel | | Filters | When you want to narrow the data | ### MCP prompt examples > "Show me a funnel from sign up to first purchase over the last 30 days" > "Create a funnel for search → product view → add to cart → checkout, broken down by device type, last 14 days" > "What's the average time to convert from prompt to tool call to response? Build a time-to-convert funnel with a 1-hour conversion window for the last quarter" > "Build a funnel from product view to purchase, excluding users who visited the returns page between steps, with 7 days extended time" ### How the server reads a prompt | You say | Kubit sets | | - | - | | `→` or "then" between events | Sequential steps | | Nothing about order | **Sequence** | | "in exact order" | **Exact** | | "in any order" | **Any** | | Nothing about mode | **Conversion** | | "frequency funnel" or "time to convert funnel" | **Frequency** or **Time to Convert** | | "by \[dimension]", such as "by country" or "by model" | A breakdown on that dimension | | "excluding users who \[event]" or "without \[event] in between" | An excluded event | | "within \[time]", such as "within 1 hour" | A conversion window | ## Related * [Funnel tips](https://learn.kubit.ai/product-analytics/reports/funnel/tips.md): duplicating steps, breakdown groups and extending the time window. * [Path report](https://learn.kubit.ai/product-analytics/reports/path.md): find a path first, then turn it into a funnel. * [Reports overview](https://learn.kubit.ai/product-analytics/reports/overview.md): the other report types. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.