Analyze a funnel
Send a POST request with your steps and a conversion window:- count — users who reached this step
- overall_rate — conversion from step 1 (0.0 to 1.0)
- step_rate — conversion from the previous step
- drop_off — users lost between this step and the previous one
Steps and filters
A funnel needs 2–10 steps. Each step is an event name, optionally with property filters:add_to_cart events where the category property equals "electronics". The other steps accept any matching event.
Step filter operators
| Operator | Aliases | Description |
|---|---|---|
eq | =, == | Equal |
ne | !=, <> | Not equal |
gt | > | Greater than |
gte | >= | Greater than or equal |
lt | < | Less than |
lte | <= | Less than or equal |
contains | like | Contains substring |
not_contains | not_like | Does not contain |
starts_with | Starts with | |
ends_with | Ends with | |
in | Value is in list | |
not_in | Value is not in list | |
is_set | isset | Field is not null |
is_not_set | isnotset | Field is null |
regex | ~ | Regex match |
properties. (e.g., properties.plan). Top-level fields like country or device_type use the field name directly.
Conversion window
Thewindow_seconds parameter sets the maximum time a user has to complete the entire funnel from their first step. Default is 604800 (7 days).
A user who triggers step 1 on Monday and step 3 on the following Sunday (within 7 days) counts as converted. A user who takes 8 days does not.
Breakdowns
Add abreakdown field to split funnel results by a dimension:
breakdown array, each group with its own step results and conversion rate:
Funnel trends
Track how conversion changes over time with the trend endpoint:minute, hourly, daily, weekly, monthly, quarterly, yearly.
What’s next
- Filtering — apply conditions, breakdowns, and comparisons to any metric
- Events — explore the events that power your funnel steps
- Boards — save funnel results to a board for ongoing monitoring
- Data queries API — full API reference for funnels and other metrics