Skip to main content
Calculated fields run automatic math (or text assembly) inside your form — quiz scores, live pricing, lead scores, or concatenated names — based on respondents’ answers. Respondents do not answer a Calculated field, and public Fill never renders the field UI. Values still update for logic, submissions, payment price targets, and thank-you merge tags such as {score}. You always see the block in Studio. For the Then action details, see also Calculate.

Examples


Create a Calculated field

In Build mode, open the Logic catalog and drag Calculated onto the canvas.
Put the Calculated field above the questions that update it (e.g. Score at the top), or at least where you can find it later. Updates come from Conditional logic → Calculate, not from the initial value alone.
1

Name the field

In the Σ pill, type a clear name (e.g. Score, Total). You will pick this name again in Calculate actions.
2

Choose Number or Text

Number — arithmetic (Add / Subtract / Multiply / Divide / Formula math).
Text — labels, status strings, concatenation (Assign / Formula text).
3

Set the initial value

After =, set the starting point:
  • Type a literal (e.g. 0 for a quiz score)
  • Leave blank
  • Or open the chevron and pick another field
Same control as Value elsewhere: type or pick from the list.
The block ships with When Always → Calculate so the initial expression stays applied. Scoring and conditional updates usually add more Calculate actions on If / Else or the Logic Board.

Insert conditional logic and Calculate

Add an If / Else (or open Logic Board) near the questions that should change the score.
  1. When — e.g. flamingo question is Tiny shrimps
  2. ThenCalculate
  3. Pick the target (Σ Score)
  4. Pick an operation, then a Value (type or pick a field)

Numeric operations

Textual operations

Formulas

Formula writes one expression instead of chaining many Add steps. Use {blockId} tokens (picker / @ in the formula editor), + − * /, and parentheses.
Tokens are block IDs ({…}), not question titles. Always insert fields with the picker / @ so IDs stay correct.

Worked example: scored quiz

Matches the common quiz pattern: one Score field + Add points when the answer is correct.
1

Add Calculated Score

Σ ScoreNumber= 0
2

Add questions

Multiple choice (or similar) for each quiz item.
3

Add logic per correct answer

When question is (correct option)Then Calculate Σ Score Add 10
Repeat for each question / point value.
4

Show or branch on Score

Thank-you message with {score}, or When Score ≥ 70 → Jump to Pass page. Fill never shows the Score field itself.
See also the Quiz recipe.

Number vs text engine behavior

Divide / modulo by zero → empty result (no crash).

How to use the result


FAQ

Add / Subtract / Multiply / Divide / Assign apply one step when the When matches (perfect for quiz “+10”). Formula is one expression with many operations and field tokens.
Logic blocks are editor-only. Calculated fields never appear on public Fill steps — respondents only see the value if you put a merge tag on thank you (or map it to payment price).
  1. Confirm Initial value is 0 (or blank) and rules Add points on correct answers.
  2. Confirm When matches the real option value.
  3. Confirm Calculate targets Σ Score, not another field.
  4. Prefer Calculate before Jump on the same screen — a Jump can skip later Calculates.
  5. Test on Fill / published, not only the canvas.
Logic runs in order. If an earlier rule Jumps, later Calculates on that path may never run. Place scoring Calculates before Jump actions.
Date arithmetic is not supported yet — same limitation as typical form calculators.

Common mistakes

Last modified on September 7, 2026