> 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/data-analytics/multi-surveys-analytics.md).
# Multi-Surveys Analytics
Using the analytic dashboard you can link one or multiple surveys to your dashboard using the link survey feature
Once you have a linked a survey you can either access quickly each survey question and its results using the link tree or you can add any of those questions to your current dashboard page.
If you linked multiple surveys and some of the questions of some surveys are similar you can link them all within a single graph a compare the results as stacked charts. To link the questions to a graph link all the similar questions to your graph in the graph properties and select the group similar option.
Once you have link similar questions your dashboard will render them and stack them in the chosen visualization which will allow you to compare easily the results within the same graph.
---
# 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/data-analytics/multi-surveys-analytics.md?ask=&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.
