DM6: Analysing behaviour: metrics, funnels, cohorts and attribution

Lesson 2 of 5 · reading 15–25 minutes; practice and project time is on the module page

Funnels and drop-off

🎯You'll be able to

Build a funnel from events, calculate step-to-step rates, and find the step worth fixing first.

🏠The everyday picture

In a railway station, people walk from the entrance to the ticket window to the platform. If a crowd forms at one staircase, that's where to add a second one.

📘What it really is

📝A worked example

Input: one week of invented MittiMart events.

Step People Step rate
view_item 8,000 —
add_to_cart 960 12.0%
begin_checkout 480 50.0%
purchase 240 50.0%

Steps:

  1. Overall: 240 ÷ 8,000 = 3.0%.
  2. Compare with a month ago: add_to_cart was 14.5%; checkout steps unchanged.
  3. Look at why: support messages mention "no delivery date shown".

Expected output: the product page (view to cart) is the step to investigate, which is what MittiMart's delivery-date test (Project 2) went on to test. (Illustrative figures.)

🌍Where it's used

📝Case scenario

An insurance site's funnel showed half of visitors leaving at "Enter vehicle details". Session recordings showed many didn't know their vehicle's registration date. Adding "Find it on your RC card" with a picture cut the drop noticeably.

🖱️Try it

Write a SQL query (in words or real SQL) that counts distinct client_ids for view_item and for add_to_cart in one week. Success: the query counts people, not events, for each step.

⚠️Common mistakes

🛠️For your project

Project 1's events make this funnel possible; Project 2 tests a change at the product page step.

✅Quick check

How is a step rate calculated?

Show the answer

People at the next step divided by people at this step.

Why count distinct people rather than events?

Show the answer

One person can trigger an event many times, which inflates the step.

← PreviousMetrics that matter
ProLearners Assist