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

# Campaign Manager

Run your own powerful programmatic ad platform.

<figure><img src="https://59878909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGoSwRYjxsR1XS6va6yLj%2Fuploads%2FoX8IC9udwT2rJfl7LjMi%2Fgraph-campaign-manager.png?alt=media&amp;token=8086c44c-351d-41d2-8d80-0244002f4948" alt=""><figcaption></figcaption></figure>

### What is Campaign Manager?

Campaign Manager is an ExoClick tool that allows Publishers to run their own programmatic ad platform, combining unique ExoClick demand with your direct and programmatic buyers. It requires no development.

### How does it work?

Publishers place a simple ad tag on their website, and Campaign Manager handles everything else from the server side. All bidders compete equally for each ad zone with a single ad call. It supports OpenRTB standard technology and custom XML integrations. Publishers can set up direct deals with customers by offering fixed traffic volumes, or allow all buyers to compete for inventory.

Campaign Manager supports integrations across Fullpage Interstitial, Email clicks, Direct links, Banner ads, Native ads, Video ads, and Popunders, with per-bidder statistics available for any time period, including requests, impressions, win ratios, and average bid CPMs. All ads are also scanned for malvertising and non-compliance.

### Who is it for?

Campaign Manager is ideal for Publishers with large free content sites, Members Area Publishers and Email List Publishers, who want to maximise revenue across multiple demand sources without building their own RTB infrastructure.

### Want to apply?

Publishers interested in Campaign Manager should fill out our [Campaign Manager application form](https://share.hsforms.com/1Ca_YIYQbQ56jDxSMOMjwJg1qozg). Then we will evaluate your eligibility.

{% hint style="info" %}
**Note:** You must have a contractual relationship with any demand partners you wish to integrate.
{% endhint %}

<figure><img src="https://59878909-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGoSwRYjxsR1XS6va6yLj%2Fuploads%2FEwhL1cAO0oRYwH5zJI6P%2FScreenshot%202026-07-31%20at%2009.39.20.png?alt=media&amp;token=c4b6feec-8905-4aa2-b24a-0146da42882e" alt=""><figcaption></figcaption></figure>


---

# 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.exoclick.com/publishers/campaign-manager.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.
