Documentation
On this page

Create a website funnel

A funnel measures how website visits progress through a sequence, such as opening pricing, starting checkout and reaching a success page. Start with a short journey you can verify yourself.

To measure ordered events across an app install’s lifetime, create an app funnel.

Before you start

Install website tracking on the relevant hosts. Send any custom goals used by the journey. Funnel steps use existing page paths and event names; creating a funnel does not start sending those events.

Choose a starting point

  1. Open Settings → Events & funnels → Funnels → Add funnel.
  2. Expand Start with a template and choose Signup, Checkout journey, Download journey, or Blank funnel.
  3. Give it a recognizable Name. Templates are editable starting points: replace their example paths and event names with your own.

Wide funnel editor with badge 1 pointing to the Signup template and badge 2 to Name, above the first Page step.

Choose a template and name the funnel before adapting its steps to your website.

Define each step

  1. Choose Page or Goal under Kind. Enter the Page path, such as /signup, or the exact Event name, such as signup.
  2. Open Step options when needed. Step label changes the display name. Hostname (optional) restricts the step to one registered host. For pages, Equals matches one path; Starts with matches a prefix, so /docs also matches /docs/getting-started.
  3. Use Add step for additional steps. A funnel has 2–8 steps, and a product can save up to 20 funnels.

Wide funnel step editor with badge 3 pointing to Kind and badge 4 outlining Step label, Hostname and Page match set to Equals.

Select Page or Goal, then use Step options to set the label, hostname and path matching rule.

Review and save

  1. Use the reorder handle or a step's actions menu to arrange the actual journey. For keyboard use, use the available step actions.
  2. Open Funnel preview, check the ordered labels and choose Save.
  3. Choose View funnel results from the saved funnel and set the reporting dates. Read funnel results to interpret completion and drop-off.

Wide funnel draft with badge 5 outlining the Landing, Signup page and Signed up preview and badge 6 pointing to Save.

Review the ordered labels before saving. Funnel preview shows the definition, not measured conversions.

What the results mean

Steps must occur in order within the same website visit. Extra activity between steps does not by itself complete a step. A visitor returning in a different visit is not a continuation of the original journey. Imported daily totals cannot reconstruct individual ordered visits.

Automatic goals such as payment, free_trial and subscription_started can be funnel steps when the checkout helper links their verified provider record to an existing visit. The payment must happen after preceding steps. Unlinked completions stay in Goals and do not advance the funnel. An app install is not a browser funnel step; Jelto keeps website and app identities separate. An app event name used as a goal step is accepted by the API, but the app event never advances the website funnel; use an app funnel for an ordered app journey.

See two complete examples or troubleshooting.