Funnels & bottlenecks

Build a funnel#

Create 2–8 named steps. Each step matches either a pageview path or a custom event name. Choose a conversion window appropriate to the journey; the API supports 60 seconds to 30 days, defaulting to one day for ad-hoc queries.

Example: landing page / → pricing page /pricing → event signup_complete. Confirm each path and event is actually collected before interpreting the result.

Save or query#

Saved funnels retain their definition for the dashboard. query_funnel evaluates a sequence without saving it and only needs read access. Creating or editing a saved funnel needs member access and write permission through the API.

Read the steps#

Compare the number reaching each step and the drop-off between steps. Funnel steps are ordered and bounded by the conversion window, so a simple count of each independent event will not necessarily match the funnel. Compare the same dates and filters before making a change.

Diagnose empty steps#

Check exact event names, sanitized paths, traffic filters, timezone and conversion window. Private or excluded pages do not contribute permitted pageviews. A missing step can be an instrumentation problem rather than user abandonment.

API example#

{
  "range": "30d",
  "steps": [
    { "name": "Pricing", "type": "pageview", "value": "/pricing" },
    { "name": "Signup", "type": "event", "value": "signup_complete" }
  ],
  "windowSeconds": 86400
}

Use query_funnel, list_funnels or analyze_funnel_bottlenecks. Create, update and delete references are in the tool catalog.