Skip to main content

​
Overview

Funnels show how many users move through an ordered sequence of events—signup → setup → first success, or trial → upgrade. They expose drop-offs and time-to-convert for agentic and SaaS journeys.

​
Use cases

  • What % of signups reach first successful agent run?
  • Where does onboarding lose the most users?
  • Mobile vs. desktop conversion
  • Free → paid paths
  • Trial start → subscription
  • Users who try templates vs. custom workflows
  • Depth after a key unlock event

​
Quick start

1

Define steps (in order)

Step 1: page_view (e.g. landing)
Step 2: signup_completed
Step 3: integration_connected
Step 4: agent_run_completed
Each step must occur after the previous within your conversion window.
2

Set conversion window

e.g. 1 day, 7 days, 30 days — users must finish all steps inside this period.
3

Choose measurement

Conversion rate, counts per step, or time between steps (where available).
4

Filter and break down

By campaign, plan, device, or custom properties.

​
Structure

​
Ordered steps

Order matters: intermediate steps cannot be skipped in the defined sequence (exact behavior follows your workspace funnel settings).

​
Conversion window

If the window is 7 days, a user who completes step 1 on day 1 but step 4 on day 10 typically does not count as converted.

​
Measurements

  • Overall conversion: Users who completed all steps ÷ users who entered step 1
  • Step-to-step: Drop-off between adjacent steps
  • Time to convert: Latency between steps or total duration

​
Filters

Global filters apply to all steps (e.g. country = US). Step filters restrict a single step (e.g. step 1 uri = "/pricing"). User property filters limit who is eligible (e.g. plan = pro).

​
Breakdowns

Compare conversion by utm_source, plan, device_type, or event properties like workflow_id.

​
Examples

​
Signup → first value

  1. signup_completed
  2. workspace_created (or your setup event)
  3. agent_run_completed with outcome = success

​
Upgrade funnel

  1. pricing_page_viewed
  2. checkout_started
  3. subscription_upgraded

​
Best practices

  • Keep step names stable; use properties for variants (don’t create one funnel per template unless needed).
  • Pick a window that matches real buying or activation cycles.
  • Name funnels after the decision they support (e.g. “7d activation v2”).

​
Next steps

Flows

Explore paths without fixing order

Filters

Filter reference