Back to Topics

Deployments & Google Forms

Learn how to mix your built assets into a secure Magic Link, configure Smart Routing, and pipe the data directly into your own Google Form.

What is the Deployment Combiner?

The Deployment Combiner is the final step before launching your trial. It allows you to select the various modules you've built (Consent forms, Question Banks, Tickets) and snap them together like Lego bricks into a single, unified "Magic Link" for your participants.

Bring Your Own Database (BYOD)

Blitztrials does not hold your clinical data hostage. By linking a Google Form, all assessment scores and raw answers are piped directly into your own Google Drive in real-time.

Conditional Smart Routing

Stack multiple Question Banks on top of each other and create logical pathways. Send users to different exams, or end the test early, based on their live scores or the time taken.

Silent Submissions

Create a frictionless UX. Participants take the exam on our beautiful UI, and when they finish, the system silently submits the data to your Google Form in the background without them ever knowing it happened.

Modular Security

Toggle features on and off instantly. Require IRB-compliant consent before the test starts, or force participants to enter a one-time-use Subject Ticket to gain access.

Part 1: Preparing Your Google Form Endpoint

To securely pipe your data out of Blitztrials and into your own database, you must provide a "Pre-filled Link" from a Google Form. This acts as the secure endpoint for our system to send the data.

Exact Text Required

When creating the pre-filled link, you must use the exact phrases MAGIC_ID and MAGIC_RESULT (all caps, underscore). The Blitztrials engine looks for these specific words in the URL to know where to inject the live data.

  1. Create the Form: Open Google Forms and create a new, blank form.
  2. Add Two Questions: Add two "Short answer" or "Paragraph" questions. You can name them anything you like (e.g., "Participant ID" and "Raw Assessment Data"). Make sure neither question is marked as "Required".
  3. Get Pre-filled Link: Click the three vertical dots (More menu) in the top right corner of Google Forms, and select Get pre-filled link. A new tab will open.
  4. Inject the Magic Words: In this new tab, type exactly MAGIC_ID into your first question box, and exactly MAGIC_RESULT into your second question box.
  5. Copy the Link: Scroll to the bottom, click "Get Link", and then click "Copy Link".
  6. Paste into Blitztrials: Return to the Blitztrials Deployment Combiner, paste that link into the URL box, and save!
Silent vs. Manual Submission

By default, Silent Background Submission is toggled ON. This provides the best user experience—when the participant finishes the test, the platform sends the data to your Google Form invisibly behind the scenes.

Why turn it off? If your Google Form is set up to strictly "Collect Email Addresses", Google blocks silent background submissions. You must uncheck the Silent toggle in Blitztrials so the user is forced to click a button that opens the Google Form manually. Additionally, if you require participants to submit file attachments (like a JPEG or PDF upload), you must toggle this OFF so they can attach their files directly in the Google Form at the end of the test.

Part 2: Smart Routing & Logic

If you assign more than one Question Bank to a deployment, you can use Smart Routing to direct participants dynamically based on their performance.

Write your rules one per line in the routing box using this exact syntax:

[Condition] [Operator] [Value] => [Action]
Available Operators & Conditions
  • Operators: Use == (Equal to), != (Not equal), > (Greater than), < (Less than), >= (Greater/Equal), or <= (Less/Equal).
  • Compound Logic (AND): Use && to combine multiple conditions on a single line (e.g., matching age AND gender for medical screening).
  • Condition: TOTAL — Evaluates the participant's total points across the current test.
  • Condition: TIME — Evaluates the total seconds taken so far.
  • Condition: [Subtotal ID] — Evaluates a specific custom subtotal you created in your Question Bank (e.g., HADS-A).
  • Condition: Q[Label] — Evaluates the exact answer chosen for a specific question (e.g., Q3 or Q1a).
Available Actions
  • GO_BANK_[Number]: Jumps the user directly to a specific bank in your stack. (e.g., GO_BANK_3 sends them to the third dropdown bank you assigned).
  • END_TEST: Immediately halts the assessment and submits their data, skipping all remaining banks.
Routing Syntax Examples

Here are real-world examples of how to format your routing rules:

# End the test early if they score less than 50 total points TOTAL < 50 => END_TEST # If subject is over 50 AND female, route to Menopause Screener (Bank 2) Q1 > 50 && Q2 == Female => GO_BANK_2 # If they answered "A" on Question 3, skip to Bank 4 Q3 == A => GO_BANK_4

Part 3: Access Limits & Quotas

Control exactly how many people can take your assessment, set specific demographic limits, and screen out invalid participants to protect your data integrity.

Global vs. Conditional Quotas
  • Global Submission Cap: A simple number (e.g., 100) that completely locks the deployment link for everyone once your total target sample size is reached.
  • Conditional Quotas & Screen-Outs: Uses the exact same syntax as Smart Routing, but the "Action" is the maximum number of people allowed. Setting a limit of 0 acts as an instant screen-out (discarding their data). Setting a limit of 30 will cap that specific demographic profile at 30 successful submissions.
Quota Syntax Examples
# Screen-out (terminate) speeders who finish under 10 mins (600 seconds) TIME < 600 => 0 # Cap the number of people who chose answer A to a maximum of 30 people Q1 == A => 30 # Compound Quota: Cap Female participants who score above 85 at 15 total TOTAL >= 85 && Q2 == Female => 15

Part 4: Module Configurations

Customize the testing environment by snapping in different operational modules:

Require Informed Consent

Essential for Institutional Review Board (IRB) clinical compliance. Toggling this ON forces a legal screen to load before the trial begins. Participants must explicitly read and click to accept your designated consent terms, or the engine will safely lock them out of the assessment.

Secure Subject Tickets

Tie access to an isolated participant batch. For elite research compliance, this module forces subjects to type both a valid ID and password to access the platform. By default, tickets are Single-Use (burning the token upon submission), but you can toggle "Allow Multiple Uses" if a subject needs to fill out the form repeatedly using the same login.

Assessment Banks & Bias Control

Stack multiple Question Banks onto a single testing track. By default, live scoring rule banners display to the user. **For blind trials or psychological exams, uncheck "Show Scoring Rule Banners"** to hide point structures, or if you are directing the user to perform an independent action like uploading a JPEG or PDF file to Google Drive at completion.

Continuing Medical Education (CME) Certificates

Link a certificate layout template directly to your workflow. If a participant successfully reaches or beats the specific passing target score configured within your template, the closure screen dynamically updates to offer them a downloadable, print-ready, high-resolution PDF certificate.

Custom Institutional Branding

Personalize the complete user experience. If your administrative account has an institutional workspace profile configured, it will cleanly embed your organization's official title and logo at the top of the testing frame. If no profile exists yet, you can use the manual overrides directly in the module card to supply a temporary image URL and text title.