Conditional forms: showing the right fields at the right time on your landing page

Every landing page form lives under a tension: each extra field costs conversions, but each removed field impoverishes lead qualification. Our analysis of the optimal number of fields shows how to arbitrate — the conditional form often lets you skip the arbitration entirely: it asks the extra questions only of the visitors for whom they're relevant. An individual and a company don't see the same fields; whoever answers "fewer than 10 employees" skips the enterprise-only questions. The form stays short for everyone, while collecting more overall.

What a conditional form is (and isn't)

Conditional logic shows, hides or modifies fields based on answers already given. Three common shapes on a landing page:

• Branching: "You are… an individual / a company" — each answer unfolds its own series of fields (company ID and headcount on one side, nothing extra on the other).
• The clarifying field: "Other" reveals a text field; "Yes, I'm already a customer" reveals the account number.
• Smart deactivation: the "job site postcode" field only appears if the service is on-site.

Not to be confused with the multi-step form, which slices a long form into successive screens without changing its content: the two techniques actually combine very well — a multi-step form where each step adapts to previous answers is the standard for modern quote forms, and the principle behind lead generation quizzes.

Why it works: fewer perceived fields, less abandonment

Visitors don't judge a form by what it collects but by what it displays. And research on web form design is clear on this point: the reference guidelines compiled by Bargas-Avila and co-authors in 2010 (Simple but Crucial User Interfaces in the World Wide Web: Introducing 20 Guidelines for Usable Web Form Design) put at the top the rule of asking only what's necessary, every superfluous question raising interaction cost and abandonment risk. The conditional form applies that rule at the individual level: "necessary" is no longer defined for the average visitor, but for each visitor given their situation. A "company headcount" field is superfluous for an individual — so they never see it.

The effect compounds with the form's other best practices: distinguishing required from optional, validating in real time and polishing the microcopy that explains why each question is asked.

The four cases where conditional logic is justified on a landing page

1. Two distinct audiences on the same page: individual/business, buyer/renter, beginner/advanced — branching avoids building two pages when the offer is shared.
2. Quotes that depend on the project: a tradesperson, mover or landscaper prices differently by service type — the form only asks the questions for the chosen type. That's the core of quote request pages.
3. Progressive sales qualification: in B2B, asking for budget only when company size justifies it avoids putting off small accounts — useful on a demo request page.
4. Compliance: asking for sensitive information only when it becomes genuinely necessary is also a data-minimization requirement of the GDPR — conditional logic is your legal ally.

Designing without overengineering: the rules

• One pivot question, first: the main branch happens on the first question ("You are…"), never in the middle of the form where it disorients.
• Two levels of depth maximum: a condition depending on a condition depending on a condition is untestable and fragile. If your logic exceeds two levels, what you need is a multi-step form.
• Never make fields vanish with their content: if the visitor changes their pivot answer, warn before erasing what they typed — or keep the values in memory.
• The reveal must be smooth and close: the new field appears directly under the answer that triggered it, not at the bottom of the form where nobody sees it.
• Test every branch end to end: each combination of answers is a different form — and each must complete. A bug on one branch is invisible in a quick test and silently costs leads.

Measuring: every branch has its own conversion rate

A conditional form is measured per branch, not on average: if the "company" branch converts at 8% and the "individual" branch at 22%, the average teaches you nothing and hides the problem. Track the pivot question as an event, then follow form abandonment field by field on each branch: it's almost always one specific field on one specific branch that leaks. The full measurement setup is described in our GA4 tracking guide.

In practice on your landing page

Technically, conditional logic fits in a few lines of JavaScript on a static page — no subscription form tool required. LanderKit templates ship clean, accessible forms that are easy to extend: the most frequent case, the branched quote form of the local service template, is personalized by changing the pivot question and each branch's fields. Start with the simplest version (one pivot question, two branches), measure, and only add a condition when data justifies it — the complete form guide gives the healthy baseline to start from.