The Questions tab of the survey editor lists every question in your survey in one table, and it is where you control how each question is named in reporting. The table has four columns — Reporting Label, Question, Tags, and Actions — with a search bar above it that filters by question text or reporting label.
Renaming reporting labels
The reporting label is the short name the platform uses for a question everywhere outside the survey itself: the question picker on a report's Scope step, row and column headers in crosstabs, and data exports — the long Excel format, for example, writes it as the reporting_id column. A question programmed as "Which of the following brands have you purchased in the past 3 months?" is much easier to work with in a report when its label is simply "Brands Purchased P3M".
To rename a label, click into the Reporting Label cell and type — the field edits inline, with no separate dialog. If a question has no label of its own, the cell shows the full question text as a placeholder. When you're done, click Save in the survey editor; the survey updates briefly and the new labels flow through to reports.
Two things to know:
- Labels are read-only while the survey is updating, and when you only have read-only access to the survey.
- Surveys within the same project share default reporting labels, which keeps names consistent across waves of a tracker. Renaming a label never touches the survey code or what respondents see — it only changes how the question is identified in reporting.
The Question and Tags columns
The Question column shows each question's full text, so you can confirm which question a label belongs to at a glance.
The Tags column shows any tags attached to the question in the survey code with s.tag(...) — for example a brand or platform tag on a block of repeated questions. Tags group questions for reporting and can be used as rows or columns in a report; they are set in code rather than on this tab. See Adding metadata to questions for how tagging works.
Jumping to the survey code
The Actions column shows Go to Line with the question's line number. Click the line number to open the Survey Code tab with the editor positioned at that question — the fastest route from "this question looks wrong in the list" to fixing it in code.
Derived questions live here too
The Questions tab is also where derived questions are created and managed. Click + DERIVED QUESTION above the table to combine two or more existing questions into a new reporting question — "Age × Gender", for example. Derived questions appear at the top of the table with a Derived chip, and their Actions column has edit and delete icons instead of a code line, since they don't exist in the survey code. See Derived Questions for the full walkthrough.
When to use this tab
Reach for the Questions tab whenever report output names the wrong thing: before your first report, spend a few minutes giving every question a clean label, and your crosstabs and exports will be readable without a decoder ring. Then use the search bar plus Go to Line as your index into the survey code whenever a specific question needs attention.