Logic that asks only what matters.

What is a conditional logic form?

A conditional logic form changes as people answer it. Instead of showing everyone the same list of questions, it uses rules like “if the rating is 2 or lower, ask what went wrong” to decide what comes next. You may also see it called branching, skip logic, logic jumps or display logic. They all describe the same idea: each person sees only the questions that apply to them.

In Forms, one rule builder covers all of it. A rule has conditions (when should it run?) and actions (what should happen?). It lives on the screen where the answer is given, and it runs as soon as someone moves on.

Conditional logic examples you can copy

• Feedback follow-up: if “How was your visit?” is at most 2, show “What went wrong?”. Otherwise jump straight to “Would you recommend us?”.
• Lead qualification: if “Team size” is greater than 50 and “Budget” is any of “$10k–$50k” or “$50k+”, jump to a booking question. Everyone else goes to an ending with helpful resources.
• Event registration: if “Are you bringing a guest?” is Yes, show the guest’s name and dietary questions. If not, they never see them.
• Quiz scoring: each correct answer adds 1 to a Score variable. On the last screen, if Score is at least 8, jump to the “Expert” ending; otherwise the “Keep learning” ending.
• Price calculator: each option adds its price to a Total variable, and a Payment question set to “calculated” charges exactly that total.
• Campaign routing: if the hidden field source is “partner”, skip “How did you hear about us?”, because you already know.
• Early exit: if “Are you over 18?” is No, finish the form with an ending that explains why.

Every condition and action available

Conditions can check an answer, a hidden field passed in the link, a variable, or the respondent’s device (mobile or desktop). Depending on the kind of answer, you can test whether it is or is not a value, contains or doesn’t contain text, starts or ends with something, is any of a list, is greater than, at least, less than or at most a number, is before or after a date, is empty, or is answered.

Actions can jump to any later screen or ending, show or hide a screen, set a variable, add to or subtract from it, or finish the form. Combine up to 30 conditions in one rule with “and” or “or”, and run up to 20 actions when it matches. A rule with no conditions always runs, which is handy for adding points or setting a default.

How to plan a branching form that doesn’t break

• Sketch the paths first. Write the main route, then mark where people should split off and where they should rejoin.
• Let branches merge back. Most paths should end at the same closing questions, so you aren’t maintaining three copies of “Anything else?”.
• Hide by default, then show. For a follow-up question, choose “Hide until logic shows it” on the screen and add a show action, rather than jumping around it.
• Use variables for anything you count: scores, prices, numbers of “yes” answers. They keep rules short.
• Check the flow map. It draws every branch and warns you about screens no path can reach and jumps that point backwards and could loop.
• Preview each path before you publish. The preview runs the same rules as the live form and the server.

Conditional logic or a shorter form?

Logic doesn’t replace editing. If a question doesn’t change what you’ll do with the answer, cut it rather than hiding it behind a rule. Use logic for questions that are essential to some people and irrelevant to others: that is where it shortens the form without losing anything you need.