Plan Incentives Before Publishing
If respondents receive compensation, course credit, or panel credit, the survey should make completion requirements clear. Incentive language usually belongs in consent, end screens, and any external recruitment instructions.
Decide before launch who qualifies for the incentive, what happens to screen-outs and quota-full respondents, whether a completion code is shown inside Domandata, and whether a panel redirect or outside payment workflow is involved.
Completion Workflow
Step 1: Explain the incentive early. Add incentive conditions to the consent or introduction when appropriate for the study.
Step 1: Explain the incentive early
Block Builder: Content Block
Add instructional text or embed a YouTube video as a stimulus.
Step 2: Screen before costly tasks. Use eligibility screeners and quotas before expensive study tasks or treatment exposure.
Step 2: Screen before costly tasks
Block Builder: Question Type
Use the question type selector to switch between multiple choice, slider, grid, ranking, and more.
Step 3: Create the completion screen. In Block Builder, add an end screen with completion instructions, code text, or redirect guidance.
Step 3: Create the completion screen
Block Builder: End Screens
Four path-specific end screens: Completion (with code), Screen Out, Quota Full, and Debriefing. Each routes from a Flow condition.
Step 4: Create alternate endings. Add separate ineligible or quota-full end screens when respondents should not receive the same message.
Step 4: Create alternate endings
Block Builder: End Screens
Four path-specific end screens: Completion (with code), Screen Out, Quota Full, and Debriefing. Each routes from a Flow condition.
Step 5: Connect endings in Flow. Route completion, screen-out, and quota-full paths with Flow to the correct end screens.
Step 5: Connect endings in Flow
Block BuilderPreviewDeployFlow Canvas
Interactive routing surface from the app, running in no-persist help mode.
Step 6: Test the exact live workflow. Use the draft or public link to complete the path, verify the code or redirect, and inspect the export.
Step 6: Test the exact live workflow
Block BuilderPreviewDeployPreview
Walk through respondent-facing behavior in the same preview surface.
Completion Codes And Redirects
If your recruitment source uses completion codes or external confirmation pages, put clear instructions on the final end screen. If the workflow uses a redirect, test it from the public survey link before launch.
- Static code: show the same code to every completed respondent only if the recruitment workflow accepts it.
- Panel redirect: test the redirect after a full completion path and after any screen-out path that should not receive credit.
- Course credit: explain whether students need to copy a code, submit a screenshot, or wait for manual confirmation.
- Partial completion: decide whether incomplete respondents receive anything, and make that rule clear in consent or recruitment text.
Deploy: Publish and Links
Deploy
Configure publishing, links, quotas, and theme from the Deploy tab.
Export Notes
Keep a record of completion status, end screen paths, and any recruitment identifiers allowed by your protocol. Do not collect personally identifying payment information inside the survey unless your study approval requires it and your workflow is designed for it.
Before paying or granting credit, compare the export against your planned eligibility, quota, completion, and quality-check rules. If you exclude responses from analysis later, keep the payment or credit decision separate from the analytic exclusion log unless your protocol says otherwise.
Deploy: Publish and Links
Deploy
Configure publishing, links, quotas, and theme from the Deploy tab.