Funnels
Funnels show how many players move from one event to the next. Use them for onboarding, store checkout, quest progression, or any sequence where drop-off matters.
How a funnel is defined
Section titled “How a funnel is defined”A funnel is an ordered list of steps. Each step is an event with optional property filters.
| Part | Meaning |
|---|---|
| Step order | Steps are evaluated in order, starting at 1. |
| Event | A built-in or custom event name. |
| Property filters | Narrow a step by event properties using eq, neq, gt, gte, lt, lte, contains, or in. |
| Time window | The maximum time allowed between consecutive steps. |
| Scope | Organization-wide, or specific to one server. |
Common time windows are 15 minutes, 30 minutes, 1 hour, 2 hours, 6 hours, 12 hours, 24 hours, 7 days, and 30 days. The default is 1 hour.
Creating a funnel
Section titled “Creating a funnel”- Open Funnels and create a new funnel.
- Name it, choose its scope, and set the time window.
- Add steps in order and attach property filters where needed.
- Review the definition, then save.
- Open the funnel to analyse results.
Reading results
Section titled “Reading results”- Users per step: distinct players who reached each step.
- Conversion rate: the percentage of step-1 players who reached the step.
- Drop-off rate: the percentage lost between the previous step and this one.
- Overall conversion: the share of players who completed the final step.
The analysis view adds a date range, a period grouping (day, week, or month), a conversion trend chart, and narrative insights that call out the largest drops.
Choosing events
Section titled “Choosing events”Funnels work best when the steps are stable, discrete events. If you are tracking a custom flow, send events through the Developer API and keep names consistent across releases.
Funnels can be organization-wide or server-specific. Organization funnels consider players across the selected servers; server funnels restrict analysis to that server’s sessions.