For the complete documentation index, see llms.txt. This page is also available as Markdown.

πŸ”€Logic, Scoring & Outcomes

The Logic tab of the Dapta Forms editor: the interactive Logic canvas, the read-only Logic map on small screens, and the form-wide Branching, Scoring and Outcomes dialogs that turn a plain form into a

Logic is what makes a form react to its respondents: questions that appear only when they matter, answers that jump ahead or end the form, points that add up to a score, and endings that change with that score. Everything lives in the Logic tab of the editor, next to Build and Connect.


The Logic tab

Open any form in the editor and click Logic in the top bar. On a desktop screen you get the Logic canvas: every question is a card, the lines between them show the path a respondent takes, and the toolbar above holds the three form-wide editors: Branching, Scoring and Outcomes.

The Logic tab showing the Logic canvas with question cards, a dashed jump to a later question, three outcome cards and the End marker, with the Branching, Scoring and Outcomes toolbar and the zoom controls highlighted
The Logic canvas. Dashed lines are jumps, the cards on the right are the outcomes, and END is where a skipped form lands.

How to read the canvas:

  • START is where every respondent begins. Cards then run left to right in question order.

  • A solid line is the normal path: "continue to the next question in order".

  • A dashed line is a jump created by a branching rule. The label on the line is the answer that triggers it (for example $2,000+ / month). A jump with no target leads to the shared END marker (the rule reads skip to end).

  • The highlighted cards near the end are your Outcomes: one per score range, stacked because a respondent only ever sees one of them.

  • Hover a card to reveal its edit button (its tooltip reads Edit the logic for {question}). It opens the same Logic dialog you get from the Build tab, so you can fix a rule without leaving the canvas.

The controls in the bottom left let you Zoom out, Zoom in, Fit to screen and Auto-arrange. Drag a card to move it; drag the empty canvas to pan. Cards you moved keep their position until you click Auto-arrange, which restores the automatic layout.


The Logic map on small screens

Below a laptop-sized window the canvas is replaced by a read-only Logic map: a vertical list of the same cards, with the jumps and conditions written out in plain sentences (If Under $500 / month β†’ skip to end, Show if What's your main goal? is any of Capture more leads, Qualify faster). You can read the flow on a phone or a narrow window, but editing happens in the dialogs.


The three toolbar dialogs

Button
What it opens

Branching

Every question in order, with its Always go to catch-all, its If answer is rules and its Show when / Hide when conditions. The summary line at the top reads, for example, 3 of 8 questions carry logic.

Scoring

Every point value in the form on one screen, plus the Enable scoring master switch.

Outcomes

The score ranges and what each range shows at the end: a label, a thank-you message, an optional redirect.

The form-wide Branching dialog listing every question with its Always go to control, and the summary line 3 of 8 questions carry logic highlighted
The Branching dialog is the quickest way to review all the logic of a form in one place.

What a qualifying form looks like

A typical lead qualification form combines the four building blocks in this order:

  1. Points on the answers that matter (team size, budget, urgency). See Scoring.

  2. Conditions so that follow-up questions only appear when an earlier answer calls for them. See Show & hide conditions.

  3. Branching rules that send a disqualifying answer straight to the end, or a hot lead straight to the booking step. See Branching & jumps.

  4. Outcomes that map score ranges to different endings: "Not a fit", "Nurture", "Book a call". See Outcomes.

πŸ’‘ Tip: The Lead qualifier template in the question gallery ships with all four already wired. Create a form from it and open the Logic tab to see a working example.

In this section

Last updated