> 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/admin/saas-admin-settings-sites-and-zones.md).

# Sites & Zones

## Inactive Zone Archiving

As an **Administrator** or **Super Administrator**, you can have the Ad Server archive zones that are no longer used. Go to **Admin > Settings > Sites & Zones**, then use the **Allow Archiving of Inactive Zones** toggle under **Zone Settings**.

<figure><img src="https://2551497454-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbWd08bYtHMw1HqDKFpBf%2Fuploads%2FvDQi3BmBTo39yKHJdHrr%2Fsaas-admin-settings-sites-and-zones-on.png?alt=media&amp;token=ab1288ad-2f23-4c29-8ccc-91999dec23e4" alt=""><figcaption></figcaption></figure>

When the toggle is on, set the **Inactive Zone Archival Period** in days. A zone is inactive when it is older than that period and has had no ad requests and no edits for the whole period.

Only zones that belong to active accounts and approved sites are checked. For Multi-Format zones, ad requests served through their format zones count as activity.

Changes apply from the next scheduled run.

**Default settings:** On, 180 days.

## How It Works

1. **Scheduled for archiving.** Every Monday at 06:00 UTC, each inactive zone changes to **Pending Archiving**. The Publisher gets one email listing all their zones that are affected, in the format *Site name - Zone name {Zone ID}*.
2. **15-day notice.** The zone keeps serving as normal. If the zone is edited during this time, archiving is canceled and the zone goes back to **Active** straight away. If it receives ad requests, it stays **Pending Archiving** until the archiving run, which then cancels archiving and sets it back to **Active**. No email is sent when archiving is canceled.
3. **Archived.** On the first Friday after the 15-day notice ends, at 22:00 UTC, zones that are still inactive are archived, and the Publisher gets a second email listing them.

Archived zones can be restored from the **Sites & Zones** tab, like any other archived zone.

{% hint style="info" %}
When a zone is archived, its blocked products, marketing tags and compliance rules are removed. Restoring the zone doesn't bring them back.
{% endhint %}


---

# 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/admin/saas-admin-settings-sites-and-zones.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.
