Quest Anatomy
Every quest contains a configuration object with the following components:| Component | Required? | Description |
|---|---|---|
| Prompts | Optional | Recurring questions delivered on a schedule. See Prompts. |
| Onboarding Questions | Optional | Pre-join screening questions for eligibility. See Onboarding. |
| Onboarding Overview | Optional | Rich HTML consent language shown before questions. See Full-Text Overview. |
| Experiments | Optional | Interactive jsPsych tasks. See Experiments. |
| Health Data Config | Optional | Toggles for collecting steps, sleep, and heart_rate from wearables. |
| Assignment | Optional | Python script for counterbalancing / conditional experiment assignment. See Ordering & Assignment. |
| Analysis Scripts | Optional | Python scripts that run against collected datasets for quality checks, metrics, and processing. See Analysis Scripts. |
| Post-Experiment Script | Optional | Python code to run after experiment completion. |
- review participants and cohort assignments
- update participant lifecycle status
- monitor collected datasets
- configure a compact baseline / follow-up schedule for cohorts
- review simple due / overdue compliance state
Prompts are no longer required to create or save a quest. This means you can run experiment-only, onboarding-only, or recording-focused studies without adding scheduled surveys first.
Quest Lifecycle
- Draft — Quest is created and saved but not yet visible to participants
- Published — Quest is live and accessible via its URL (consumes credits — see Pricing)
- Participant operations — Researchers manage participants, cohorts, and schedule/compliance state
- Data collection — Participants submit prompts, onboarding responses, experiments, recordings, and health data
- Unpublished — Quest is taken offline; existing data is preserved
Organization Scope
Every quest belongs to an organization. When creating a quest, you select the organization using a dropdown. All billable actions on the quest (publishing, participant joins, data submissions) are charged to the quest’s organization.You must create an organization before creating a quest. See Creating an Organization to get started.
Data Types Collected
| Dataset Type | Source | Description |
|---|---|---|
prompt_responses | Web / Mobile | Answers to recurring prompts |
onboarding_responses | Web / Mobile | Answers to onboarding questions (free — not billed) |
experiment_trials | Web / Mobile | jsPsych experiment results (stored in Azure Blob) |
brain_recordings | Web / Mobile | EEG recordings from Neurosity Crown or Muse |
health | Mobile | Steps, sleep, heart rate from wearables |
Next Steps
Creating a Quest
Step-by-step guide to building your first quest.
Participant Journey
See how participants move from onboarding into prompts, experiments, and study activities.
Prompts
Configure recurring data-collection questions.
Onboarding
Set up consent and eligibility screening.
Experiments
Add interactive jsPsych experiments.
Analysis Scripts
Automate data analysis with Python scripts.