Funnel reports show how users move through a sequence of events. Use them to understand where users complete a flow and where they drop off.


Create a funnel

  1. Open Analytics.
  2. Choose a project and board.
  3. Select New chart.
  4. Choose Funnels as the report type.
  5. Select at least two events as funnel steps.
  6. Add more steps if needed.
  7. Save the chart to your board.

Configure funnel steps

Each step is an event. You can reorder steps by dragging them, add more steps, and remove steps when they are no longer part of the flow.

Common funnel examples include:

  • Signup started to email verified to profile completed.
  • Trial started to feature used to upgrade clicked.
  • Product tour viewed to checklist started to checklist completed.
  • Checkout started to payment submitted to purchase completed.

Filter funnel data

Use filters to narrow the funnel to a specific audience, property, or behavior. Filters can be applied to individual steps or to the whole chart.

For example, you can filter a signup funnel to users on a specific plan, country, campaign, or app version.


Add a breakdown

A breakdown splits the funnel by a property. Use breakdowns to compare conversion across groups such as plan, country, device, campaign, or account type.


Read the result

The funnel chart shows each step with the number of users or events that reached it and the percentage that continued. Look for the step with the largest drop-off first, then inspect that part of the product experience.

Example: measure activation from signup to first value

Start with a concrete definition of activation. For a collaborative product, that might be “created a first project and invited a teammate,” rather than merely opening a dashboard.

  1. Define the successful application action behind each step: account created → first project created → teammate invited.
  2. Create matching code actions and track them at the successful completion of those actions. Treat names such as project_created as examples to configure, not built-in Userorbit events.
  3. Verify the three events with a synthetic user in Live Events.
  4. Create a funnel with those events in order, using one project and a date range containing the test.
  5. Check the largest drop-off. Compare an available relevant property, such as a verified plan attribute, only if that property is actually present in the data.

A low final conversion can indicate a product problem or an instrumentation problem. Before changing onboarding, check whether the last action fires after success, whether the same stable user identity is used across steps and whether filters exclude the expected users. If you use replay to investigate, inspect only recordings collected under your configured privacy and access controls.

Keep the activation definition and tracking keys with your team's tracking plan so later changes do not silently change the meaning of the chart.

Was this helpful?