> For the complete documentation index, see [llms.txt](https://docs.pinot.apache.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pinot.apache.org/functions/funnel.md).

# Funnel Analysis Functions

Apache Pinot supports a few funnel functions:

## Null handling

When [advanced null handling](/build-with-pinot/querying-and-sql/sql-syntax/null-value-support.md#advanced-null-handling-support) is enabled, funnel functions ignore rows whose timestamp is null. `FUNNELCOUNT` also ignores a row when any `CORRELATE_BY` column is null. Null step predicates are treated as not matched, while null optional extra fields do not discard an otherwise matched event.

With advanced null handling disabled, Pinot continues to read each column's configured default null value.

## FunnelMaxStep

`FunnelMaxStep` evaluates user interactions within a specified time window to determine the furthest step reached in a predefined sequence of actions. By analyzing event timestamps and conditions set for each step, it identifies the maximum progression point for each user, ensuring that the sequence follows the configured order or other specific rules like strict timestamp increases or event uniqueness. This function is instrumental in funnel analysis, helping businesses and analysts understand user behavior, measure conversion rates, and identify potential drop-offs in critical user journeys.

{% content-ref url="/pages/YMJLGM2ZH4GvZGPG52Sn" %}
[FunnelMaxStep](/functions/funnel/funnelmaxstep-1.md)
{% endcontent-ref %}

## FunnelMatchStep

Similar to `FunnelMaxStep` , this function returns an array which reflects the matching status for the steps.

{% content-ref url="/pages/9Tj5H4koZaXVKSLRRQEu" %}
[FunnelMatchStep](/functions/funnel/funnelmaxstep-2.md)
{% endcontent-ref %}

## FunnelCompleteCount

This function evaluates all funnel events and returns how many times the user has completed the full steps.

{% content-ref url="/pages/4d1PLIzFTTCsryhf3ZHy" %}
[FUNNELCOMPLETECOUNT](/functions/funnel/funnelcompletecount.md)
{% endcontent-ref %}

## FunnelCount

This function evaluates funnel steps and returns the distinct correlated counts for each step.

{% content-ref url="/pages/vSoNQfkz44AT5QUVpvhQ" %}
[FUNNELCOUNT](/functions/funnel/funnelcount.md)
{% endcontent-ref %}

## Additional Reference Pages

* [funnelmaxstep.md](/functions/funnel/funnelmaxstep.md)
* [FUNNELSTEPDURATIONSTATS](/functions/aggregation/funnelstepdurationstats.md)
* [FUNNELEVENTSFUNCTIONEVAL](/functions/aggregation/funneleventsfunctioneval.md)


---

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pinot.apache.org/functions/funnel.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.