Find the step
that leaks revenue.
Map homepage → pricing → signup → activation (or your paths) and measure drop-off between steps. Funnel analysis in RunPivot ties to the pages you test, not a separate product analytics warehouse.
Test where the funnel breaks
Aggregate conversion rate hides which step failed. Funnels expose it.
Steps that match your business
Use URLs and events that reflect your real journey, visit pricing, start trial, complete onboarding. Name steps the way your team already talks about the funnel.
Pricing → Signup
−38%
See the cliff, not just the average
Step-to-step conversion shows where you lose half your audience. Pair with session replay on that step to understand why before you prompt the next variant.
Test queued on Signup step
Hypothesis on the weak step
Launch an experiment on the page that owns the drop (new hero on pricing, shorter signup form, clearer CTA on activation) without rebuilding analytics in a second tool.
Why funnels inside RunPivot?
Prioritize tests
Run fewer, better experiments on the highest-leak step.
Segment funnels
Mobile vs desktop funnels often look nothing alike.
Connect to replay
Drop-off step + session watch = grounded hypotheses.
Conversion-focused
Built for marketing funnels, not arbitrary event graphs.
Related capabilities
Prompt-Built Tests
Describe a change in plain language and it becomes a live experiment.
See how tests startAnalytics
Conversion metrics native to your test program, not a full product analytics suite.
See analytics scopeFix the step, not the average.