Funnels

In this report type you set up several steps as events and see how many users made it from the first step to each next one. It's useful for finding where users "drop off" — for example, they opened the bot but never reached checkout.

Just like in trends, you can choose a specific event for each step and add a filter to it — click the funnel icon next to the event. Available filter fields are on the Filter Fields page.

You can click the user count for a specific step to open the list of those users.

How to add a funnel

1. Add steps in order — from the first action the user should perform to the last.

2. For each step, choose an event and a filter if needed.

3. Set up the conversion window, order strictness, and (optionally) a UTM breakdown — see the table below.

Funnel settings

Setting	Description
Conversion window	How much time a user is given to go through every step of the funnel, from the first to the last. Users who don't make it in time are considered to have dropped that step
Order strictness	How exactly the step order is checked — see the options below
UTM breakdown/grouping	Splits the funnel's data by UTM tags — at every step you can see how many users came in by each tag

Order strictness

Option	Logic
Sequential	Step B must occur after step A, but any number of other events may happen in between
Strict order	Step B must occur immediately after step A, with no other events in between
Any order	Steps can be completed in any sequence — the order doesn't matter, only that all of them happened

UTM breakdown/grouping

This setting splits the data by UTM tags. In the data table, tags are grouped in a cascade by parameter name and value; you can expand the lists by clicking +.

Cross-funnel

The UTM breakdown takes the tags a user arrived with at the first step and applies them to every following step — even if those steps belong to a different resource (bot or channel). This lets you build a cross-funnel: take events for the first step from one resource, and events for the following steps from another.

Example. We want to understand which traffic source brings not just channel subscribers, but actual buyers in the bot:

1. Step 1 — event "Joined channel", filtered by resource — channel A.

2. Step 2 — event "Bot launch", filtered by resource — bot B.

3. Step 3 — event "Purchase" in bot B.

With a UTM breakdown on the first step, we get a funnel broken down by source: how many users joined the channel by each tag, and how many of them ultimately reached a purchase in the bot.

Example report

Funnel "subscription → bot launch → purchase"

• Step 1: "Joined channel"

• Step 2: "Bot launch"

• Step 3: "Purchase", filter "Unit" = usd

• Conversion window: 7 days

• Order strictness: "Sequential"

• Breakdown: by the first step's UTM source

The result is a table or chart with the number of users at each step and the conversion rate between them, broken down by traffic source.