Survey

Connect research questions to measurements

Use Design → Research to record why you are running the study, and Variables to describe what you will measure. These descriptions help collaborators understand the survey; they do not create participant questions automatically.

For the browser-extension walkthrough, first define the variables and route, then write the extension content and two outcome questions. You can record research notes earlier; linking sources needs the questions to exist.

Record the research plan

For the browser-extension study:

  1. In Research, open the Goal Understand decisions about browser-extension permissions from the design guide. Add it if you are starting here.
  2. Edit its existing willingness-to-install research question to Does explaining requested capabilities change willingness to install, and does this differ between the two extensions? If you are starting here, use Add research question.
  3. Under that question, choose Add hypothesis: Explanation text increases willingness to install the Pomodoro timer more than the adblocker.
  4. Add a second research question, Does explanation text improve understanding of the requested capabilities?, with the hypothesis Explanation text increases understanding of requested capabilities.
  5. Use notes to record the rationale and planned comparisons. Design notes in the Design section can hold the overall plan.

Research questions describe the study. Survey questions are the controls participants answer in Content. You can record the plan first and connect sources after you have written those questions.

  1. In Variables, add Willingness to install. Leave How is this variable obtained? as Measured in the survey.
  2. Choose Measurement method → Direct survey value.
  3. Select Add source, then select the Would you install [Extension name]? question from Permission decision. Select the whole question for this example.
  4. Use Open in Content or Open in Flow beside a source to inspect the connected item.

Create Permission understanding as a measured variable. Choose Calculated after export, link the comprehension Text question already on Permission decision, and describe your coding rubric in Scoring notes. The tool records your scoring plan; it does not grade these answers automatically.

Return to the research questions and hypotheses in Research. Link Permission and Priming as Independent variables, the conditions you vary. Link Willingness to install and Permission understanding as Dependent variables, the outcomes you measure.

For other studies, you can create a missing question from the source picker: expand Create a question, choose its page and type, then select Create and link question. Finish its prompt and options in Content.

The source picker also offers supported timing metrics and Flow values. For an outcome computed during the survey, calculate it in a JavaScript node, then link its saved Flow value as the source.

Describe the data and analysis

Declared data type records whether the measure is Boolean, Number, Text, or Category. Measurement level describes how it can be interpreted: Nominal for unordered categories, Ordinal for ordered categories, Interval for equal differences, or Ratio for equal differences with a meaningful zero. Leave either unspecified until decided.

These fields describe your intended analysis. They do not add question validation, convert exported answers, or calculate scores. Configure the question itself to control the answer it accepts.

For the Yes/No installation question, Category and Nominal describe the recorded choice. For the comprehension score, record the intended coding and interpretation in Scoring notes.

Repeated measurements and linked questions

The Permission Loop presents both questions once per extension and collects separate answers per iteration. One source question can therefore supply repeated measurements. Revisiting an ordinary question updates its existing answer rather than creating a new occasion.

For measurements on separate pages, add multiple source questions and place them at the intended points in Flow. If their wording should stay synchronized, create linked questions. Linking an outcome to a source and linking question wording are separate operations. The separate question sources identify the before and after measurements; adding both sources does not compute a change score.

For a completed response in this example, expect one installation answer for Broad and one for Simple, both under the same Priming profile. Inspect a pilot export and its column mapping to verify the source and iteration associations.

Warnings identify missing sources, removed questions, or coverage that needs checking. Replacing a removed source is an explicit choice: select its replacement or remove the link. Test the actual route in Preview: a linked source can still be bypassed by a branch.

Next: Test both Priming profiles and both extension orders, then check a published pilot export.

Confirm action