Designing an E-Commerce Conversion Funnel Tracking System
Intermediate
75 min
1 views
0 solutions
Overview
UrbanMart's e-commerce team has raw customer session logs but no funnel tracking — they can't tell where customers drop off. The analyst must design a rule-based funnel stage system (Visit → Browse → Cart → Checkout → Confirmed), manually trace 10 sample sessions, and identify the biggest leak before the marketing team spends another ₹5 lakh on acquisition.
Case Details
# Aplly.xyz Case Study Submission
## Title
Designing an E-Commerce Conversion Funnel Tracking System
## Type
Data Analytics
## Difficulty
Intermediate
## Estimated Time
75 minutes
## Overview
UrbanMart's e-commerce team has raw customer session logs but no funnel tracking — they can't tell where customers drop off. The analyst must design a rule-based funnel stage system (Visit → Browse → Cart → Checkout → Confirmed), manually trace 10 sample sessions, and identify the biggest leak before the marketing team spends another ₹5 lakh on acquisition.
## Case Details
Function Focus: Rule-based funnel stage design, multi-session attribution logic, edge-case handling, drop-off analysis
Scenario:
UrbanMart spent ₹5 lakh on digital ads last month but can't measure conversion because there's no funnel tracking — only raw page-view logs. The marketing director wants a funnel system that answers one question: "Where are we losing customers?" The analyst must design a 5-stage funnel with clear transition rules, then manually trace through 10 real customer sessions to verify the rules work for normal paths, multi-session journeys, and edge cases like direct-to-cart checkouts or abandoned carts that later convert.
Funnel Stages (Draft):
1. Visit — customer lands on any page
2. Browse — customer views 2+ distinct product pages in a session
3. Add to Cart — customer adds at least 1 item to cart
4. Checkout Initiated — customer reaches the checkout or payment page
5. Order Confirmed — customer completes payment and receives confirmation
Draft Transition Rules:
- Stages are sequential — a customer cannot reach stage N without passing through stages 1 through N-1
- A new session resets to Visit unless the customer has items in a saved cart; if a saved cart exists, the session starts at Add to Cart
- If a customer adds an item to cart without browsing 2+ product pages, they advance to Add to Cart but Browse is recorded as skipped (counted as Browse for funnel purposes since intent is demonstrated)
- Cart abandonment (emptying cart) drops the customer back to the Browse stage
Tasks:
1. Before tracing, read the draft funnel stages and rules — identify at least 2 situations not handled by the current rules (e.g., what counts as a product page? what if a customer checks out as guest vs logged in?)
2. Manually trace all 10 customer sessions through the funnel — for each session, list which stages were reached, where the drop-off occurred (if any), and which rule governed each transition
3. Compute the funnel conversion metrics from your traces: (a) overall Visit-to-Confirmed conversion rate, (b) stage-by-stage drop-off rate (percentage who enter each stage but do not advance), and (c) identify which stage has the highest absolute drop-off
4. Identify which sessions were edge cases that the draft rules handled poorly or ambiguously — propose a revised rule for each edge case
5. Only after submitting your manual analysis, implement the funnel rules in a spreadsheet or trace tool and verify your stage assignments — report any sessions where the tool disagreed with your manual trace
Expected Output:
A funnel analysis packet containing: (a) critique of the draft rules with at least 2 missing edge cases identified, (b) a 10-session trace table showing stages reached and drop-off points with rule references, (c) conversion metrics with stage-by-stage drop-off rates and identification of the biggest leak, (d) revised rules for the edge cases found, and (e) a round-trip discrepancy log.
Evaluation Criteria:
Completeness of the session trace table (all 10 sessions fully classified), correct funnel metrics arithmetic, correct identification of the stage with the highest drop-off, quality of edge-case rule revisions, and honest discrepancy reporting.
## Data Sources
Customer Sessions (10):
| Session ID | Customer | Events (in order) | Duration |
|---|---|---|---|
| S01 | C001 | Homepage → Product A → Product B → Add A to Cart → Checkout → Payment → Order Confirmed | 12 min |
| S02 | C002 | Homepage → Product A → Product B → Product C → Product D → Leave | 8 min |
| S03 | C003 | Homepage → Blog → Leave | 1 min |
| S04 | C004 (Day 1) | Homepage → Product A → Product B → Add A to Cart → Add B to Cart → Leave | 15 min |
| S04 | C004 (Day 2) | Login → Cart (items A, B still present) → Checkout → Payment → Order Confirmed | 5 min |
| S05 | C005 | Homepage → Product A → Add A to Cart → Checkout → Leave at payment page | 7 min |
| S06 | C006 | Homepage → Add A to Cart (direct from homepage featured product) → Checkout → Payment → Order Confirmed | 4 min |
| S07 | C007 | Homepage → Product A → Product B → Add A to Cart → Remove A from Cart → Browse Product C → Leave | 20 min |
| S08 | C008 | Homepage → Product A → Add A to Cart → Checkout → Payment Error → Payment Error → Leave | 10 min |
| S09 | C009 | Homepage → Product A → Product B → Product C → Add B to Cart → Add C to Cart → Checkout → Payment → Order Confirmed | 18 min |
| S10 | C010 (Day 1) | Homepage → Product A → Add A to Cart → Leave | 6 min |
| S10 | C010 (Day 8) | Homepage → Search → Product B → Add B to Cart → Checkout → Payment → Order Confirmed | 9 min |
Notes on the data:
- S04 Day 2: customer returned next day — cart items A and B were still saved (session resumed at Add to Cart)
- S06: customer added to cart directly from a featured product on the homepage without browsing other product pages
- S07: customer removed all items from cart mid-session then continued browsing
- S10: customer returned 8 days later and bought a different product (B) than the one originally carted (A)
Page Type Reference:
| Page URL Pattern | Type |
|---|---|
| /, /home, /index | Homepage |
| /products/, /category/ | Product page |
| /cart, /bag | Cart page |
| /checkout, /payment | Checkout page |
| /order/confirm* | Order confirmation page |
| /blog/*, /about, /contact | Non-product page |
| /search?q=* | Search results page |
## Solution Frameworks
Funnel analysis, sessionization logic, state-machine design, multi-session attribution, drop-off analysis
## Solver Guidance & Tutorials
Link to: "Funnel Design and Drop-Off Analysis" tutorial
## What You'll Learn
- Designing a state-machine funnel with clear transition rules
- Handling edge cases: multi-session journeys, direct-to-cart paths, cart abandonment
- Computing and interpreting stage-by-stage conversion metrics
- Identifying the biggest funnel leak before spending on acquisition
## Tags
conversion funnel, e-commerce, session analysis, drop-off, customer journey
## Registration Links
- Register as Solver
- Register as Evaluator
## Title
Designing an E-Commerce Conversion Funnel Tracking System
## Type
Data Analytics
## Difficulty
Intermediate
## Estimated Time
75 minutes
## Overview
UrbanMart's e-commerce team has raw customer session logs but no funnel tracking — they can't tell where customers drop off. The analyst must design a rule-based funnel stage system (Visit → Browse → Cart → Checkout → Confirmed), manually trace 10 sample sessions, and identify the biggest leak before the marketing team spends another ₹5 lakh on acquisition.
## Case Details
Function Focus: Rule-based funnel stage design, multi-session attribution logic, edge-case handling, drop-off analysis
Scenario:
UrbanMart spent ₹5 lakh on digital ads last month but can't measure conversion because there's no funnel tracking — only raw page-view logs. The marketing director wants a funnel system that answers one question: "Where are we losing customers?" The analyst must design a 5-stage funnel with clear transition rules, then manually trace through 10 real customer sessions to verify the rules work for normal paths, multi-session journeys, and edge cases like direct-to-cart checkouts or abandoned carts that later convert.
Funnel Stages (Draft):
1. Visit — customer lands on any page
2. Browse — customer views 2+ distinct product pages in a session
3. Add to Cart — customer adds at least 1 item to cart
4. Checkout Initiated — customer reaches the checkout or payment page
5. Order Confirmed — customer completes payment and receives confirmation
Draft Transition Rules:
- Stages are sequential — a customer cannot reach stage N without passing through stages 1 through N-1
- A new session resets to Visit unless the customer has items in a saved cart; if a saved cart exists, the session starts at Add to Cart
- If a customer adds an item to cart without browsing 2+ product pages, they advance to Add to Cart but Browse is recorded as skipped (counted as Browse for funnel purposes since intent is demonstrated)
- Cart abandonment (emptying cart) drops the customer back to the Browse stage
Tasks:
1. Before tracing, read the draft funnel stages and rules — identify at least 2 situations not handled by the current rules (e.g., what counts as a product page? what if a customer checks out as guest vs logged in?)
2. Manually trace all 10 customer sessions through the funnel — for each session, list which stages were reached, where the drop-off occurred (if any), and which rule governed each transition
3. Compute the funnel conversion metrics from your traces: (a) overall Visit-to-Confirmed conversion rate, (b) stage-by-stage drop-off rate (percentage who enter each stage but do not advance), and (c) identify which stage has the highest absolute drop-off
4. Identify which sessions were edge cases that the draft rules handled poorly or ambiguously — propose a revised rule for each edge case
5. Only after submitting your manual analysis, implement the funnel rules in a spreadsheet or trace tool and verify your stage assignments — report any sessions where the tool disagreed with your manual trace
Expected Output:
A funnel analysis packet containing: (a) critique of the draft rules with at least 2 missing edge cases identified, (b) a 10-session trace table showing stages reached and drop-off points with rule references, (c) conversion metrics with stage-by-stage drop-off rates and identification of the biggest leak, (d) revised rules for the edge cases found, and (e) a round-trip discrepancy log.
Evaluation Criteria:
Completeness of the session trace table (all 10 sessions fully classified), correct funnel metrics arithmetic, correct identification of the stage with the highest drop-off, quality of edge-case rule revisions, and honest discrepancy reporting.
## Data Sources
Customer Sessions (10):
| Session ID | Customer | Events (in order) | Duration |
|---|---|---|---|
| S01 | C001 | Homepage → Product A → Product B → Add A to Cart → Checkout → Payment → Order Confirmed | 12 min |
| S02 | C002 | Homepage → Product A → Product B → Product C → Product D → Leave | 8 min |
| S03 | C003 | Homepage → Blog → Leave | 1 min |
| S04 | C004 (Day 1) | Homepage → Product A → Product B → Add A to Cart → Add B to Cart → Leave | 15 min |
| S04 | C004 (Day 2) | Login → Cart (items A, B still present) → Checkout → Payment → Order Confirmed | 5 min |
| S05 | C005 | Homepage → Product A → Add A to Cart → Checkout → Leave at payment page | 7 min |
| S06 | C006 | Homepage → Add A to Cart (direct from homepage featured product) → Checkout → Payment → Order Confirmed | 4 min |
| S07 | C007 | Homepage → Product A → Product B → Add A to Cart → Remove A from Cart → Browse Product C → Leave | 20 min |
| S08 | C008 | Homepage → Product A → Add A to Cart → Checkout → Payment Error → Payment Error → Leave | 10 min |
| S09 | C009 | Homepage → Product A → Product B → Product C → Add B to Cart → Add C to Cart → Checkout → Payment → Order Confirmed | 18 min |
| S10 | C010 (Day 1) | Homepage → Product A → Add A to Cart → Leave | 6 min |
| S10 | C010 (Day 8) | Homepage → Search → Product B → Add B to Cart → Checkout → Payment → Order Confirmed | 9 min |
Notes on the data:
- S04 Day 2: customer returned next day — cart items A and B were still saved (session resumed at Add to Cart)
- S06: customer added to cart directly from a featured product on the homepage without browsing other product pages
- S07: customer removed all items from cart mid-session then continued browsing
- S10: customer returned 8 days later and bought a different product (B) than the one originally carted (A)
Page Type Reference:
| Page URL Pattern | Type |
|---|---|
| /, /home, /index | Homepage |
| /products/, /category/ | Product page |
| /cart, /bag | Cart page |
| /checkout, /payment | Checkout page |
| /order/confirm* | Order confirmation page |
| /blog/*, /about, /contact | Non-product page |
| /search?q=* | Search results page |
## Solution Frameworks
Funnel analysis, sessionization logic, state-machine design, multi-session attribution, drop-off analysis
## Solver Guidance & Tutorials
Link to: "Funnel Design and Drop-Off Analysis" tutorial
## What You'll Learn
- Designing a state-machine funnel with clear transition rules
- Handling edge cases: multi-session journeys, direct-to-cart paths, cart abandonment
- Computing and interpreting stage-by-stage conversion metrics
- Identifying the biggest funnel leak before spending on acquisition
## Tags
conversion funnel, e-commerce, session analysis, drop-off, customer journey
## Registration Links
- Register as Solver
- Register as Evaluator
Data Sources
Customer Sessions (10):
| Session ID | Customer | Events (in order) | Duration |
|---|---|---|---|
| S01 | C001 | Homepage → Product A → Product B → Add A to Cart → Checkout → Payment → Order Confirmed | 12 min |
| S02 | C002 | Homepage → Product A → Product B → Product C → Product D → Leave | 8 min |
| S03 | C003 | Homepage → Blog → Leave | 1 min |
| S04 | C004 (Day 1) | Homepage → Product A → Product B → Add A to Cart → Add B to Cart → Leave | 15 min |
| S04 | C004 (Day 2) | Login → Cart (items A, B still present) → Checkout → Payment → Order Confirmed | 5 min |
| S05 | C005 | Homepage → Product A → Add A to Cart → Checkout → Leave at payment page | 7 min |
| S06 | C006 | Homepage → Add A to Cart (direct from homepage featured product) → Checkout → Payment → Order Confirmed | 4 min |
| S07 | C007 | Homepage → Product A → Product B → Add A to Cart → Remove A from Cart → Browse Product C → Leave | 20 min |
| S08 | C008 | Homepage → Product A → Add A to Cart → Checkout → Payment Error → Payment Error → Leave | 10 min |
| S09 | C009 | Homepage → Product A → Product B → Product C → Add B to Cart → Add C to Cart → Checkout → Payment → Order Confirmed | 18 min |
| S10 | C010 (Day 1) | Homepage → Product A → Add A to Cart → Leave | 6 min |
| S10 | C010 (Day 8) | Homepage → Search → Product B → Add B to Cart → Checkout → Payment → Order Confirmed | 9 min |
Notes on the data:
- S04 Day 2: customer returned next day — cart items A and B were still saved (session resumed at Add to Cart)
- S06: customer added to cart directly from a featured product on the homepage without browsing other product pages
- S07: customer removed all items from cart mid-session then continued browsing
- S10: customer returned 8 days later and bought a different product (B) than the one originally carted (A)
Page Type Reference:
| Page URL Pattern | Type |
|---|---|
| /, /home, /index | Homepage |
| /products/, /category/ | Product page |
| /cart, /bag | Cart page |
| /checkout, /payment | Checkout page |
| /order/confirm* | Order confirmation page |
| /blog/*, /about, /contact | Non-product page |
| /search?q=* | Search results page |
| Session ID | Customer | Events (in order) | Duration |
|---|---|---|---|
| S01 | C001 | Homepage → Product A → Product B → Add A to Cart → Checkout → Payment → Order Confirmed | 12 min |
| S02 | C002 | Homepage → Product A → Product B → Product C → Product D → Leave | 8 min |
| S03 | C003 | Homepage → Blog → Leave | 1 min |
| S04 | C004 (Day 1) | Homepage → Product A → Product B → Add A to Cart → Add B to Cart → Leave | 15 min |
| S04 | C004 (Day 2) | Login → Cart (items A, B still present) → Checkout → Payment → Order Confirmed | 5 min |
| S05 | C005 | Homepage → Product A → Add A to Cart → Checkout → Leave at payment page | 7 min |
| S06 | C006 | Homepage → Add A to Cart (direct from homepage featured product) → Checkout → Payment → Order Confirmed | 4 min |
| S07 | C007 | Homepage → Product A → Product B → Add A to Cart → Remove A from Cart → Browse Product C → Leave | 20 min |
| S08 | C008 | Homepage → Product A → Add A to Cart → Checkout → Payment Error → Payment Error → Leave | 10 min |
| S09 | C009 | Homepage → Product A → Product B → Product C → Add B to Cart → Add C to Cart → Checkout → Payment → Order Confirmed | 18 min |
| S10 | C010 (Day 1) | Homepage → Product A → Add A to Cart → Leave | 6 min |
| S10 | C010 (Day 8) | Homepage → Search → Product B → Add B to Cart → Checkout → Payment → Order Confirmed | 9 min |
Notes on the data:
- S04 Day 2: customer returned next day — cart items A and B were still saved (session resumed at Add to Cart)
- S06: customer added to cart directly from a featured product on the homepage without browsing other product pages
- S07: customer removed all items from cart mid-session then continued browsing
- S10: customer returned 8 days later and bought a different product (B) than the one originally carted (A)
Page Type Reference:
| Page URL Pattern | Type |
|---|---|
| /, /home, /index | Homepage |
| /products/, /category/ | Product page |
| /cart, /bag | Cart page |
| /checkout, /payment | Checkout page |
| /order/confirm* | Order confirmation page |
| /blog/*, /about, /contact | Non-product page |
| /search?q=* | Search results page |
Solution Frameworks
Funnel analysis, sessionization logic, state-machine design, multi-session attribution, drop-off analysis
Solver Guidance & Tutorials
Link to: "Funnel Design and Drop-Off Analysis" tutorial
What You'll Learn
- Problem-solving and analytical thinking
- Data-driven decision making
- Business strategy development
- Professional report writing
0
Solutions Submitted
Difficulty
Intermediate
Estimated Time
75 minutes
Relevance
Fresh
Source
case-studies-in