Highlights
- The test compared the original button-first demo entry with a revised email-first design.
- The revised design carried the email into the same form, with the other fields left to complete.
- The revised design recorded a 3.62% demo-button click rate versus 2.47% for control, +46.8% relative.
- The Product Evals form event was 0.97% versus 0.21%, +374.1% relative.
The Challenge
The demo request on this cybersecurity product page started with a button. Clicking it opened a pop-up form, where visitors began entering their details.
Our Solution
The revised design let visitors begin with their email on the product page. After they entered it and clicked, the existing form opened with that answer filled in and the remaining fields ready to complete.
Technical Implementation
How each version worked for a visitor:
Control:
- Click the demo button on the product page.
- The demo form opens in a pop-up.
- Fill in the form.
Variation:
- Type an email into the field next to the button.
- Click the button.
- The same pop-up form opens with the email already filled in.
- Fill in the remaining fields.
Test flow Diagram
Control: the button opens the demo form
- Visitor clicks the demo button on the product page
- The demo form opens in a pop-up
- Visitor fills in the form
Variation: email field first, then the same form
- Visitor types their email into a field next to the demo button
- Visitor clicks the button
- The same pop-up form opens with the email already filled in
- Visitor fills in the remaining fields
Simplified test flow. Archived desktop and mobile design details appear below. The mobile crop is small, so the diagram shows the email field and the form that follows.


The Results
We compared two events for each group. Both rates divide by the users who saw that version.
Table: Event rates for each version. Relative change uses exact counts.
| Event | Control | Variation | Relative change |
|---|---|---|---|
| Request a Demo Clicks | 36 / 1,460 users (2.47%) | 52 / 1,437 users (3.62%) | +46.8% |
| Product Evals (In Modal) | 3 / 1,460 users (0.21%) | 14 / 1,437 users (0.97%) | +374.1% |
What each event counts:
- Request a Demo Clicks counts clicks on the demo button. A click isn’t a submitted demo request.
- Product Evals is a separate event recorded inside the pop-up form. The report doesn’t tie it to trial signups, qualified leads or revenue, so we don’t either.
Reality Check
- Product Evals increased from 3 events to 14, with just 17 in total. A few events can move the percentage a lot at that size, so the size of the effect remains uncertain.
- The test’s final summary reports a different result, but it isn’t clear which event or group of visitors it covers. The rates above are the results we can verify.
Why It May Have Worked
An email field on the page may make the first step easier to see. Carrying that address into the form avoids asking visitors to type it again after that first step.
Appendix
Test parameters
- Users in the report: 2,897, with 1,460 in control and 1,437 in the variation.
- Rates: event count divided by that group’s users.
- Relative change: variation rate divided by control rate, minus one. Displayed rates are rounded, and relative changes are calculated from the underlying counts.
- The report doesn’t break out device, visitor eligibility or traffic allocation.
Statistical analysis
- The report lists 95% confidence for Request a Demo Clicks and 90% for Product Evals.
- We’ve shown these as reported and haven’t recalculated them.
Frequently Asked Questions
Did the email field replace the SaaS demo form?
No. It added a step on the product page. The same pop-up form still opened, with the email filled in and the other fields left to complete.
How did the two recorded event rates compare?
The revised design recorded a 3.62% demo-button click rate against 2.47% for control. Product Evals was 0.97% against 0.21%.
Why track both the button click and the form event?
Button clicks and form events describe different actions. Keeping both in the report prevents the button-click rate from being mistaken for the whole result.
What could another SaaS team test next?
- Compare the current button-first entry with an email-first entry.
- Keep the other form fields, button wording and nearby links the same.
- Measure both button clicks and a clearly defined form event.
How is this different from moving a form higher on the page?
This test changed how visitors start an existing pop-up form. Moving a form changes where they find it. Our enterprise SaaS form-placement study covers that approach, and there are more product-page and signup tests in our SaaS CRO case studies.
Related reading
Related service: Conversion rate optimization.
