Skip to content
Open fromusers

Variables and piping

SurveysUsability testsIn-product surveys

Variables store values you can reuse in question text, logic conditions, formulas, and asset rules. Piping inserts a variable into participant-facing text with {{name}}.

TypePlain-English meaningTypical source
QuestionAnswer captured in the studyQuestion response
ParticipantKnown attributes of the personParticipant sample fields
URLValues from the respond link query stringURL parameter
SessionValues for the current takeSession context (for example browser language)
SystemPlatform-provided valuesSystem generated fields such as language or timestamps
ComputedCalculated from a formulaFormula expression
CustomValues you define for the studyManual or configured custom value

Sources in the builder are labeled as question response, participant sample, URL parameter, system generated, and computed formula.

  • Question: pipe prior answers into later wording, or use them in conditions.
  • Participant: personalize invitations and in-study text from sample columns.
  • URL: pass campaign, variant, or CRM IDs on the shareable link.
  • Session / system: react to runtime context such as language or environment.
  • Computed: derive scores, flags, or labels with formulas.
  • Custom: hold fixed study constants used in multiple places.

Use the variable name inside double curly braces:

Thanks {{first_name}}. You rated us {{nps_score}}.

You can pipe into titles, descriptions, and placeholders. If a value is missing, configure a fallback where the builder allows it, or keep wording that still reads well without the value.

  1. Open study logic / variables in the builder.
  2. Create a variable and choose its type.
  3. Map the source (question, sample column, URL key, formula, or custom value).
  4. Give it a stable name used in piping and conditions.
  5. Reference it as {{variable_name}} in content or select it in logic rules.
  6. Preview with sample values.

Pass ?plan=pro on the respond link, store it as a URL variable named plan, then:

  • Pipe: You are evaluating the {{plan}} experience.
  • Display logic: show Pro-only questions when plan equals pro.
  • Names should stay unique and readable. Renaming breaks piping that still uses the old token.
  • Question variables resolve only after the source question is answered.
  • Computed variables depend on their formula inputs being available at evaluation time.

Common questions

What is the piping syntax?

Insert a variable with double curly braces around its name, for example {{first_name}} in a question title or description.

Can variables drive display logic?

Yes. Conditions can reference variables the same way they reference question responses.

Where do participant variables come from?

From participant samples you import, or from values attached to the invitation link and session context.