Google Apps Script Automates Large-Scale Longitudinal Psychology Studies

Longitudinal research promises a view of how people learn, think, adapt and behave over time, but keeping hundreds of participants engaged across 20 sessions can become a logistical ordeal. A new open-source framework called GABLE turns familiar Google Workspace tools into an automated coordination system for multi-session online studies. The researchers behind the system report that it handled 12,982 session completions for 852 participants in two live cognitive-science projects while requiring little manual intervention and no dedicated servers for participant management.

The system, expanded as Google Apps Script-Based Longitudinal Experimentation, was described in Behavior Research Methods. GABLE is designed for a problem that often receives less attention than the experimental tasks themselves: researchers must continually coordinate enrollment, session timing, calendar invitations, reminders, completion tracking, protocol compliance and compensation. Manual workflows become increasingly error-prone when the number of participants, sessions or study duration rises, particularly because each participant may need a different schedule. GABLE automates this work through Google Forms, Sheets, Gmail, Calendar, Drive and Apps Script, while remaining compatible with externally hosted experimental tasks and data storage.

Rather than replacing specialized platforms for building behavioral experiments, GABLE functions as an automation layer around them. Experimental applications built with tools such as jsPsych, Gorilla or custom web code can continue to present tasks and collect behavioral data, while GABLE manages the participant-facing workflow. The separation is central to the design: coordination data, including participant identifiers, group assignments, session status and schedules, remain in the researcher’s Google Workspace account, whereas experimental records can be held in Qualtrics, Box, REDCap, the Open Science Framework, institutional storage or another researcher-selected service. The authors’ deployments used Microsoft Azure for task data and system logs, but the framework itself is not dependent on that provider.

Deployment begins by copying GABLE’s source code into a Google Apps Script project and editing a global configuration file. Settings define the number of sessions, experimental groups, permissible intervals between sessions, message templates, grace periods and incentive structure. The system then uses an event-based trigger to process registrations submitted through Google Forms and several time-based triggers to handle communication, data synchronization and administrative reporting. Every trigger execution appears in Apps Script’s built-in log with its status and messages, giving coordinators an audit trail without requiring a separate monitoring platform. A repository also includes a working jsPsych example based on the Stroop task, demonstrating the full pathway from registration through completion.

Participant scheduling is adaptive rather than fixed. GABLE creates a unique record and study identifier when a participant registers, assigns experimental conditions through a configurable round-robin algorithm and uses a participant’s preferred start time to establish the first appointment. Calendar invitations contain structured attachments that can appear in services such as Google Calendar or Outlook, even though participants do not need Google accounts. Subsequent sessions become available according to completion history and configured waiting periods, preventing a rigid calendar from creating conflicts when one person finishes early or late. The same logic can enforce a protocol in which each session opens 24 hours after the previous one and remains available for a one-to-three-day window.

The tracking spreadsheet serves as a live control center. Each row represents a participant, each column a session, and configurable cell colors indicate whether a session is upcoming, completed, approaching its deadline, partially attempted, within a grace period or invalidated. These same sheets can be edited when a participant needs an exception, such as a delayed start or an extra day to complete a task. The system propagates such changes through its connected workflows. For longer protocols, GABLE can activate grace periods only after a specified number of sessions, allowing extra flexibility for people who have already demonstrated sustained engagement. Reminders for unopened sessions and incomplete sessions are generated from configurable timing rules and templates, reducing the risk that a participant is locked out by a missed message.

Communication and compensation are integrated into the same automation. GABLE sends enrollment confirmations, task links, completion acknowledgments, deadline reminders, grace-period notices and exit messages through its linked Gmail account, substituting participant-specific information such as names, identifiers and session numbers. Messages are tied to changes in participant status, so the system does not send reminders outside a participant’s permitted timeline. At study exit, it calculates payment from rules that may reward each completed session, cumulative participation or a full-completion bonus. Available electronic gift-card codes are stored in a dedicated sheet, marked as used when allocated and linked to the corresponding participant identifier, creating a record intended to make payouts consistent and auditable.

The two real-world demonstrations recruited 852 participants for browser-based cognitive tasks and self-report measures. Each participant was assigned 20 sessions, scheduled approximately two days apart, with a session becoming available 24 hours after the preceding completion and a window of one to three days to complete it. The task applications were external to GABLE: one used Unity exported to WebGL and the other used Node.js. Of the initial enrollments, 593 participants completed all 20 sessions and 623 completed at least 10. The platform recorded 12,982 completions, automatically invalidated 604 accounts for missed deadlines or inactivity, sent 5,812 standard reminders and issued 570 grace-period notifications. Staff manually handled occasional requests such as deferred start dates and technical questions.

Reliability was high but not absolute, and the authors were careful not to claim that GABLE caused the observed retention. Neither study included a non-GABLE comparison, so differences in dropout cannot be attributed to the software. GABLE also did not eliminate the burdens of demanding protocols, nor can it solve the behavioral reasons people withdraw. During a representative seven-day period, the system performed about 1,900 automated operations with a logged error rate of 2.30%. Most errors were transient API timeouts or network delays that redundant triggers resolved without participant-facing failures. Progress was checked every five minutes, study emails were distributed hourly, and the registration and coordinator-summary functions recorded no failures in that period. Trigger frequencies are configurable and can be increased, although faster checks consume more of the Apps Script execution allowance.

GABLE’s accessibility comes with clear constraints. Its dependence on Google Workspace may conflict with institutional data-governance rules, Microsoft 365 environments or locally managed servers, although deployment through an institutional Google account can address some ownership and access concerns. Identifiable information stays within the researcher’s authenticated Workspace environment, while the task application receives only a study identifier; researchers must still align the arrangement with ethics, privacy and institutional review requirements. Apps Script quotas also cap very large operations, particularly outgoing email, and cloud-service outages can interrupt synchronization. The system is best suited to studies involving hundreds or thousands of participants and dozens of sessions rather than millions of participants or experiments requiring exact, sub-minute timing. Even with those boundaries, the demonstrations suggest that a low-cost stack of ordinary cloud services can remove much of the repetitive work of longitudinal research without dictating how the science is conducted.

Subject of Research: A Google Workspace-based infrastructure for automating participant management in online longitudinal psychology studies

Article Title: Introducing GABLE: Lightweight infrastructure for longitudinal experiments using Google Apps Script

Article References: Berber, I., Kas, I., Sepuri, T., Macnamara, B. N., Çavuşoğlu, M. C., Wilson-Delfosse, A. L., Krupinski, E. A., Smith, P. J., & Ray, S. (2026). Introducing GABLE: Lightweight infrastructure for longitudinal experiments using Google Apps Script. Behavior Research Methods, 58(11), Article 327. https://doi.org/10.3758/s13428-026-03205-8

Image Credits: AI Generated

DOI: 10.3758/s13428-026-03205-8

Keywords: GABLE, longitudinal studies, Google Apps Script, online psychology, research automation, participant scheduling, multi-session experiments, Google Workspace, behavioral research, open-source infrastructure, Introducing, Lightweight