GamebeastDocs
Dashboard

Funnels

See how many players get through a series of steps, where they drop off, and how long you give them to convert.

A funnel follows players through a series of steps, such as logging in, finishing the tutorial, opening the shop and buying something, and shows how many reach each one. The gap between two steps is where players drop off, so a funnel tells you which step to fix first.

1
2
3
4
5
Conversion criteria
By
InteractiveChange the steps, the conversion window and the advanced options, and break the funnel down by platform. Hover the chart to see each step's conversion. The players are made up.

Funnels are built from the markers your experience already sends, so you can build one for any period you have data for without adding new events.

How a funnel is counted

Four rules cover every funnel:

  1. Players are counted, not events. Each player is counted once, at the furthest step they reached. Step 3 is the number of players who reached at least step 3.
  2. Steps happen in order. A step only counts when it comes after the step before it. A player who bought something and then opened the shop hasn't reached "opened the shop, then bought".
  3. Steps happen inside the conversion window. The window starts at the player's step 1. A step after the window ends doesn't count.
  4. The best attempt wins. A player who started the funnel more than once is counted at the furthest step any attempt reached.

For example, take the funnel Login → TutorialCompleted → ShopOpened. A player who logs in and finishes the tutorial on Monday, then opens the shop on Wednesday, reached step 2 with a 1-day window and step 3 with a 7-day window.

Creating a funnel

Open a dashboard, click Edit, then Add panel → Query, and select Funnel from the query types at the top of the query setup.

  1. Pick the steps. Choose an event for each step. A funnel has at least 2 steps and up to 32. Click Steps to add another, and drag a step by its grip to reorder it.
  2. Filter a step if only some of its events should count, with the filter icon on the step or Filter in its ⋯ menu. For example, "Purchase where ItemName is Starter Pack". See local filters.
  3. Name a step with Edit display name in its ⋯ menu. The name labels the step on the chart. Without one, the chart uses the event's name.
  4. Set the conversion window under Conversion criteria.

The chart updates as you go. The same event can be used for more than one step: Login, then Login counts the players who came back for a second session.

Conversion criteria

Conversion window

Within 7 days by default. Click it to choose how long a player has, from their first step, to finish the funnel: any number of seconds, minutes, hours, days, weeks or months. A month is 30 days.

Pick a window that matches the question. A tutorial takes minutes, so a 7-day window also counts players who quit the tutorial and came back days later to finish it. A first purchase can take longer than a day.

Allow steps between

On by default. Open Advanced beside Conversion criteria to change it.

Allow steps betweenA player converts when…Use it for
Onthey did each step after the one before it, whatever else they did in between.Almost every funnel.
Offthey did each step with no other event at all in between, from any marker.Steps that should happen back to back, such as two screens in a menu.

Off is strict: a single click or heartbeat marker between two steps ends the player's funnel at the step before it. Try it in the demo above, where players send clicks and start matches between steps.

Any order is also listed under Advanced. It doesn't let players do the steps out of order: steps are always counted in the order they're listed.

Holding a property constant

Advanced → Holding property constant… adds a property that must have the same value on every step. A player whose steps disagree on it isn't counted at all. Use it when every step must be about the same thing:

  • ItemId, so viewing an item and buying it are about the same item.
  • QuestId, so starting and finishing a quest are about the same quest.
  • Platform, so a player who started on mobile and finished on PC is left out.

You can hold more than one property constant. A player is left out if any of them changes.

Reading the chart

Each column is a step, sized by the number of players who reached it. The label above it shows that number and, from step 2 on, the share of the step before that continued. Hover any part of the chart to see:

  • Step conversion: the share of players at the previous step who reached this one.
  • Overall: the share of players at step 1 who reached this one.

Look for the biggest drop in step conversion, not the smallest final number. A 40% drop between the tutorial and the shop says more about your game than the drop at the purchase step that every game has.

Chart types

Pick the chart from the controls above the preview.

ChartShows
Funnel StepsOne column per step, with breakdown values side by side and each step's drop-off above its column. The default.
Stacked Steps (Beta)The chart in the demo above: breakdown values stacked in one column per step, with ribbons from each step to the next.
SankeyPlayers flowing from each step to the next, with the players who dropped off flowing into a drop-off node under every step.
Funnel Table (Beta)One row per step with Step Completion, Churn and Total Conversion, and a row per breakdown value under each step.

Filters

Where you put a filter decides what it limits:

Filter onLimitsExample
A step (local filter)Which of that event's occurrences count.Only purchases of the Starter Pack count as the last step.
Global Filters (global filter)Every step.Only events from mobile.

A global filter on an argument or property only works if every step's event has it. If they don't, filter the step that has it.

To follow a group of players rather than a kind of event, add a New User filter (the User tab of the filter picker) or filter by a cohort.

Breakdowns

A breakdown splits the funnel by a property, argument, cohort or experiment, with one column, segment or row per value.

  • Each value is its own funnel. A player's events are split by the value each one had, and each part is counted on its own. A player who started on mobile and finished on PC reached step 1 on mobile, and no step on PC.
  • The chart shows the 5 largest values to start with. Click a value in the legend to show or hide it.
  • A limit keeps the largest groups, ranked by their step 1 events. The rest are combined into Other.

Breaking down by an experiment is the quickest way to see whether a variant changes conversion, and at which step.

Using a funnel elsewhere

  • In a cohort. A funnel condition matches the players who completed a saved funnel, or reached one of its steps, so you can target them with an experiment or follow them in another query.
  • On a dashboard. Save a funnel like any other query; see Saving a query.
  • As data. Funnel charts can't be exported from the dashboard. Run the funnel with Execute funnel query to get each step's numbers as JSON.

Tips

  • Start with 3 to 5 steps, find the biggest drop, then add steps around it to see exactly where players leave.
  • Set the window to how long the steps should take, not the longest you can. A long window hides players who got stuck and came back later.
  • Use a step filter rather than a global one when only one step needs it.
  • Leave Allow steps between on unless the steps really happen back to back.
  • Not sure which steps to use? Build a user journey from your first step to see what players actually do next.

With the assistant

Ask the assistant things like "where do players drop off between the tutorial and their first purchase?" or "does the new shop layout convert better on mobile?". It builds the funnel, shows the chart in the chat, and can open it in the query builder or add it to a dashboard. Agents connected over MCP can build, run and save funnels too.

With the API

Run a funnel from your own tools with Execute funnel query. Each step comes back with its player count and its conversion from the step before, for each breakdown value.

On this page