> For the complete documentation index, see [llms.txt](https://help.citrusad.com/retail-media-interface/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.citrusad.com/retail-media-interface/campaign-management/campaign-statuses.md).

# Campaign statuses

Checking the status of your campaigns can be done on the campaign manager tab. It's a permanent column on the right of the table.

<figure><img src="https://19206235-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FmxYbXHcdDvQ7toxAu8ql%2Fuploads%2FbWGtKjPL0IISZiJTx2p4%2FCleanShot%202025-12-17%20at%2015.34.16.png?alt=media&amp;token=3077303e-590f-4149-9ecc-acb6212220fd" alt=""><figcaption></figcaption></figure>

## Understanding campaign statuses in the new platform

Campaign status' have been improved in the New UI to be clearer and more representative of their state. As such, they are a combination of active and approval (valid) state.&#x20;

The combined campaign status is calculated by evaluating the campaign’s **active** **state**, **approval status**, and (where applicable) its **schedule**. The logic is applied in the order below.

### 1. Campaign State

The campaign state is always evaluated first.

* **Draft** → Status is **Draft**
* **Archived** → Status is **Archived**
* **Paused** → Status is **Paused**
* **Active** → Continue to approval checks

### 2. Approval Status (Active campaigns only)

For campaigns in an **Active** state, the approval status determines the next outcome.

* **Pending** → Status is **In Review**
* **Rejected** → Status is **Changes Required**
* **Approved** → Continue to schedule checks

### 3. Campaign Timing (Active and Approved only)

Timing rules are only applied to campaigns that are both **Active** and **Approved**.

1. **Has the campaign ended?**
   * Yes → Status is **Complete**
2. **Does the campaign start in the future?**
   * Yes → Status is **Scheduled**
3. **Otherwise**
   * Status is **Active**

***

A table version is below explaining each status and the conditions:

<table><thead><tr><th>Status</th><th width="176.4166259765625">Active State</th><th>Approval (Valid) State</th><th>Active period</th></tr></thead><tbody><tr><td><strong>Complete</strong></td><td>Active</td><td>Approved</td><td>The campaign has ended</td></tr><tr><td><strong>Scheduled</strong></td><td>Active</td><td>Approved</td><td>The campaign's active period is in the future</td></tr><tr><td><strong>Active</strong></td><td>Active</td><td>Approved</td><td>The campaign is live now (either in active period, or has no active period set).</td></tr><tr><td><strong>In review</strong></td><td>Active</td><td>Pending</td><td>Any</td></tr><tr><td><strong>Changes required</strong> </td><td>Active</td><td>Rejected</td><td>Any</td></tr><tr><td><strong>Draft</strong></td><td>Draft</td><td>N/A</td><td>Any</td></tr><tr><td><strong>Archived</strong></td><td>Archived</td><td>Any</td><td>Any</td></tr><tr><td><strong>Paused</strong></td><td>Paused</td><td>Any</td><td>Any</td></tr></tbody></table>

```mermaid
flowchart LR
    A[Campaign Status Check] --> B{Campaign state}
    B -->|Draft| D[DRAFT]
    B -->|Archived| E[ARCHIVED]
    B -->|Paused| F[PAUSED]
    B -->|Unknown| G[UNSPECIFIED]
    B -->|Active| H{Approval status}
    H -->|Pending| I[IN REVIEW]
    H -->|Rejected| J[CHANGES REQUIRED]
    H -->|Unknown| G
    H -->|Approved| K{Has campaign ended?}
    K -->|Yes| L[COMPLETE]
    K -->|No| M{Starts in the future?}
    M -->|Yes| N[SCHEDULED]
    M -->|No| O[ACTIVE]
```


---

# 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://help.citrusad.com/retail-media-interface/campaign-management/campaign-statuses.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.