Variables and piping
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}}.
Variable types
Section titled “Variable types”| Type | Plain-English meaning | Typical source |
|---|---|---|
| Question | Answer captured in the study | Question response |
| Participant | Known attributes of the person | Participant sample fields |
| URL | Values from the respond link query string | URL parameter |
| Session | Values for the current take | Session context (for example browser language) |
| System | Platform-provided values | System generated fields such as language or timestamps |
| Computed | Calculated from a formula | Formula expression |
| Custom | Values you define for the study | Manual or configured custom value |
Sources in the builder are labeled as question response, participant sample, URL parameter, system generated, and computed formula.
When to use each type
Section titled “When to use each type”- 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.
Piping
Section titled “Piping”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.
How to set up a variable
Section titled “How to set up a variable”- Open study logic / variables in the builder.
- Create a variable and choose its type.
- Map the source (question, sample column, URL key, formula, or custom value).
- Give it a stable name used in piping and conditions.
- Reference it as
{{variable_name}}in content or select it in logic rules. - Preview with sample values.
Example
Section titled “Example”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
planequalspro.
Limitations
Section titled “Limitations”- 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.
Related uses
Section titled “Related uses”- Drive display logic and branching.
- Feed randomization groups and compare assets.
- Personalize email templates and sample-based invites.
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.