> For the complete documentation index, see [llms.txt](https://docs.exads.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.exads.com/ad-server/saas-campaigns-tab/saas-compliance.md).

# Campaign Compliance

This page describes how the Campaign Compliance feature works when enabled for your Ad Server.

{% hint style="info" %}
Campaign Compliance is only available to EXADS clients with Compliance enabled at the Ad Server level. Once the Compliance feature is enabled, a list of pre-defined rejection reasons should also be set up.
{% endhint %}

## Compliance Functionality

The goal of Compliance is to police your Ad Server and ensure that Advertisers and Publishers are compliant with the Ad Server guidelines to protect the end user experience and the Ad Server itself. Only users with the role of **Super Administrator**, **Administrator**, or **Compliance** have the permission to do this.

### Compliance for Advertisers' Campaigns

![compliance status](https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FRSrKVFEgRk7NJ8f1B84F%2Fsaas-compliance-status.png?alt=media\&token=f0f18930-90a6-440a-b2aa-3481c9b42455)

For Campaign Compliance, campaigns should be checked to ensure that they can safely run on your Ad Server.\
To verify campaigns created by the Advertisers, the Compliance user will need to go to the Campaigns page and look for campaigns for which they would like to audit and change the **Compliance Status**. This change can be done at any time by choosing a new status from the drop down, options as follows:

| Status       | Explanation                                                                        |
| ------------ | ---------------------------------------------------------------------------------- |
| **Approved** | The campaign is compliant and it can run.                                          |
| **Pending**  | Default status\*. The campaign requires Compliance audit.                          |
| **Rejected** | The campaign has been rejected\*\* - check **Rejection Reason** to understand why. |

\*All newly created campaigns will appear as “Pending” until changed to "Approved" or "Rejected".\
Internal campaigns will be automatically approved.\
Copied campaigns will have the same status as the original campaign.\
If a user updates a previously approved or rejected campaign, the status of this campaign will change to "Pending".

\*\*When a campaign is rejected, you have to select the reason for the rejection and this information will be then shown in the “Rejection Reason” column.

{% hint style="success" %}
**Tip**: To easily find the campaigns that need to be audited, use the **+ADD FILTER**, filter by **Compliance Status** as **Pending** and click **APPLY**.
{% endhint %}

{% hint style="info" %}
To check and analyze the campaign, you will need to **Jump To** the campaign. When you click the **Jump To** button, you will be redirected to the advertiser's campaign page.
{% endhint %}

![compliance jump to](https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FdqzyQXO9fv7cmYTpU3Af%2Fsaas-jump-to-due-to-compliance.png?alt=media\&token=aa320286-b3a0-4717-8f33-525c24a0131d)


---

# 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.exads.com/ad-server/saas-campaigns-tab/saas-compliance.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.
