Survey Logic¶
The Survey Logic page arranges the path participants take through your survey. Where the Builder edits what is on each page, Survey Logic decides which pages appear, in what order, under what conditions, and with what variables set along the way.
The tree¶
The page shows your survey as a tree of elements in execution order. Drag elements by their grip handles to reorder or to nest them inside a branch or randomizer (press and hold on touch screens). Blocks shown here are the same blocks you edit in the Builder, the toolbar's buttons add new elements, Add Block, Add Code Block, Add Rating Task, Add Randomizer, Add Branch, Add Custom Variables, and End Survey.
The path always ends at the Survey Complete card, participants who reach the end of the tree without hitting an End Survey element finish there.
Element types¶
Blocks¶
One participant-facing page each, see The Builder. Removing a block from the tree (without deleting it) is possible by deleting the tree element, the Builder offers to move orphaned blocks back into the flow.
Branch¶
A branch holds conditions and children. When the conditions pass, the participant goes through the elements nested inside, otherwise the branch is skipped entirely. Conditions read participant answers to earlier questions or custom variables, and compare with is equal to, is not equal to, is less than, is less than or equal to, is greater than, is greater than or equal to, contains, or does not contain. Multiple conditions combine on the branch.
Randomizer¶
A randomizer shuffles its children per participant. Use it for condition assignment, nest one block per experimental condition inside and each participant receives the children in an independent random order, or combine with a branch per child for show-one-of-N designs. The randomization a participant received is reconstructable from the data, every response records its own ordering.
Custom Variables¶
A Custom Variables element sets named values on the response when the participant passes it, condition labels, group assignments, computed flags. Set keys and values in the card (or edit them as JSON in bulk). Reference any variable later as a placeholder
{{ emb.your_key }}
inside question text, Content questions, the completion message, or a redirect URL. Branch conditions can also read variables, so a variable set in one arm can route later parts of the survey. Variables appear in the response detail view and as columns in exports.
End Survey¶
Ends the survey immediately when reached, useful inside branches for early exits (screening out, quota full). Participants reaching it complete normally and see the completion page.
Completion behavior¶
In Settings you configure what completion shows, a message (rich text, with {{ emb.key }} and a generated completion code placeholder available) or an automatic redirect to an external URL, also placeholder-aware, which is how participant IDs and condition labels travel back to panel platforms.
Logic and versions¶
Like everything else, logic edits belong to the draft you are editing and reach participants when you publish. Undo and redo cover Survey Logic changes, and deleted elements restore from the Recycle Bin.