What does a funnel report show?
A funnel shows how users move from the first touch to conversion and where they drop off. Testvoy combines this with variant, segment and date filters in the same decision surface so teams can answer not only who won, but why it won or where the journey broke.
Landing page viewed
Pricing viewed
Signup started
Signup completed
Purchase completed
Per-variant funnel breakdown
A variant can win more clicks but lose more users at payment. That is why teams should not read final CVR only; each step should be checked by variant. Testvoy's funnel report is designed to bring step-level gains and losses into the decision note.
- Where is the biggest drop-off?
- Where does Variant B improve?
- Do mobile and desktop behave the same?
- Does Google Ads traffic differ from organic?
- Is a funnel step mapped to the wrong event?
Example report-reading flow
Example: Variant B looks strong in total conversion. Before deciding, read funnel steps, segment breakdown, revenue impact, bot-filtering signals and SRM warnings. This order reduces the risk of deciding early on one metric.
- 01
Read the Best variant card
- 02
Check Bayesian/Frequentist signals
- 03
Look for SRM warning
- 04
Inspect funnel drop-off steps
- 05
Compare device, country and UTM segments
- 06
Check whether revenue or RPV supports the same direction
- 07
Create a shareable report
Variant B shows +8.4% lift on signup_completed.
No SRM warning.
Mobile segment is stronger; desktop is neutral.
Checkout drop-off did not change.
Decision: move Variant B to 25% rollout.Practical scenario
A growth team changes CTA copy on the pricing page, connects signup_started and signup_completed goals, then reads Google Ads and returning visitor segments separately. If the result is promising, they share a report link with the client or leadership.
Common mistakes
Most mistakes come from wrong project keys, overly broad selectors, missing goals, staging/prod mixups, early decisions on small samples or skipping mobile QA.
Naming an experiment 'test'
Launching without a goal
Deciding on total CVR only
Sending screenshots instead of shareable reports