Loading tutorials…
Loading tutorials…
Logic jumps are what turn Typeform from a survey into a smart funnel. Done right, they route every respondent to a personalized path. Done wrong, they create dead ends and respondents stuck on the wrong branch.
Who this is forMarketers building any survey with more than one respondent segment — lead qualification, product onboarding, customer feedback by tier. If your survey has "if-then" logic anywhere, this is for you.
What you'll need
Step 1
Draw the flow as a tree. Every multiple-choice answer is a branch. If you can't fit it on one sheet of paper, the logic is too complex for one survey.
Open a blank sheet of paper or a Whimsical/FigJam board. Draw question 1 at the top.
For every multiple-choice answer in question 1, draw a branch with an arrow to the next question that branch should go to.
Repeat for every multi-choice question. Eventually every path lands at a thank-you screen.
Number each thank-you screen — different branches usually deserve different end screens.
If the diagram exceeds one page, you have too many branches. Consider splitting into two surveys.
Step 2
Typeform logic is set FROM the question that triggers a jump. Open the question → Logic → Add logic.
Open the question that determines branching (e.g., "What is your role?").
Click the Logic icon (lightning bolt) in the right rail.
Click "Add logic." Set: IF answer IS "Founder" THEN JUMP TO "Q4 — Founder qualification questions."
Add a new logic rule for each answer. Important: rules are evaluated in order — the first matching rule wins.
Add a default "ELSE jump to" rule at the bottom for any unmatched answer (or to skip to thank-you for disqualified respondents).
Step 3
Calculator fields (Plus+) let you assign points to answers and compute a score. Branch on score thresholds to route hot leads to a calendar booking.
In a question's Logic tab, click "Calculate" to assign points. Example: "Budget = $10K+" adds 30 points to the score variable.
Repeat for every qualification question (budget, timeline, team size, role).
On the final question, add a logic rule: IF score >= 60 THEN JUMP TO "Hot lead thank-you with Calendly embed."
IF score < 60 THEN JUMP TO "Cold lead thank-you with resource library."
This is how a single Typeform becomes a lead-scoring + routing engine, not just a form.
Step 4
Hidden fields (utm_source, utm_campaign, page_url) carry context from the referring page into the form response — without asking the respondent.
In Typeform → Settings → Hidden fields, add fields: utm_source, utm_medium, utm_campaign, page_url, lead_source.
Pass values via URL: ?utm_source=linkedin&utm_campaign=q2-launch. Typeform reads them automatically.
Hidden field values can be used in logic jumps: IF utm_campaign IS "q2-launch" THEN JUMP TO specific thank-you screen with campaign-specific offer.
Hidden fields also flow to your CRM via integration, enabling source attribution per lead.
Step 5
Open the preview link. Walk through every possible branch by selecting different answers. Confirm each path lands at the right thank-you screen.
In Typeform → Share, copy the preview link.
Open in incognito. Walk through branch 1 (e.g., "Founder" path). Complete to thank-you screen. Confirm it is the right one.
Open a fresh incognito. Walk through branch 2 (e.g., "Marketer" path). Confirm the right thank-you screen.
Repeat for every branch. Disqualified paths included — make sure they exit cleanly to the right screen.
For score-based branches, deliberately answer high-score and low-score paths and confirm both route correctly.
A 5-branch survey takes ~15 minutes to fully test. Worth every minute.
Step 6
When logic 'silently fails' — respondents end up on wrong branch — debug by re-checking rule order, calculator math, and hidden-field defaults.
Symptom: respondents are landing on the wrong thank-you screen. Open Responses → individual response.
Check which answers triggered the path. Common cause: a calculator-field score is mis-summed because a question was edited after scoring was set up.
Re-check every question with logic — calculator deltas, jump targets, hidden-field references.
Check rule order — overlapping rules ("contains X" before "equals X") cause silent misroutes.
If you cannot reproduce, duplicate the form, simplify to the minimum reproducer, and add complexity back one rule at a time.
Common mistakes
Building logic without a paper flow chart
What goes wrong: Multi-branch logic gets tangled fast. You think respondents are routing correctly, but 20% are landing on the wrong thank-you screen. Lost-lead cost adds up at any meaningful volume.
How to avoid: Always draw the flow chart on paper first. Every branch and thank-you screen mapped before you touch Typeform.
Overlapping logic rules in the wrong order
What goes wrong: Broader rule fires before the specific rule. Respondents end up on the wrong path silently. You only notice when sales complains about bad leads.
How to avoid: Order rules from most specific to least specific. Always include a default "ELSE jump" at the bottom.
Calculator-field scoring without testing edge cases
What goes wrong: Hot-lead threshold accidentally triggers on cold leads. Sales team gets flooded with bad-fit demos. ~10-15% of low-quality bookings get attributed to mis-scored Typeforms.
How to avoid: After setting scoring, manually walk through a low-quality answer set and confirm the score is below threshold. Walk through a high-quality set and confirm the score is above.
No ELSE jump on the final qualifying question
What goes wrong: Respondents whose answers don't match any rule get the default thank-you. Often a wrong fit — wasted lead in your CRM.
How to avoid: Always add an ELSE jump on the final qualification question. Route unmatched paths explicitly to a disqualification thank-you.
Not re-testing after editing a published form
What goes wrong: You edit a question, calculator math shifts, and previously-working logic breaks. You don't notice for two weeks until the lead-quality drop becomes visible in CRM.
How to avoid: After ANY edit to a question with logic, re-walk every branch. 15 minutes of testing beats two weeks of bad leads.
Recap
Done — what's next
How to build a Typeform survey that actually gets completed
Read the next tutorial
Hand it off
Logic jumps on a simple 5-branch survey are doable. Logic on a 20-branch product-qualification survey with score-based routing is specialist work. A vetted conversion-funnel specialist will build, test, and document the logic. $80-200 for a one-time build, $200-600/mo for ongoing.
See specialist rates
No hard limit, but past ~20 jumps the survey becomes hard to maintain. If you need more, consider splitting into two linked surveys.
Yes. Dropdown logic works the same as multiple-choice. But dropdowns convert worse than multiple-choice — use them only when options exceed 8.
ELSE only fires if no other rule matches. If an earlier rule has a broader condition than intended (e.g., "contains" when you meant "equals"), it captures the case before ELSE has a chance.
Yes, but it is rarely a good idea. Backward jumps confuse respondents and break completion-rate analytics. Use a "Are you sure?" pattern with a confirmation question instead.
Typeform
Typeform's one-question-at-a-time UX is what makes it convert — and what makes it brittle. This walks through how to structure questions, pick the right field types, and ship a survey that hits 60%+ completion rate.
Typeform
Quizzes are the highest-converting form pattern in B2B marketing. Done right, a quiz captures 3-5x the leads of a plain form. Done wrong, it is a glorified survey with worse completion. This walks through the right pattern.
Typeform
Typeform captures the lead. Your CRM and email tool nurture it. The connection between them is where 90% of lead-routing problems hide. This walks through the right setup path for both HubSpot and Mailchimp.
Tally
Logic jumps are what turn a static form into a smart one. They are also where most Tally forms quietly break. This walks through the branching patterns that actually hold up at scale.