Logic engine

Formtoro forms aren't just linear. With logic, a form adapts to each shopper — routing them to the right step, showing only relevant elements, and reacting to what they tell you.

There are two complementary systems: step logic (routing) and visibility conditions (show/hide).

Step logic — routing rules

Step logic runs when a shopper submits a step. You build rules in the Logic editor for a step. Each rule is "when a condition is met, then take an action."

Actions

• Go to step — branch to a specific step instead of the next one.
• Redirect — send the shopper to a URL (in the same tab or a new one).
• Dismiss — close the form.
• Display error — show an inline message and keep the shopper on the step (e.g. "You're already subscribed"), preventing them from advancing.

Conditions

A condition compares an input against a value using an operator:

Conditions can read three kinds of input:

• Fields — a previous answer in this form (by its field name).
• Hidden values — context passed into the form (e.g. a campaign ID).
• Visitor signals — whether Formtoro recognizes the shopper: known by email or phone, which forms they've submitted before, and when they last submitted.

Combine multiple conditions with AND / OR groups for precise targeting.

How rules are chosen

Rules run in priority order, and the first matching rule wins — its action fires and the rest are skipped. A rule with no condition acts as a fallback. If nothing matches, the form simply advances to the next step.

Where rules run

• Client-side rules evaluate instantly in the storefront widget using field answers.
• Server-side rules evaluate on submission and can use visitor recognition (e.g. "has this person subscribed before?"), which isn't available in the browser.

Visibility conditions — show/hide elements

Separately, any element can be shown or hidden based on field answers. These are simpler than routing rules: a flat list of conditions (equals, contains, is empty, and so on) combined with AND/OR, with no actions — just whether the element appears. Use them to reveal a follow-up question only when it's relevant.

Test your logic

The builder includes a logic simulator ("Test rules"). Enter sample answers for the fields your rules reference, and it shows which rule matches and what action fires. The tester evaluates client-side rules; rules that need server evaluation (visitor recognition) are flagged, since they depend on live data. The tester only takes the runtime inputs your rules use — there are no canned "returning customer" profiles.

Next steps

• Audience filtering — control who sees a form in the first place.
• Discounts — reward shoppers based on their path through the form.