> For the complete documentation index, see [llms.txt](https://docs.talentmap.com/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talentmap.com/knowledge-base/survey-design-and-deployment/survey-logic-and-display-conditions-quick-start/branching-based-on-demographics.md). # Branching Based on Demographics Branching lets you show or hide a survey page depending on a participant's demographic data. Use it to keep surveys short and relevant by only asking each participant the questions that apply to them. *** ### When to use branching Use branching when: * A page only applies to a subset of participants (for example, a Unionized supervision page that only Union members should see). * You want to ask follow-up questions based on an earlier answer. * You want to route participants to different question sets based on demographic data uploaded with your participant file. You can branch on: * **Demographic data** uploaded with your participant file (department, location, union status, tenure, and any other demographic field). * **Earlier survey responses** on previous pages or questions in the same survey. *** ### How branching works A page with branching applied is only shown to participants who match the condition you set. Participants who do not match the condition skip the page entirely. The page jumps over to the next visible page without showing the branched page. Participants are not told that a page was skipped. *** ### Set up branching on a page 1. Navigate to **Surveys** and open the survey you want to edit. 2. Click **Design Survey** in the left navigation. 3. Click the page you want to branch. **Note: You can branch pages or questions.** 4. In the right-hand panel, open the **Conditions** tab. 5. Click the pencil icon next to **Make the page visible if**.
6. In the **Make the page visible if** modal, choose a demographic field or an earlier survey question as the **If** value. 7. Choose an operator (such as **Equals**, **Does not equal**, or **Contains**). 8. Choose or enter the value that should make the page visible. 9. To add another condition, click **Add Condition**. Conditions combine with AND logic by default. 10. Click **Apply**.
When a condition is set, the **Conditions** panel shows "A condition has been applied" and a small branching icon appears on the page in the Design Survey view.
To remove branching, click **Clear** in the **Conditions** panel. *** ### How branching affects your data and reports Branching changes which questions a participant sees, which in turn affects the data you collect and report on. Plan for these effects when you design the survey. {% hint style="info" %} **Read this section before launching a branched survey.** The behavior described here is by design and applies to all branched pages. {% endhint %} #### Excel exports In raw Excel exports, questions on a branched page appear as blank or N/A for participants who did not see that page. Filter the export by the same demographic field if you want to analyze only the participants who saw the page. #### Reporting and dashboards Reports and dashboards include all participants by default. To analyze a branched page accurately, apply the same filter you used in the branching condition (for example, filter the report on Union status = Union when reviewing a page that was only shown to Union members). #### Key driver analysis Key driver analysis automatically respects branching. The analysis only includes participants who answered both the driver questions and the outcome questions. #### Comment analysis Comment themes and sentiment analysis respect the filters you apply. If you filter a comment report on a demographic value, comments from participants who saw a branched page tied to that value are included or excluded based on the filter. #### Visibility to participants Participants do not see any indication that a page was branched. They see only the pages that apply to them. {% hint style="warning" %} **Branching is not shown in client-facing reports.** Reviewers cannot tell from a report whether a page was branched or not. If you want to highlight this in a client report, note it in the report commentary. {% endhint %} *** ### Tips for designing branched surveys * **Test the branching before launch.** Use the **Preview** tab in the survey designer to walk through different demographic combinations. If your survey uses participant PINs, you can also use the test PIN listed on the **General** page to confirm the flow. * **Keep the rest of the survey neutral.** A branched page might be skipped, but introductory pages, instructions, and the closing page are shown to everyone. * **Document your branching logic.** Keep a note of which pages are branched and the conditions used. This makes it easier to interpret reports later. * **Avoid branching on optional demographic fields.** If a participant has no value for the demographic field you are branching on, the page will not be shown to them. *** ### FAQ #### Can I branch a survey based on a question instead of a demographic? Yes. The **If** field in the branching modal lets you select any earlier question in the survey, in addition to demographic fields. The question must appear on a page before the branched page. #### Can I apply more than one condition to a single page? Yes. Click **Add Condition** in the branching modal to combine multiple conditions. Conditions combine with AND logic. #### What happens if a participant has no value for the demographic I am branching on? The branched page will not be shown to them. If the page is important, consider branching on a different field or making the field required in your participant upload. #### Will branched participants show up in my report response counts? Yes. The total response count for the survey includes everyone who started the survey, regardless of which pages they saw. The response count for a specific question only includes participants who saw and answered that question. #### Can I see which participants were branched? Not directly in reports. To identify which participants saw a branched page, filter your raw Excel export by the demographic field used in the branching condition. #### Can I branch on multiple demographic fields at once? Yes. Add a separate condition for each field in the **Make the page visible if** modal. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.talentmap.com/knowledge-base/survey-design-and-deployment/survey-logic-and-display-conditions-quick-start/branching-based-on-demographics.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.