v.25.12New Feature

Add allow_reentry option to windowFunnel aggregate

Add allow_reentry option to windowFunnel aggregate function. When enabled with strict_order, it ignores events that violate the order instead of stopping the funnel analysis. This enables handling user journeys with refreshes (A->A->B) or back-navigation (A->B->A->C) without underreporting conversion rates. #86916 (Lee ChaeRok).
Added the allow_reentry option to the windowFunnel aggregate function, allowing it to ignore events that violate strict order instead of stopping the funnel analysis.

Why it matters

This feature solves the problem of underreporting conversion rates caused by user behaviors like page refreshes or back-navigation that produce out-of-order events (e.g., A->A->B or A->B->A->C). By enabling allow_reentry with strict_order, it improves funnel accuracy by continuing analysis despite order violations.

How to use it

Use the windowFunnel aggregate function with the strict_order parameter and enable the allow_reentry option to allow ignoring order violations. Example usage: windowFunnel(time_column, event_column, strict_order=1, allow_reentry=1).