Funnels

A funnel measures conversion through a sequence of events. You define an ordered list of step events, and Beacon computes how many actors reach each step within a configurable time window. Useful for onboarding flows, checkout sequences, or any multi-step process where you care about drop-off.

Prerequisites

• Plan: Funnels are available on Trial, Pro, Business, and Enterprise. Starter accounts see an upgrade prompt instead of the Funnels page.
• Permissions: view_funnels to see and run funnels; manage_funnels additionally to create, edit, or delete.

Create a funnel

In the sidebar, click Funnels, then New Funnel in the top-right.

Fill in:

For each step:

• Event name (required) — must match the name your SDK sends.
• Event category (optional) — if supplied, the step matches only events with this (category, name) pair. Leave blank to match the event name across any category.
• Label (optional) — friendly name shown in charts and tables instead of the raw event name.

Steps are ordered top-to-bottom. Drag the grip handle to reorder.

Click Create funnel to save. You’re navigated to the new funnel’s detail page.

Run the funnel

The detail page auto-runs the funnel against the last 30 days the first time you open it. Later visits restore the filters you used last (stored per-funnel in your browser).

The Filters panel controls:

• Source App — restrict to events from a single product. Defaults to the funnel’s stored default product, or blank.
• Time range — a preset or a custom date range.

Click Run Funnel to recompute. Computation is live (queries raw events on each request — no aggregation delay), so newly-fired events appear in results as soon as ingestion accepts them.

If the selected start date predates your plan’s retention window, a yellow banner appears:

Data before [date] has been purged per your plan’s retention policy.

Beacon silently clamps the start date to the earliest retained event — the funnel still runs, but only against the data available.

Read the results

Each step row shows:

• Actor count — distinct actors who reached this step.
• Conversion rate — actors at this step ÷ actors at step 1, as a percentage. Step 1 is always 100%.
• Drop-off — actors at the previous step who did NOT reach this step.
• Median time from previous step — median elapsed seconds from the previous step’s event to this one, across all actors who completed both. Blank for step 1.

Above the table, a completion indicator summarises the funnel: green check if any actors reached the final step, red if none did. A bar chart visualises the step counts.

Conversion window semantics

• Step 1 is the first occurrence of that event for each actor within your selected time range.
• Each subsequent step must occur after the previous step’s matching event AND within conversion_window_days of the step-1 anchor (not the previous step).

So a funnel with a 7-day window where step 1 fires on Monday will count step 4 only if it also fires by the following Monday. An actor who completes step 1 on Monday and step 4 on Tuesday-the-next-week is dropped.

Compare two periods

After Period A results render, click Compare to another period to reveal a second filter panel. Pick a date range; Source App inherits from Period A. The comparison table renders A and B side by side per step. Useful for A/B-style release comparisons (before vs after a launch, this quarter vs last quarter).

Common questions

The funnel times out. Computation has a 30-second budget. Narrow the date range, drop a step, or filter to a single product.

Step counts seem too low. Verify each step’s event name and (if supplied) category exactly match what your SDK sends. The match is case-sensitive. Check Event Explorer to see the names actually flowing through.

The conversion window is too tight (or too loose). Edit the funnel, change the window, and rerun.

Can I delete a funnel? Yes, from the edit page. Requires manage_funnels.

Next

→ Retention & Churn