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

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

Metrics that matter

🎯You'll be able to

Define conversion rate, average order value, revenue per visitor, customer acquisition cost and lifetime value, and tell useful metrics from vanity metrics.

🏠The everyday picture

A tea stall owner who counts only the people passing by learns little. Counting how many stop, how many buy, and how many come back tomorrow tells them what to change.

📘What it really is

📝A worked example

Input: MittiMart's cleaned test data (experiment/): 22,600 visitors, 694 who ordered, 735 orders, and ₹8,53,071 of orders.

Steps:

  1. Conversion rate per visitor: 694 ÷ 22,600 = 3.07%.
  2. AOV: ₹8,53,071 ÷ 735 = ₹1,160.64.
  3. RPV: ₹8,53,071 ÷ 22,600 = ₹37.75.

Expected output: three metrics, each with its definition. Note that 41 visitors ordered twice, which is why orders (735) are more than buyers (694). (All practice-kit data.)

🌍Where it's used

📝Case scenario

A meal-kit start-up celebrated 1 lakh app downloads. Only 4,000 people ordered, and most didn't order twice. Switching its main metric to "customers with a second order within 30 days" refocused the team on delivery quality and menus.

🖱️Try it

Using the figures above, work out what RPV would be if the number of orders stayed at 735 and AOV rose by ₹100. Success: about ₹41.00 (735 × ₹1,260.64 ÷ 22,600), with the steps shown.

⚠️Common mistakes

🛠️For your project

Project 2 counts conversion per visitor (test 5: "visitors with at least one order, not orders").

✅Quick check

What's revenue per visitor?

Show the answer

Total revenue divided by visitors; it combines conversion rate and order value.

Why are app downloads often a vanity metric?

Show the answer

They can rise without anyone using the app or paying.

← BackDM6
ProLearners Assist