Piping and Recall
Piping (also called recall) lets you drop a value into question text, help text, or other rich text instead of retyping it. Pull in a name from the email list that invited them, what they already answered, a value that arrived with their link, or an item they just ranked. The survey fills it in as it renders.
Where to insert a recall token
Click into a question prompt, help text, or other rich text field in the Survey Builder. The same control appears on email/SMS Survey Triggers (subject and message body).
Click the Insert recall / piping button (clipboard icon) in the text toolbar.
Pick what you want to recall from the Insert recall menu. What you're inserting determines what happens next — see the sections below.
The menu lists earlier questions, Contact fields, embedded data, and — on restricted surveys — Access ID data. Long prompts are truncated in the list, so hover an entry if you're not sure which question it points to.
Contact fields live on the Survey Builder (question text, help text, labels, end screens). They are not on Survey Triggers. Trigger emails still recall answers and embedded data; they do not fill {{contact.*}}.
What you can recall
Contact fields
Use this when the person arrived through a signed email invitation — Send to Email List or an Email → Campaigns send with survey tracking on.
A public Quick Share link, interviewer / kiosk session, or a pasted anonymous URL has no contact attached. Those tokens stay empty.
In Insert recall, open Contact fields:
- Standard fields (all lists) — First Name, Last Name, Full Name, Email, Company, Job Title, Phone, External ID
- Contact lists — pick a list to see that list’s standard fields plus any custom columns
Picking a list does not bind the token to that list. It is only how you find the column name. The saved token looks like {{contact.first_name}} or {{contact.department}}. Custom labels are normalized (spaces and punctuation become underscores: anothr 1 → {{contact.anothr_1}}).
You do not need Include email list columns in survey data for this. That picker copies fields into Raw Data / exports. Contact recall reads the live contact record when the signed link starts the session. Edit the contact after send, before they click, and the survey sees the new value. The Raw Data snapshot stays frozen at send.
| Field | Token | Empty contact |
|---|---|---|
| First Name | {{contact.first_name}} | Blank in the survey. Email bodies that use {{first_name}} still fall back to “there.” Those are different systems. |
| Last Name | {{contact.last_name}} | Blank |
| Full Name | {{contact.full_name}} | First + last. If both are empty, the part of the email before @. |
| Email, Company, Job Title, Phone, External ID | {{contact.email}}, {{contact.company}}, … | Blank |
| Custom column | {{contact.your_key}} | Blank |
In the builder and Test Survey, there is no recipient, so the token stays visible. That is useful. Live respondents never see the curly braces — a missing value just leaves a hole in the sentence. Write copy that still reads if the name is empty, or keep those questions behind an email-only deploy.
This is not Embedded Data, not Access ID data, and not the optional Email list data columns in analytics. Three stores. Do not mix the tokens.
Embedded data
Fields you've defined in Tools → Embedded Data — campaign codes, panel IDs, source tags — show up in the menu as Embedded Data - Display Name. Inserting one drops in a token like {{ed.campaign_id}}.
Embedded data is metadata that arrived with the respondent (through the survey link or a default value), not something they answered in the survey. See Embedded Data for how to define fields, pass values through links, and set defaults.
Access ID data
On surveys set to Restricted (requires access ID), fields you imported with custom Access IDs and marked Recallable appear in a separate group: Access ID data. Inserting one pipes the value stored on that respondent’s Access ID — for example a segment or wave you already knew — not an answer they typed.
This is not the same as embedded data. Access ID values are attached to the ID they used to start. Link query parameters cannot override them. Only recallable fields show in the menu. PII fields stay off recall unless you confirmed that during import.
Setup: Restricted Survey Access.
Question and answer recall
Most question types recall as a single value — the answer a respondent gave to that question. Select the question from the menu (for choice questions, Selected answer) and its answer is inserted, so:
You said your favorite feature was {{Q3}} — tell us more about that.For choice-based questions, this pipes the option label, not an internal value or code.
What a bare recall like {{Q3}} means depends on the question type:
| Question type | Bare recall ({{Qn}}) shows |
|---|---|
| Choice questions (single/multiple choice, dropdown, and similar) | Selected option labels |
| Matrix / Matrix (Multi-Select) | A row summary (each row with its chosen column labels), same idea as All rows |
| Rank Order / Group Ranking | The full ranked list, same idea as All ranked items |
| Multi-field Short Text / Long Text | All non-empty fields, same idea as All fields |
Matrix row recall
Matrix and Matrix (Multi-Select) questions open a submenu instead of a single insert:
- All rows — every row’s answer in one piped value (for example,
Speed: Excellent; Price: Good) - Each row by name (or Row 1, Row 2, …) — just that row’s selected column label(s)
Other-specify text
When a question has Other Specify options, the Insert recall menu also offers:
- All other-specify texts — every other-specify answer joined together
- Each other option by label (or Other 1, Other 2, …) — just that write-in (
{{Qn.oeN}})
On Multiple Choice (and other choice types with more than one Other Specify option), each selected Other keeps its own write-in. Pick the specific Other in the menu when you need one of them; don’t assume every Other slot shares the same text.
On Rank Order and Matrix questions, these other-specify choices appear inside the same submenu as the rank or row options.
Multi-field short and long text
When a Short Text or Long Text question has more than one field, the menu offers:
- All fields — every non-empty field as one piped value
- Each field by label (or Field 1, Field 2, …) — just that field’s text
Ranked item recall
Rank Order and Group Ranking questions get their own submenu instead of a single insert, because a ranking produces an ordered list rather than one answer:
- All ranked items — the full ranked list as one piped value (for example, "Speed, Price, Support")
- Rank #1, Rank #2, and so on — just the item that landed in that position
If the ranking question also has Other Specify, those write-in recalls appear in the same submenu under the rank positions.
For Rank Order questions limited with Max items to rank, only the positions a respondent actually ranked are available to recall. For Group Ranking, position reflects the flattened order across groups (top group first, then the next, each in the order the respondent sorted them); items left unassigned never get a position.
Computed (Hidden) recall
Computed (Hidden) value questions also open a submenu, because one computed question can store several expression results plus an optional combined final:
- Final / sole expression — the combined
finalwhen a Final output function is set; if Final is None and you defined exactly one expression, that expression’s value - Final only — the combined
finalonly (blank when Final = None) - All expressions — every finite expression value, comma-separated (shown when you have more than one expression)
- Each expression by label (or Expression 1, Expression 2, …) — that expression’s numeric result
The base token is the computed question’s question number (for example {{Q5}}, or {{COMP1}} if you renamed it). Suffixes look like .final, .e1, and .eall.
With multiple expressions and Final = None, the bare token stays empty—pick a specific expression or All expressions.
Computed list outputs are recalled like other choice-style answers when available; the expression submenu above applies to value computation.
Token reference (optional)
You usually don’t need to type tokens by hand — use Insert recall. If you see tokens in existing text, here’s what they mean:
| Menu choice | Typical token |
|---|---|
| Selected answer / bare question | {{Q3}} |
| All rows / one row | {{Q3.rowall}} / {{Q3.row1}} |
| All fields / one field | {{Q3.fall}} / {{Q3.f1}} |
| All ranked items / Rank #1 | {{Q5.rall}} / {{Q5.r1}} |
| All other-specify texts / one other | {{Q3.oeall}} / {{Q3.oe1}} |
| Computed final / sole expression | {{COMP1}} |
| Computed final only | {{COMP1.final}} |
| Computed expression / all expressions | {{COMP1.e1}} / {{COMP1.eall}} |
| Embedded data | {{ed.campaign_id}} |
| Access ID data | {{aid.segment}} (field key from import) |
| Contact field | {{contact.first_name}}, {{contact.company}} |
Common uses
- Personalize later questions with an earlier answer: "Earlier you mentioned
{{Q2}}. How long have you used it?" - Confirm a respondent's top pick before asking a follow-up: choose Rank #1 from the ranking question in Insert recall
- Pull one Matrix row into a follow-up: choose that row under the Matrix entry in Insert recall
- Show a derived score or total months from a Computed (Hidden) question: choose Final / sole expression or a specific expression label
- Reference where someone came from without asking again: "Thanks for joining from
{{ed.campaign_id}}." - Personalize a restricted survey from imported Access ID fields: pick Access ID data in Insert recall (for example a segment label)
- Greet an email-invited respondent by name: Contact fields → First Name (
{{contact.first_name}}) - Summarize a full ranking on a review or thank-you screen: choose All ranked items
Tip
Always preview a survey after adding recall tokens. A token with nothing to recall (a skipped question, an unranked position, a missing embedded data value, a computed expression that stayed null, an Access ID field that was not marked Recallable, or a contact field on a link that is not a signed email invitation) renders as blank rather than breaking the page — good to confirm before you launch. For contact tokens, send yourself a real invitation. Test Survey will not fill them.