Skip to main content
Onboarding questions are pre-join screening questions shown to participants after the full-text overview (if configured). Use them for eligibility screening, demographic collection, and baseline data.

​
Question Fields

Each onboarding question has:

​
Response Types

Onboarding questions support the same 5 response types as prompts:

​
Custom Options Rendering

The rendering of customOptions depends on whether a question guard is set:
  • If the guard uses in or not_in → checkboxes (multi-select), answer stored as comma-separated values
  • Otherwise → radio buttons (single-select)
Options in onboarding questions are entered as comma-separated values (e.g., Student, Professional, Retired, Other). This is different from prompt custom options, which use semicolons.

​
Adding Questions

  1. Open your quest in the editor
  2. Navigate to the onboarding section
  3. Click Add Question
  4. Enter the question text
  5. Select a response type
  6. If using customOptions, enter the options
  7. Optionally toggle Required (on by default)
  8. Optionally add a validation rule (question guard)

​
Validation

Client-side: All required questions must have a non-empty, trimmed answer before the form can be submitted. Server-side: If any question has a question guard, the answers are validated server-side. Failed validations show rejection messages and block the participant from joining.

​
Data Storage

  • Onboarding responses are saved as a dataset with type onboarding_responses
  • Source is tagged as web or mobile depending on where the participant completed onboarding
  • Onboarding responses are free — they are not billed
Onboarding responses are submitted before the participant joins the quest. This is different from prompt responses, which are submitted after joining.

​
Example

A typical eligibility screening setup: