Run the failure
Use the red CTA to create the analytical problem intentionally.
Practice Lab · 12 · Product Analytics
Funnel Drop-off Detective
A redesign appears to hurt activation. Run a funnel diagnostic and separate real product friction from a tracking break.
FunnelsSegmentationInstrumentationActivation
Case brief
Find which step changed and decide whether the product or instrumentation deserves the first investigation.
01
Your task
Break it. Run the checks. Explain the evidence.
Predict the result
Before validating, decide what you expect row counts or metrics to do.
Run validation
Use the green CTA to reveal the checks that catch the failure.
Explain it
Say what broke in plain business language, not only SQL language.
02
Interactive case
Run this.
RUN THIS CASE ↓
Funnel Drop-off Detective
Find which step changed and decide whether the product or instrumentation deserves the first investigation.
Ready — run the case. One step collapses only on mobile after the release.
Signup
100%100%
Address added
82%82%
Payment added
70%42%
Checkout started
55%34%
First order complete
41%28%
DesktopstableMobilestablepayment_added collapses
The break begins at payment_added and is isolated to mobile after release. Instrumentation/payment-step regression deserves investigation before blaming acquisition.
Debrief unlocked
What should the analyst learn?
- Look at step conversion, not only final activation.
- Segment before generalizing a funnel problem.
- A sudden platform-specific break may be instrumentation, not behavior.
03
Transfer
Use the same checks at work.
Look at step conversion, not only final activation.
Segment before generalizing a funnel problem.
A sudden platform-specific break may be instrumentation, not behavior.