Logic engine

Formtoro forms don't have to be linear. Step logic lets a step react to what the shopper just submitted — send them to a different step, redirect them to a URL, close the form, or stop them with an inline error. A returning subscriber can skip straight to a thank-you screen while a new visitor gets the full flow.

Open the logic editor

Logic lives on a step — it runs when the shopper submits that step. Three ways in:

• Select a step and open the Logic section in the inspector, then click Add logic (or Edit logic if rules exist). The section also shows a plain-language summary of each rule at a glance.
• Click the Logic button on the step's card on the canvas — it shows a count of rules, like Logic (2).
• Click any logic connection or action card on the canvas (see Logic on the canvas).

All of them open the Step Logic sheet, where you build rules and click Apply to write them into your draft. As with everything in the builder, the draft autosaves; Save version snapshots it and Turn on puts it in front of shoppers — see Saving, versions, and going live.

Anatomy of a rule

Each rule reads as a sentence: when its conditions are met, then an action fires. Click Add rule to create one — Formtoro automatically pairs your first rule with an Otherwise branch so there's always a defined path.

A rule can hold several conditions. The Match setting decides how they combine — All conditions (every one must be true) or Any condition (one is enough) — and Add condition stacks more. Drag the handles to reorder rules and conditions.

Conditions

A condition compares an input against a value. The Use selector picks what kind of input:

• Field — an answer from this form. The Field dropdown lists every field, labeled with its name and step, like shopping_interest (Survey). For choice fields, the Answer value is a dropdown pre-filled with that field's actual options, so you can't mistype a value.
• Visitor — whether Formtoro recognizes this shopper from a previous submission (see below).

Pick an Operator to compare with:

Visitor recognition

Visitor conditions answer one question: have I seen this person before? Formtoro checks the email or phone the shopper just typed against prior submissions to any of your forms.

Classic uses: route recognized shoppers past the capture step to a "Welcome back" screen, or show an inline "You're already subscribed" error instead of re-capturing them.

Actions

The Then row sets what happens when the rule matches. The Action select offers four:

Show inline error can only target a field on the current step — the dropdown only offers this step's fields, so the message always has somewhere to appear.

Rule order and the Otherwise branch

Rules run top to bottom, and the first matching rule wins — its action fires and the rest are skipped. Drag rules to change their order.

The Otherwise card sits below your rules and runs its action when no rule above it matches. If a step has no logic at all, submitting simply follows the submit button's own behavior — normally straight to the next step (see the fields reference).

Test your rules

Click Test rules at the bottom of the Step Logic sheet to open the simulator. It shows an input for each field your rules reference — type or pick sample answers and watch the result update live:

• a banner announces the outcome, e.g. Rule 1 matched → Go to "Thank You" or No rule matched — default action applies;
• each rule gets a per-rule verdict: Matched, Did not match, or Otherwise (always matches).

Visitor-recognition rules are flagged Requires server evaluation — they depend on your real subscriber data, so the simulator can't predict them. The simulator tests your current unsaved edits, so you can tune rules before clicking Apply.

Logic on the canvas

Your routing is drawn right on the canvas. Steps connected by logic show labeled connections — solid gray for an unconditional path, dashed amber for a conditional one. Rules that leave the flow (Redirect, Dismiss, Show error) appear as small action cards beside the step. Click any connection or card to jump into the logic editor with that rule highlighted.

Renames, deletes, and the issues panel

Logic references fields by name, and the builder keeps those references honest:

• Renaming a field automatically rewrites every rule and error target that uses it — nothing to fix by hand.
• Deleting a field removes the rules that depended on it, rather than leaving rules that silently misfire.
• The issues panel flags remaining problems before they go live: a rule pointing at a field that doesn't exist, a value that doesn't fit the field's answers, or a step with no way forward.

Logic and completion

A submission counts as complete when the shopper reaches an end screen — a step with nothing left to fill in, like a thank-you or discount reveal — even if they then close the popup without clicking anything. A rule that ends the form with Redirect to URL or Dismiss form also completes it. That's what drives the completion numbers in Analytics, so routing shoppers to a proper end screen keeps your funnel honest.

Next steps

• Audience filtering — control who sees the form in the first place; logic controls where they go once they're in it.
• Discounts — reward shoppers based on the path they take.
• Building forms — steps, the issues panel, and going live.
• Analytics — see which branches shoppers actually take.