> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/platform/references/references-classic/glossary-classic/campaign-classic.md).

# Campaign (classic)

A *campaign* is a set of questions addressed to a group of users with the goal of getting their opinion on a particular matter. Usually, the subject matter of a campaign relates to the users' perception of the IT services and equipment that your organization provides to them.

Create your campaigns in the Finder and assign different target audiences for each campaign by using investigations on users. The targeted end-users receive notifications in their Collector equipped devices for answering the questions of your campaigns.

Track the results of your campaigns using investigations and metrics, as well as dashboards to follow their evolution.

***

RELATED TASK

* [Creating a campaign](/platform/user-guide/campaigns/campaigns-in-finder-classic/creating-a-campaign-with-finder-classic.md)


---

# 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.nexthink.com/platform/references/references-classic/glossary-classic/campaign-classic.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.