> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/optimize-your-setup/server-container-monitoring.md).

# Server container monitoring

What you see on a container's Monitoring page: whether your tracking works, from the visit on your website to what your platforms accepted.

### Where to find it

Open your container and click **Monitoring** in the sidebar. At the top you see when the latest check ran and whether there are open alerts. Click **Refresh** to run the check again.

The page has five tabs: **Overview**, **Proactive monitoring**, **Raw requests**, **History** and **Sent alerts**.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2F6zugGFMnTh9OfVC3lVCV%2Fmonitoring-overview-performance-en.webp?alt=media" alt="The Overview tab of the Monitoring page"><figcaption><p>The Overview tab of the Monitoring page.</p></figcaption></figure>

{% hint style="info" %}
Monitoring shows whether your tracking works. What AdPage sends to your platforms on top of your server container is set up under **Data boosts**.
{% endhint %}

### Overview

The Overview follows your data in five steps. Each step shows its status at a glance, and the blocks below explain each step in more detail.

| Step                 | What it shows                                                                                                     |
| -------------------- | ----------------------------------------------------------------------------------------------------------------- |
| **Visit**            | Whether visits reach your server container: the CNAME record and the tagging pixel.                               |
| **Incoming**         | The events from your website, last 7 days.                                                                        |
| **Webhooks**         | Whether webhooks from your commerce platform come in, or *Not in use*.                                            |
| **Server container** | What your platforms accepted, last 7 days, with the acceptance percentage per platform.                           |
| **Boosts**           | How many of your boosts you use, for example *You use 3 of the 8 boosts*. **Go to Data boosts** opens the boosts. |

Under **Open alerts** you see what the latest check rejected. These are the issues we send alerts about. When everything is fine, it says *Nothing: everything from the latest check is fine.*

The column on the right links to the other tabs: **Go to Proactive monitoring ›**, **View history ›** and **View sent alerts ›**.

### Proactive monitoring

Here you choose which alerts you get by email: the **Purchase alert**, **Duplicate alert**, **Consent alert** and **Platform alert**, and who receives them. Proactive monitoring is part of the Performance package. See [Pro-active monitoring](https://docs.adpage.io/optimize-your-setup/pro-active-monitoring.md).

### Raw requests

A list of what your server container sent to your platforms in the last 7 days, newest first. Click a row to see the request and the response.

<figure><img src="https://1274044937-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FA65KwL1NwewlJbtCXsXd%2Fuploads%2FkRT9N3AIT32ny8zK5NgG%2Fmonitoring-raw-requests-en.webp?alt=media" alt="The Raw requests tab with the Platform filter, Problems only and the list of requests"><figcaption><p>The Raw requests tab on the Monitoring page.</p></figcaption></figure>

* Use the **Platform** filter to show one platform, such as Google Analytics 4, Google Ads, Meta, TikTok, Pinterest, Snapchat, Microsoft Ads or LinkedIn.
* Tick **Problems only** to show only requests a platform did not accept.

There is no export. Missing a filter, column or export? Click **Request a feature ›** at the bottom of the tab.

{% hint style="info" %}
Raw requests are individual requests, not a total per day or week. For your request usage, see [Monthly Usage](https://docs.adpage.io/accountmanagement/container-management/monthly-usage).
{% endhint %}

### History

**Data quality per day** shows how your tracking scored on each day, together with the checks that were saved. Use it to see when a problem started, or whether a fix worked.

### Sent alerts

Every alert for this container, with whether it arrived and was read. Filter on channel (email or Slack), status and level. Sent alerts appear here automatically.


---

# 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.adpage.io/optimize-your-setup/server-container-monitoring.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.
