Three phases and six stages, from designing the instrument to exporting the dataset — and, at every one of them, which part your team does and which part the platform does.
Experience sampling has a lot of moving parts — timing, notifications, compliance, payments. Here is where each one lands, and who handles it.
Build your surveys, choose the sensor streams you need, and set the schedule. No code, no app build, no store review.
Build the instrument in the browser: pick from twenty question types, add branching and piping, randomize order, and screen out careless responding before it contaminates the dataset.
No coding, no app to compile, no store review. Your surveys appear inside the participant app the moment the project goes live.
Choose the protocol your design calls for — fixed intervals, random signals inside a window, or participant-initiated events — or combine all three in one project. Add reminders and close times so responses can’t be backfilled.
Schedules follow each participant’s local clock and re-anchor automatically if they change time zone mid-study.
Participants download the free app and join. Prompts and sensor streams follow each participant’s local clock.
Distribute three ways: a project access code, an email allow-list, or project-scoped temporary accounts for fully anonymous collection.
Participants install the free app, enter the code, and consent — remote onboarding with no lab visit and no identifying information shared with you.
This is the part you don’t do. Prompts fire, participants answer where the experience is happening, and the data lands in your project.
Push notifications with email backup, multimedia answers with automatic transcription, GPS and wearable streams, and offline capture that syncs when a connection returns.
Track response rates while the study is still live, send reminders and anonymized payments, then export everything.
Watch response rates per participant in real time instead of discovering attrition at the end, and nudge individuals directly from the participant log.
Live dashboards, notification delivery logs, and event triggers that fire a contingent survey the moment a response crosses your threshold — the mechanism behind EMIs and JITAIs.
Pull everything as CSV, TSV, or XML — numeric or choice text, every response time-stamped and linked by one anonymous identifier, ready for multilevel models.
Voice and video answers arrive auto-transcribed, and participants are compensated with Amazon e-gift cards in-app, scaled to response rate, with no personal details collected.
As someone who isn’t a programmer, the no-code setup was a lifesaver. I designed and launched my entire ESM study in a single afternoon. Highly recommended for any researcher.
Indicative only — a rolling schedule gives every participant the same window whenever they start, so enrollment doesn’t have to be simultaneous.
No. Surveys are built in the browser and appear inside the existing ExpiWell participant apps — there is no app to compile and no store review to wait on. Participants download one free app regardless of which study they join.
Yes. Interval-contingent, signal-contingent, and event-contingent surveys can run in the same project, each on its own schedule, with responses linked by the same anonymous identifier.
Surveys open and save offline, then upload when a connection returns. Response timestamps reflect when the participant answered, not when the data synced.
Consent management is built into every study, and our team can walk yours through the IRB process. Anonymized collection and temporary accounts often simplify approval — the Trust Center holds the compliance documentation reviewers usually ask for.
Join over 7,000 researchers around the world and start collecting high-fidelity data today.