Skip to main content
A funnel shows where people drop off. Conversion insights suggest why. This guide builds a signup funnel from a page view to a custom event.

Before you start

  • Install the Web SDK, or send app events from a game.
  • Send your conversion steps as custom events, for example track('signup_started') and track('signup_completed'). See track.
  • Call identify() after signup, so a user who converts on a later visit counts once.

Part 1: Create the funnel chart

1

Open a dashboard

Open Dashboards and open a dashboard, or click Blank dashboard on the Dashboards page.
2

Add a funnel chart

Click Add chart. Pick the Signup funnel example, or click Blank chart and set the Chart type to Funnel.
3

Add the steps

Add two to five steps. For a page step, choose Page and enter a path such as /pricing. For an event step, choose Event and enter a name such as signup_completed.
4

Choose the order and window

Keep Sequential order for a linear journey. Choose a conversion window: 1 hour, 24 hours (default), 7, 14, 30 or 90 days.
5

Save

Click Save Chart.

Part 2: Read the results

Click a count on the chart to open the users behind that step or that drop-off. Click a user to open the profile and see what they did.

Part 3: Find out why people drop off

  • Break down the funnel by Channel, UTM Campaign, Device or Country in the chart header. Compare the conversion rate of each group.
  • Choose first touch or last touch for the breakdown value.
  • Limit the funnel to a saved segment, for example Pro users.
  • Open Conversion insights. The Events view lists the events that go with converting more or less often. The Event Properties view does the same for property values, such as platform=steam_deck or build=1.4.2. Click a row to see the counts behind it. Lift is correlation, not cause.
Lower counts than you expect? People may skip a step or do the steps in a different order. Remove a middle step, or switch to Any order.

Tips

  • Start with two or three steps. Add steps when the funnel works.
  • Use the same event name everywhere. signup_completed and Signup Completed are different events.
  • Send the last step from your backend with server events when the browser can close before the SDK sends it.