Future InTech
Language · English

Measurement and interpretation · FIELD GUIDE

Funnel time windows: test consecutive steps, not total duration

Check step order and each interval before diagnosing an unexpected funnel drop-off in Umami.

By Future InTech · Published
Evidence cutoff: 2026-11-04T01:45:44.105842+00:00 · UTC

What the evidence can establish

A list of visited pages is not enough to evaluate an ordered funnel. Umami requires the steps in the specified order and allows other activity between them. Its documented window is the maximum interval between consecutive funnel steps. Confusing that rule with the total start-to-finish duration changes which journeys should qualify.

Hypothetical 30-minute window: A at 09:00, B at 09:20 and C at 09:40 has two 20-minute gaps. The total duration is 40 minutes, but neither consecutive gap exceeds 30. A second journey with B at 09:35 fails the first interval. These are arithmetic test fixtures, not observed conversion data.

Match the ordered steps; Calculate each adjacent gap; Test one failing interval; Explain the exclusion
Original explanatory diagram based on the dated sources below. Any example values are hypothetical; this is not a screenshot, customer measurement or AI platform result.

The saved evidence used here

This guide interprets dated official documentation. It does not report traffic from a customer or a measured AI answer. Each material claim is mapped to a source below.

c1 · Explanation and verification steps
Umami requires ordered funnel steps but permits other activity between them. Source 1
c2 · Explanation and verification steps
The funnel window applies between consecutive steps. Source 1
c3 · Explanation and verification steps
Funnel steps can use URLs, events and supported URL wildcards. Source 1

The diagram explains the investigation or a clearly labeled hypothetical example. No measured counts or platform outcomes are added.

AI answer visibility: Not measured. No original platform answers or verified citation records were collected for this guide. A request count is not an audience, ranking or citation count.

What to do next

  1. Record the ordered step definitions, including whether each matches a URL, an event or a supported wildcard.
  2. Save timestamps for an authorized test journey and calculate the interval from each matched step to the next. Keep unrelated intermediate activity visible.
  3. Test a valid sequence, an out-of-order sequence and a sequence with one interval beyond the window. Use the same filters for all three.
  4. If a production drop-off remains, inspect the actual matched events before changing the window. A broader window changes the question being measured.

How to check the result

The test table should identify the first failed condition for each journey: wrong step, wrong order or excessive consecutive interval. State the configured window next to any funnel conversion rate.

Limits of this conclusion

These documented rules do not establish an observed funnel result. Boundary behavior at an exact cutoff should be tested in the installed version rather than guessed.

This is a saved, dated edition. Source documentation can change. This edition retains the original retrieval dates and claim mapping; follow the sources before applying version-specific guidance.

Sources and publication checks

Automated checks validate source availability, supported fields, duplicate wording, numeric figures and page configuration. This guide was prepared with AI assistance and checked against saved source passages in the same authoring session. The batch importer checks source fingerprints, quotation locations, wording overlap and required fields. No paid generation API or separate model-review pass was used for this batch. These checks can miss errors and are not expert or human review.

Funnel

Obtained: 2026-11-04T01:45:44.105842+00:00
Location: Choose your steps # / b7; Funnel / b3; Parameters # / b4

Saved source fingerprint9a528e7367d5c0b620bc194cef873c080436db273f28fb9df25b0323f9661ee8

Download this edition's evidence and action record (JSON)