> 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/campaigns/campaign/campaign-results.md).

# Campaign Results

The campaign results page allows you to manage and see the current respondents who answered or not your survey

![](https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-M8fLhS0bmfBRyq0HdUm%2F-MBOGQfAHQvcuVyvDwrk%2F-MBOOp6o96lvS8bttfYV%2Fimage.png?alt=media\&token=b2435fa5-18e7-4040-9434-eceef36da9bf)

1. **Completed** are the respondent who answered your survey. You can click on any of the email entry to display its corresponding survey answers.
2. **Opened** are the respondents who clicked on the invitation link and opened the survey in the browser but did not yet submit any answers.
3. **Read** are the respondents who read the invitation message but didn't click on the invitation link.
4. **Pending** count are the respondents who did not answer your survey yet.

The **Export all** button allows you to export a CSV formatted file with all the recipients of the tab you are in. It will export all recipients, their unique code and also the unique link to for each respondent to take the survey 

{% hint style="warning" %}
Make sure that you have properly setup your [host domain](/installation-setup/system-settings/general.md#hosting-domain) in the [system settings](/installation-setup/system-settings/general.md#hosting-domain) to generate the unique respondent link using the export all function. 
{% 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/campaigns/campaign/campaign-results.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.