> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/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/references/references-classic/search-and-information-display-classic/campaign-display-compatibility-in-finder-classic.md).

# Campaign display compatibility in Finder (classic)

### Overview <a href="#campaigndisplaycompatibilityinfinder-classic-overview" id="campaigndisplaycompatibilityinfinder-classic-overview"></a>

This article explores the Collector’s different capabilities when displaying campaigns. These capabilities differ depending on the platform (Windows or Mac) as well as the version of the Collector.

Based on the features used when creating a campaign, Finder will dynamically display the version requirements for Collector at the bottom of the screen.

<figure><img src="https://268444917-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxJSUDk9NTtCHYPG5EWs3%2Fuploads%2Fgit-blob-c3a3c58ad8c076ae7a50f0fcd3b85781eee403d2%2F620px-nxfinder-1605445100.png?alt=media" alt=""><figcaption></figcaption></figure>

### Feature compatibility <a href="#campaigndisplaycompatibilityinfinder-classic-featurecompatibility" id="campaigndisplaycompatibilityinfinder-classic-featurecompatibility"></a>

Both Windows and Mac Collector support all the main campaign features:

* One-off, recurring and continuous campaigns
* Single answer, multiple answer and opinion scale questions
* Workflows
* Links and placeholders in campaign descriptions
* Internationalization and translations
  * The following languages are supported in campaign notifications starting from V6.22 only: Dutch, Norwegian, Danish, Swedish, Finnish, Afrikaans, Hindi, Japanese, Korean and Vietnamese​. [Click here for the full list of supported languages](/user-guide/campaigns/campaigns-in-finder-classic/translating-a-campaign-with-finder-classic.md#translatingacampaignwithfinder-classic-languageofbuttonsincampaignnotifications).

In addition, the Windows Collector supports the [branding of campaigns](/user-guide/campaigns/managing-campaigns/campaigns-branding.md). Because the Mac Collector uses the standard notification mechanism of macOS to display campaigns, the aesthetic of a campaign is fixed. This means that although the Mac Collector is still compatible with all campaigns, it will ignore any specified brand logo or company colors that may have been applied

Starting from V6.21, the following feature is available in both Windows and Mac Collectors:

* Skip campaign notification

Configuring the notification of all campaigns is still required for backwards compatibility, as versions of Collectors previous to V6.21 ignore the setting to skip the notification.

### Protocol compatibility <a href="#campaigndisplaycompatibilityinfinder-classic-protocolcompatibility" id="campaigndisplaycompatibilityinfinder-classic-protocolcompatibility"></a>

From V6.12, Nexthink Engage introduced a more efficient communication protocol through the TCP channel. End-user feedback can now be retrieved between the Engine appliances and the Collector. Hence, Collectors versions before V6.12 cannot display campaigns created with Nexthink V6.12 or later.

***

RELATED TASKS

* [Creating a campaign](/user-guide/campaigns/campaigns-in-finder-classic/creating-a-campaign-with-finder-classic.md)
* [Branding of campaigns](/user-guide/campaigns/managing-campaigns/campaigns-branding.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/references/references-classic/search-and-information-display-classic/campaign-display-compatibility-in-finder-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.