> For the complete documentation index, see [llms.txt](https://fair-indonesia.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fair-indonesia.gitbook.io/docs/features/campaign-management.md).

# Campaign Management

Track and manage all your active influencer campaigns from a single dashboard — deliverables, performance, and status in real time.

***

## Overview

Campaign Management is where your shortlisted creators become an active campaign. You set the brief, add creators, define deliverables, and then Fair tracks everything as it happens — no more chasing creators via DM or updating spreadsheets manually.

***

## Creating a campaign

1. Go to **Campaigns → New Campaign**
2. Fill in the campaign details:

| Field            | Description                                             |
| ---------------- | ------------------------------------------------------- |
| Campaign name    | Internal reference name                                 |
| Brand            | Which brand this campaign is for (useful for agencies)  |
| Start / end date | Campaign timeline                                       |
| Budget           | Total campaign budget (optional)                        |
| Platforms        | Which platforms deliverables will be on                 |
| Brief            | Campaign objectives, content guidelines, and dos/don'ts |

3. Add creators from your saved lists or search directly
4. Set deliverables per creator (e.g. 2 Instagram Reels + 3 Stories)
5. Click **Launch Campaign**

***

## Campaign dashboard

Each active campaign has its own dashboard showing:

* **Status overview** — how many deliverables are pending, in review, live, and completed
* **Performance metrics** — total reach, impressions, engagement, and CPV updated in real time
* **Creator status** — individual progress per creator in the campaign
* **Timeline** — upcoming deliverable deadlines

***

## Deliverable tracking

For each creator in a campaign, you can track:

* Content submission (creator submits content for review)
* Approval status (approved / revision requested / rejected)
* Go-live date
* Post-live performance (views, likes, comments, shares)

{% hint style="info" %}
Fair pulls live performance data directly from the platform APIs after content goes live. You don't need to manually check each post.
{% endhint %}

***

## Reporting

Once a campaign ends (or at any point during), you can generate a campaign report that includes:

* Summary of all deliverables
* Total reach and engagement
* Cost per view and cost per engagement
* Creator-level performance breakdown
* Comparison against campaign benchmarks

Reports can be exported as PDF or CSV.

***

## Campaign limits by plan

| Plan           | Active campaigns                 |
| -------------- | -------------------------------- |
| Self-Service   | 3                                |
| Pro            | Unlimited                        |
| Growth Partner | Unlimited (managed by Fair team) |

***

## Related

* [Brand Analytics](/docs/features/brand-analytics.md) — cross-campaign performance overview
* [Running Your First Campaign](/docs/guides/running-your-first-campaign.md) — step-by-step guide


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://fair-indonesia.gitbook.io/docs/features/campaign-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.