---
title: Funnels | ReplayPilot Docs
description: Track how visitors move through a sequence of steps, and where they drop off.
canonical: https://replaypilot.com/docs/funnels
---

# Funnels | ReplayPilot Docs

Search docs…⌘KBrowse docs

Get started
- [Installation](/docs/getting-started)
- [What's new](/docs/whats-new)

Dashboard
- [Replays & the session player](/docs/replays)
- [Errors](/docs/errors)
- [Frustration signals](/docs/frustration)
- [Funnels](/docs/funnels)
- [Releases](/docs/releases)
- [Logs & network requests](/docs/logs)
- [Visitors](/docs/visitors)
- [Heatmaps](/docs/heatmaps)
- [Click map](/docs/click-map)
- [Cohort retention](/docs/cohorts)
- [Projects & project keys](/docs/projects)
- [Alerts](/docs/alerts)
- [Shared links](/docs/shared-links)

Integrations
- [Integrations](/docs/integrations)
- [MCP server](/docs/mcp-server)

Account & data
- [Billing & plans](/docs/billing)
- [Security & masking](/docs/security-masking)
- [Data retention & limits](/docs/retention-limits)
- [Team accounts](/docs/team-accounts)

# Funnels

Track how visitors move through a sequence of steps, and where they drop off.

## What a funnel is

A funnel is a named, ordered list of steps you define. Each step is an event name. A funnel needs at least 2 steps, and can have up to 4.

A funnel shows you how many sessions made it from one step to the next, and where the biggest drop happens.

## How a step matches

Steps match against custom events you send with the snippet's track() call. [Install the snippet](/docs/getting-started) covers how to call track(eventName, props) from your own code.

For example, if your code calls:

ReplayPilot.track('signup_started')
ReplayPilot.track('signup_completed')

you can build a 2-step funnel out of signup_started and signup_completed.

Matching looks at the whole event name, not a loose substring. An event named signup_clicked won't count as a match for a step named signup. An event named signup extra-detail will, because the extra detail comes after a space, not stuck onto the word itself.

While you type a step name, the builder suggests event names ReplayPilot has seen on your project recently. You don't need to remember exact spelling.

## Sessions vs. visitors

By default, a funnel counts sessions: each recording that reached a step counts once. Switch to visitors mode and it counts distinct identified people instead. See [Visitors](/docs/visitors) for what "identified" means. Changing the mode recalculates any visible results immediately, and ReplayPilot never relabels the previous mode's counts.

## What gets saved, and what doesn't

ReplayPilot saves the funnel's definition, its name and step list, and nothing else. Every time you open a saved funnel, it recalculates from scratch.

## The 1,000-session window

ReplayPilot computes a funnel live, over your project's most recent 1,000 sessions, each time you view it. No pre-computing, no caching.

This matters for high-volume projects: once your project has more than 1,000 recent sessions, a funnel shows you a recent slice, not your complete history. If you need a longer view, run the funnel again later. The window always covers your latest activity.

## What funnels don't do

- No branching. A funnel is a single, straight sequence of steps.

- No time window between steps. A session counts as reaching a step whenever that event happened, no matter how long after the previous step.

- No more than 4 steps per funnel.

[← Frustration signals](/docs/frustration)[Releases →](/docs/releases)