Updated on September 25, 2026
You've probably already filled out a form that asked for your "number of employees" when you were responding as an individual. Or a question about your "renovation budget" before even knowing if you owned or rented the form. These kinds of irrelevant questions not only waste time, but they also give the impression that the form wasn't designed for you and encourage you to give up.
Conditional logic solves exactly this problem. But before explaining how to use it, we need to be honest about a point that most guides omit.
Conditional logic displays, hides, or adapts form questions based on previously given answers, ensuring a visitor never sees a question irrelevant to them. That's the short answer. The honest answer is more nuanced: after reviewing a dozen guides on the subject, both French and English, none cites specific figures on its isolated impact on completion rates. Most simply state something like "we have observed significant increases," without providing any supporting data.
This is no coincidence. Isolating the effect of conditional logic in a classic A/B test is difficult because it generally changes several things at once (number of questions viewed, perceived relevance, path length). The closest and most verifiable figure available comes from path simplification tests in general: a case study documented by Growform shows that a financial institution went from a conversion rate of 1% to almost 20% by cutting up its form and adapting the questions to the visitor's profile — a result consistent with what conditional logic allows, even if the study does not isolate it as the sole variable.
Technically, conditional logic relies on rules of the type "if the answer to question A is X, then display question B" (and hide question C). These rules can apply to a single question or to a combination of several answers.
Specifically, in conditional logic integrated into Blastform, these rules are configured visually, without any code: you select the trigger question, the condition, and the action (show, hide, skip to a given step). It's the same mechanism that allows, for example, to offer a different question depending on the size of the company on a demo form or to adapt the engagement question to the role of the registrant on a webinar form.
Three mechanisms are generally distinguished, often confused in general guides:
These three mechanisms are often combined in the same form: a global branching by profile type, with skip logic inside each branch.
On a multi-step quote form, branching typically separates individuals and professionals from the very first question, with each then receiving different qualification questions (reference tax income for an individual, SIRET number and sector of activity for a professional) — our examples of quote forms that use it they detail this mechanism sector by sector.
On an energy lead form, filter out ineligible profiles from the moment you ask about status (owner-occupier, landlord, tenant), you avoid having to display the rest of the form to a visitor who, in any case, will not be able to undertake any work without the agreement of a third party — a mutual time saving for the visitor as well as for your sales team.
On a property valuation form, branching separates a seller "ready to sell within the year" from a seller "just curious," each receiving a different set of steps an insurance or mutual insurance quote form, the same logic adapts the risk assessment questions depending on whether it concerns an individual or a professional.
Conditional logic can also backfire on you. Three errors occur most frequently: too many rules that make the form impossible to maintain without documentation; branches that never join, forcing the duplication of common questions in each path; and the absence of mobile testing, where a poorly managed question jump can give the impression that the form is broken.
And that's not all: overly complex logic can sometimes create more confusion than it solves, especially if the visitor doesn't understand why certain questions appear or disappear. The safest rule remains to limit each form to two or three main branches, even if it means creating a second form for a completely different use case rather than trying to cram everything into a single conditional flow.
Conditional logic is not a feature to be activated once and for all: it is built by observing where your current visitors drop off, and then filtering out questions that are not relevant to them at that precise point in the journey.
Once the branches are in place, you can send the qualified responses to your CRM with profile data already collected, ready for use by your sales team. To avoid starting from scratch, an existing model it already includes a basic structure onto which you can graft your own rules. Try conditional logic for free on your next form.