Funnel evaluators (timeline vs last match)
An evaluator tells FunnelStory how to place an account on a workspace funnel’s stages when stage filters can be true at different times, overlap, or change as data updates.
This page applies to funnels in the Funnels section (/funnels). Product-level funnels use the same filter ideas for stages but refresh placement from current matches with last-match-style rules; see that guide for hierarchy-specific behavior.
Where you set it
When you create a funnel, pick Timeline or Last match in the create dialog. On an existing funnel, change it from Funnel Overview with the Evaluator dropdown (defaults to Timeline when unset).
Changing evaluator affects which filter types are available when editing stages—see Stage conditions.
Timeline (timeline)
What it does
- FunnelStory replays the account’s history (activities and other signals the funnel uses) in chronological order and drives a state machine so stages advance in sequence.
- Order matters: progression respects your stage order as the replay walks forward in time.
- Completed stages stick: once a stage is recorded as completed for that account, it remains completed even if the same filter would fail later (for example a usage metric drops after the account already qualified). That keeps the journey faithful to what actually happened.
- Current stage is the first stage that is not yet complete at evaluation time.
- When every stage has completed, the account is shown in the funnel’s Done state (the built-in completion stage).
When to use it
- Onboarding or strict sequences (“must complete A before B”).
- Motions where history matters more than “what would pass a filter if we only looked at today.”
- Reporting where you do not want accounts to “fall back” to an earlier stage just because a later-stage metric cooled off.
Stage filters
Only metrics, activities, and account properties are available—inputs compatible with historical replay.
Last match (last_match)
What it does
- FunnelStory does not run the full historical replay to decide where the account sits right now.
- It evaluates each stage’s filter against the account’s current data, then picks the rightmost stage in your order whose filter matches (the latest qualifying stage).
- If no stage matches, the account is not in the funnel for that evaluation. Unlike Timeline, there is no built-in Done state that means “finished every stage in order”—placement is always “rightmost stage that matches today.”
- If data changes so only an earlier stage’s filter matches, the account can appear to move backward relative to a strict historical story.
When to use it
- Stages represent current maturity or health (tiers, risk bands) where it is normal for an account to move up or down as metrics change.
- You want the funnel view to answer: “Which stage definition fits this account today?” not “What path did it take through time?”
Stage filters
The builder exposes the broader palette (signals, subscriptions, account metrics, funnel stage/state helpers, etc.) in addition to the timeline-compatible types.
Side-by-side
| Question | Timeline | Last match |
|---|---|---|
| Default if unset | Yes | No |
| Uses chronological replay | Yes | No |
| How “current stage” is chosen | First incomplete stage in order | Rightmost stage whose filter currently matches |
| Earlier stage already completed, later filter stops matching | Account can sit in next incomplete or Done; earlier completion stays | Account moves to whatever matches now (often an earlier stage if only that filter passes) |
| All stages satisfied in order | Done | Still based on rightmost match, not a special “finished” flag |
Product-level funnels (reminder)
Product funnels documented under Product-level funnels evaluate on refresh with current data and rightmost placement—the same placement rule as Last match here—even if a stored evaluator field is shown in configuration.