Text piping is the survey feature that takes something a respondent already told you, their name, the product they bought, the branch they visited, the answer they gave two pages ago, and drops it into the wording of a later question. Somebody picks “Downtown branch” at question 3, and question 7 asks how long they waited at the Downtown branch. The next person picks “Airport” and reads about the airport. One survey, two readers, no extra work from either of them.
A generic question gets a generic answer, which is the whole case for piping. “How satisfied were you with the location you visited?” makes people work out which visit you mean, and a fair few of them guess. Ask about the Downtown branch by name and they’re back in the lobby, looking at the line. The answer you get is about that visit, which is the one you wanted.
The definition comes first. Nine piped text examples you can copy come straight after it, because the setup steps make more sense once you’ve seen what the result looks like, and the syntax and the ways it goes wrong round things off.
Key takeaways
- Piped text drops a respondent’s earlier answer, or a field from your contact list, into the wording of a later question. From the respondent’s seat there’s no mechanism at all, only a question that happens to know what they said on the last page.
- Two separate features get called piping. One inserts an answer into question text. The other copies answer options from an earlier question into a later one, so somebody who owns three of your eight products rates three.
- The source question has to sit on an earlier page than the question that uses it, and it should be mandatory, since a blank source produces a blank in your sentence. “How satisfied were you with ?” is what 40 respondents read before anyone noticed.
- It works in anonymous surveys as long as the piped value comes from the survey itself. Pipe a name from the contact list into an “anonymous” employee survey and you’ve told the respondent, correctly, that you know who they are.
What is text piping in surveys?
Text piping in surveys is the practice of inserting a value the survey already holds, usually a respondent’s answer to an earlier question, into the text of a later question, instruction or answer option, so each person reads wording built from their own responses. The name is plumbing: a pipe carries the answer forward from one spot in the survey to another. You’ll meet it under other names too, dynamic text, merge fields, placeholders, question piping, and when a colleague asks what is piped text, the shortest honest answer is a placeholder with the respondent’s own answer already in it.
The value can come from three places. It can be an earlier answer in the same survey, which is the common case. It can be a field in your contact list, such as a first name or an account number, which gets merged in when the invitation goes out. Or it can ride in on the link itself, so everyone who arrives through the Denver store’s link sees “Denver” without being asked. Sogolytics has a separate control for each: the piping feature, mail merge in the invitation, and URL-based pre-population.
Say a hotel group with 14 properties runs one post-stay survey, and question 2 asks which property the guest stayed at. From then on, every question that would have said “the hotel” says “the Lakeside Inn” or “the Harbor Suites”, and the open-ended question at the end asks what the Lakeside Inn could have done better. The guest never notices. The analyst does, when the open-ended answers stop mentioning the wrong property.
What are some examples of piped text in surveys?
The piped text examples below are the nine patterns that turn up in almost every survey program. The part in square brackets is what the survey fills in, from an earlier answer or from a contact field.
- The product by name. “You told us you bought the [Product name] in the last 30 days. How often have you used it since?” The source is a product picker on the previous page. Without piping, this is “the product you purchased”, and a customer who bought two things has to pick one.
- The location, branch or store. “How long did you wait to be served at the [Branch] location?” The source is a branch dropdown, or the branch comes from a unique link per site.
- The person’s own rating, played back. “You rated your onboarding a [Rating] out of 10. What was the main reason for that score?” Playing the number back makes the follow-up feel like a conversation, and it stops people from explaining a 9 when they’d given a 6. Most customer satisfaction survey questions with a why-question attached benefit from it.
- The chosen answer, in the follow-up. “You said [Reason] was the main reason you considered switching. What would have changed your mind?” The source is a single-select reason question.
- The name from the contact list. “Thanks for your time, [First Name].” In Sogolytics this one is a mail merge field in the invitation, written as {{First Name}}, rather than in-survey piping. The respondent can’t tell the difference.
- The employee’s manager or team. “How often does [Manager name] give you useful feedback?” The manager comes from the HR file through pre-population, so the respondent never has to type it and never spells it wrong. It’s the single most useful piped field in a set of employee survey questions.
- The event they attended. “Which session at [Event name] did you find most useful?” One survey then covers all six events, and nobody has to merge six reports in December.
- The answer option piped as a list. “Which of these features do you use at least weekly?” where the list holds only the features the respondent said they’d heard of. This is answer piping rather than text piping, and it’s covered in its own section below.
- The open-ended answer, quoted back. “Earlier you wrote: ‘[Open answer]’. Is there anything you’d add?” Use this one sparingly. People are surprised to see their own words, and a long answer makes a long question.
Say you look after a customer survey for a software company with four products. Examples 1, 3 and 8 together turn a 30-question survey about every product into a 12-question survey about the one each customer owns, with the follow-up quoting that customer’s own score. Completion goes up. The “why are you asking me about a product I don’t have” emails stop. And you never built four surveys.
How to set up text piping in a survey?
Write the source question first
The source question gets written first, and it goes on an earlier page than any question that will use it. Piping can’t pull from a question on the same page, and it can’t run on a one-page survey at all, since the answer has to be saved before the next page loads.
Make the source question mandatory
The source question gets set to mandatory. Leave the source optional and anyone who skipped it meets a hole in the later sentence. That hole is the one thing they’ll remember about your survey.
Draft the destination question
The destination question gets drafted with a gap where the answer belongs, and “How long did you wait at the ___?” is plenty for now, since the gap gets filled in the next step.
Insert the pipe in the editor
In the question editor you open the destination question with Edit, and the Piping option drops the piping icon at the gap. A dropdown lists the questions on earlier pages, you pick the source, and that’s the whole click. One source question can feed up to 40 answer options in Sogolytics.
Read each answer in place
The sentence gets read aloud with each possible answer in place. “How long did you wait at the Other?” only turns up when you try every option, and the “Other” choice usually ends up needing its own wording or a skip.
Add display logic where needed
Display logic gets added where a piped answer shouldn’t appear at all. Somebody who said they never visited a branch shouldn’t see a branch question with a blank in it, and question display logic is what hides it for them.
Preview once per answer
The survey gets previewed end to end, once per source answer, before anything goes live. Piping bugs only ever show up on the respondent’s screen, never in the designer.
Setting up text piping in a survey is four decisions and a few clicks. The clicks are the easy part. All of it sits on top of the ordinary work of creating a questionnaire, so the questions want settling before any of this starts. Sogolytics inserts the piped answer with a piping icon in the question editor, no typed code involved, and the steps below follow that flow.
Picture a marketing manager building a webinar feedback survey. Page 1 asks which of three sessions the person went to. Page 2 asks “What was the most useful part of [Session]?” She makes the session question mandatory, places the piping icon, picks the source from the dropdown and previews it three times, once per session. On the third pass the session title wraps the question onto three lines on her phone, so she shortens the option label. Twenty minutes, start to finish, including the fix.
What are the common uses of piped text?
Piped text in surveys turns up wherever one questionnaire has to serve people in different situations, which is most questionnaires. The uses that come up most:
- Customer feedback after a purchase or visit, where the product, store or agent gets named in every follow-up question instead of “the item” or “the location”.
- Follow-up questions on a rating, where the score the respondent gave is played back in the question that asks why.
- Employee surveys with a manager or team field. Each person gets asked about their own manager by name, and “your supervisor” stops meaning three different people to someone with a dotted line.
- Event and training feedback. One survey covers the whole conference. Each respondent sees the title of the session they sat in, so the keynote and the 2pm breakout get scored separately.
- Multi-product research. A respondent rates only what they own, because the list was built from page 1.
- Patient and client follow-up. The appointment date, clinic or procedure comes from the record, and “your visit on March 4” gets a better answer than “your recent visit” from someone who’s been in twice.
- Screening and routing. A respondent’s segment gets written into later wording, so a small-business owner reads questions about her business rather than about “your organization”.
- Chat-style surveys. Each question picks up the last answer, which makes the sequence read like an exchange instead of a form.
Most of these use survey question types you’d reach for anyway. What piping changes is that the question’s text knows what the person said, so the Likert row or the open-ended box is about the specific thing rather than the category.
Benefits of using text piping in surveys
The benefits of text piping are mostly about the quality of what comes back rather than the look of the survey, though it does look better too.
- Answers about the right thing. When the question names the branch, the respondent answers about the branch. When it says “the location you visited”, a share of respondents answer about the wrong one, and you can’t tell which.
- Shorter surveys. One piped question replaces a block of near-identical questions, one per product or location, most of which any given respondent would have skipped.
- Fewer drop-offs, which is the hardest part of increasing survey response rates to move. Heerwegh and Loosveldt found that personalizing a web survey raised the response rate from 53.5% to 62.9% and cut break-offs from 14.2% to 9.0%. Their personalization was in the invitation rather than the questions, but the mechanism, a survey that appears to know who it’s talking to, is the same one piping uses.
- Better open-ended answers. “What could the Lakeside Inn have done better?” gets a specific complaint. “What could we have done better?” gets “nothing” and “the price”.
- Less memory load. The respondent isn’t holding their earlier answers in their head to make sense of a later question, which matters most on long surveys and on a phone on a train.
- One survey instead of many. A chain with six regions runs one project and gets one report, where before it ran six variants and spent a week merging them.
- A conversational feel. Playing a score back before asking why reads as a person following up, and people write more for a person than for a form.
[Source: https://www.scb.se/contentassets/ca21efb41fee47d293bbee5bf7be7fb3/an-experimental-study-on-the-effects-of-personalization-survey-length-statements-progress-indicators-and-survey-sponsor-logos-in-web-surveys.pdf]
The response-rate point deserves a caveat. Personalization helps most when respondents would otherwise feel like one of thousands; a 12-person team survey won’t move on it. The cleaner win from piping is in what people write when the question is about their own case, and that shows up in every size of survey.
How to pipe responses into survey answer choices?
Build a compatible source question
The source question gets built as a multi-select, single-select, dropdown, ranking or rating question, since those are the types that can feed an answer set. Open-ended questions can’t be a source here.
Add the destination question later
The destination question gets added on a later page, in a type that accepts piped options: check box, radio button, dropdown, list box, ranking, numeric allocation, or one of the grid and rating variants.
Open the Pipe Answers control
In the destination question’s editor, the Pipe Answers control above the answer block opens a window where the source question is chosen.
Set the piping condition
The condition gets set. The options are all answers, selected answers, unselected answers, displayed answers or not displayed answers; a ranking source also offers the highest-ranked and lowest-ranked answer. “Selected answers” is the usual choice, so the respondent sees only what they picked.
Add and check fixed options
Any fixed options get added alongside the piped ones, such as “None of these”, and every option label gets checked for uniqueness, since two identical labels confuse both the respondent and the report.
Save and preview three ways
The question gets saved and previewed once with nothing selected at the source, once with one option and once with all of them, because an empty piped list is the failure mode nobody tests for.
Piping responses into answer choices means a later question’s options are built from what the respondent chose, or didn’t choose, earlier. Ask which of eight streaming services someone subscribes to on page 1, and page 2 asks which of those, and only those, they’d cancel first. Sogolytics calls this piping answers into answer sets, and it has its own control in the question editor.
Picture a retailer asking which of its six store departments a customer visited, then asking them to rank only those departments by how helpful the staff were. A customer who visited two departments ranks two. One who visited all six ranks six. Without answer piping, everybody ranks six, including four they never saw, and the ranking data for those four is noise.
Two limits are worth knowing in advance. Answers can’t be piped from a question that has hidden post-population applied, and once responses have come in, piped answers that already hold data stay in the question even if you remove the piping. Build the piping before launch and leave it alone afterward, so the report stays clean.
What is the syntax for implementing text piping?
The syntax for text piping depends on where the value comes from, and there’s less of it than you’d think. Picture a researcher setting up a customer survey who wants three things piped: the customer’s first name in the invitation, their chosen product in question 7, and their region from the link they clicked. She’ll type exactly one of those.
- Step 1: The first name is a mail merge field in the invitation, and this is the one she types. A field goes in double curly braces and has to match a column in her contact list:
Hi {{First Name}},
We’d like two minutes of your time on your recent visit to {{Branch}}.
The column header has to match, down to the space. When she sends, the Mail Merge step asks her to map each field and to set a generic replacement for blank values, and that replacement is what saves the 140 contacts with no first name on file from an email that opens “Hi ,”. Subject lines take merge fields too.
- Step 2: The product name in question 7 is in-survey piping, and she places it rather than typing it. The piping icon goes where the answer belongs, the dropdown picks question 3 as the source, and the survey stores a reference to question 3 behind the scenes. Written out, that reference behaves like this:
How long did you wait to be served at [Q3 answer]?
She never types the bracketed part. The editor inserts it and keeps it pointed at question 3, right up until somebody reorders the survey and question 3 becomes question 5, which is why piping gets checked after any restructuring.
- Step 3: The region rides in on the link, through URL-based pre-population. In Utilities she chooses the project, marks the region question as hard coded or variable, and generates the link, which gives her one URL per region with that region’s value built in:
https://survey.example.com/s/abc123?branch=Denver
That’s the general shape of a parameterized link. The exact URL Sogolytics generates comes from the Utilities page, and it has to be shared as generated, because editing it drops the pre-populated values.
The rule across all three is that the survey can only pipe what it already holds. The contact field has to be in the list before the invitation goes out. The answer has to be saved on an earlier page. The link value has to be in the link. Test each one with a real value and with a blank, and that’s the whole quality check.
What should you know before using text piping?
Text piping fails quietly, and that’s the main thing to know before using it. A broken piped field throws no error. What you get instead is a sentence with a gap in it. The respondent guesses what you meant, or closes the tab. Picture “How would you rate your experience with ?” landing in 2,000 inboxes at 9am on a Tuesday while your team is in standup, and nobody having seen it coming because the preview ran on a test account where every field was filled in.
The second thing is that piping changes what a question measures. Ask about the Downtown branch by name and you’re asking a different question from “the location you visited”, so if last year’s survey used the generic wording, this year’s numbers won’t sit on the same trend line. Pick which matters more, the trend or the specificity, before you switch.
The third is privacy. In an anonymous survey, piping an earlier answer is fine, since the survey already has it. Piping a name, a manager or an employee ID from the contact list is a different thing, because it shows the respondent that the survey knows who they are, which is the whole worry behind anonymous surveys for employees. The Sogolytics Experience Index: Employee Edition Q3 2026 shows what that confidence is worth: 79% of employees who are very confident their feedback is anonymous respond regularly, against 38% of those who are less confident. A piped name in a survey that was promised as anonymous spends that confidence for nothing.
Before launch, run this list:
- Every source question is mandatory, or else the destination has display logic that hides it when the source is blank.
- Every source question sits on an earlier page than every question that uses it.
- Each possible source answer has been read in the destination sentence, including “Other” and “Prefer not to say”.
- Piped options that could come back empty have a fixed fallback option beside them.
- Contact fields have a generic replacement for blank values set in the mail merge step.
- The anonymity promise in the invitation matches what the survey pipes. If it says anonymous, nothing from the contact list appears in the questions.
- Any question that changed wording because of piping is flagged in the trend report.
- The survey has been previewed on a phone, since a piped product name like “Professional Edition Annual Subscription” pushes a question onto three lines.
Skip logic trips piping in a way that’s easy to miss. Say page 2 is skipped for existing customers; nothing on page 2 can then be piped into page 5 for them, and the reference comes back blank. Map the skip paths first, and pipe only from questions that everyone on a given path answered.
Conclusion
Piped text makes a survey read as though somebody wrote it for the person answering. The payoff is answers about the right thing, a shorter questionnaire, and fewer people quitting at question 14. Sogolytics builds the three routes into the platform: Question Piping and Answer Piping in the survey designer for earlier answers, mail merge for invitation fields, and pre-populated links for values you already hold, with single-use invitation links so each respondent’s piped values stay their own.
FAQs about piped text
How does text piping personalize survey questions?
It rewrites each question around something the respondent already told you. “The product you bought” turns into “the Model X”, “your supervisor” turns into “Priya”, and the person answering is thinking about Priya rather than about supervisors in general, which is faster and involves less guessing.
Can text piping work with conditional survey logic?
Yes, and they belong together. Display logic settles whether a question shows up at all, and piping settles what it says once it does, so the customer who told you at question 2 that they never visited a branch is never shown a branch question with a hole in it.
Does piped text improve survey completion rates?
The evidence is for personalization in general rather than piping on its own: Heerwegh and Loosveldt measured a rise from 53.5% to 62.9% in response rate and a drop in break-offs when invitations were personalized. Inside the survey, piping’s clearer effect is fewer irrelevant questions, which is where most mid-survey drop-off comes from.
Can piped text be used in anonymous surveys?
Yes, as long as the piped value comes from the survey itself; an earlier answer identifies nobody. Pipe a name, employee ID or manager from the contact list into a survey you’ve called anonymous and you’ve broken the promise, and respondents notice that sort of thing.
What should you do if text piping does not display the correct response?
Page order is the usual culprit, since the source has to sit on an earlier page than the destination. If that’s fine, look at whether the source was answered rather than skipped, and whether the piped reference still points at the right question after somebody reordered the survey. Once those pass, preview with each possible source answer, because the wrong value usually shows up for one option rather than all of them.


