> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/form-designer/pages/branching.md).

# Page Branching

## 🌲What is page branching ?

The page branching features let you define [conditions](/form-management/form-designer/condition-rules.md) to which page the [next button](/form-management/form-designer/footer-manager.md) will lead the the respondent based on his answers to the survey, you may also conditionally end the survey based on the respondent answers.

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBwGaq7XZHO5ZXCNFol%2F-MBwHeY21jtL-yaLDRit%2Fcaptured%20\(28\).gif?alt=media\&token=73bb0680-678e-4489-bacf-c74b939ab3cc)

{% hint style="info" %}
Page branching is only available on surveys with multiple pages.
{% endhint %}

## ➕ Adding a page branching

Branching can be added from the [page properties](/form-management/form-designer/pages.md) page or in a more visual way using the [flow logic graphs](/form-management/flow-logic-graph.md).

## 🔅 Branching properties

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBwJqvTQPHGEGRyQ2jn%2F-MBwLHhDCtUvvwr8F1__%2Fimage.png?alt=media\&token=022ba968-0609-46d5-9f4d-4a612d1f129e)

1. We can update the target page that should be shown if [condition rule](/form-management/form-designer/condition-rules.md) is met.
2. Add an additional [condition rules](/form-management/form-designer/condition-rules.md) group. 

{% hint style="info" %}
In the example above the survey would be ended once the respondent answered 1 to the Would you recommend our company? question and clicked on the next page button. 
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ngsurvey.com/form-management/form-designer/pages/branching.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.