Scenario 1: Scored quiz
1
Create Calculated Score
Drag Calculated → name it Score (field name
Public Fill never shows Calculated fields — the score appears on thank you via
score) → Number → = 0.Public Fill never shows Calculated fields — the score appears on thank you via
{score}.2
Add quiz questions
Multiple choice (or similar) for each item.
3
Add points with Calculate
For each correct answer:
When that question is (correct option) → Then Calculate Σ Score Add
(use Subtract / other ops if you need penalties).
When that question is (correct option) → Then Calculate Σ Score Add
10(use Subtract / other ops if you need penalties).
4
Route by score
When Score ≥
Another rule (or else path) → Fail / other result page.
Keep Calculate rules before Jump rules. Mark Pass / Fail pages as terminal.
70 → Jump to page Pass.Another rule (or else path) → Fail / other result page.
Keep Calculate rules before Jump rules. Mark Pass / Fail pages as terminal.
5
Show score on Thank you
In the thank-you message, use a merge tag with the field name:
After submit, Fill replaces
Attempt recorded. Final score: {score}/100.After submit, Fill replaces
{score} with the calculated value.Scenario 2: Dynamic pricing
1
Collect inputs
Quantity, plan, add-ons, etc.
2
Calculated Total
Calculated → Number → initial
0 or a Formula such as {price} * {quantity}.3
Conditional adjustments
e.g. When plan is Pro → Calculate Total Multiply
1.2, or Formula ({price} * {quantity}) - {discount}.4
Show or charge
Echo Total on thank-you with
{total}, or map it to payment price when your payment block supports Calculated targets. Public Fill does not render the Calculated field itself.Scenario 3: Eligibility gate
1
Ask the qualifier
e.g. monthly budget.
2
Explain low fits
When budget is too low → Show a message block. Prefer Require / Jump over hiding Next/Submit.
3
Optional score
Use a Calculated lead score the same way as the quiz (Add points per answer), then branch or sync. Fill never shows Calculated fields.