> 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/accountmanagement/container-management/monthly-usage.md).

# Monthly Usage

How your monthly usage is calculated, where to view your usage, and how to investigate a sudden spike.

### How are requests calculated?

With server-side tagging, a single visit to your website generates several types of requests. Not all of them are billed: whether a request counts toward your monthly usage depends on its type.

<table><thead><tr><th width="601">Request type</th><th>Billed</th></tr></thead><tbody><tr><td>/g/collect requests sent to your server container (<code>page_view</code>, <code>click</code>, <code>purchase</code>, etc.)</td><td>Yes</td></tr><tr><td>Script delivery (<code>gtm.js</code>, <code>user-data-minified.js</code>, etc.)</td><td>Yes</td></tr><tr><td>Incoming webhooks from your commerce platform (Shopify, WooCommerce, Magento, etc.)</td><td>Yes</td></tr><tr><td>AdPage's Data Assistant monitoring (<code>/_tools/monitoring</code>)</td><td>No</td></tr><tr><td>Requests from your server container to GA4, Meta, Google Ads, etc.</td><td>No</td></tr></tbody></table>

**Priced by volume. Not by seat.** Your bill follows your request count. Send your data to as many platforms as you like, at no extra cost.

#### Example

A visit to a product page may generate the following requests: 1 script load, 1 `page_view` event, 1 `view_item` event. This increments the usage by 3 requests.

These events are then added to the AdPage Data Assistant and sent to your server container, which forwards it to GA4, Meta, and Google Ads. None of those requests are added to your usage.

### How to view your monthly usage

Usage tends to grow gradually as your traffic increases and event types are added, so a trend towards an overrun is usually visible well before it becomes a problem. There are two places to keep an eye on it.

#### The Plan block on the Overview

Open your container. The **Plan** block on the **Overview** shows your plan and how many requests you have used this month. Click **Usage per month** to open the full usage page, or **Manage** to change your plan. On the Free plan this button is called **Upgrade**.

<figure><img src="https://1908438300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvuyv7mcuSvQb9yTkzfeA%2Fuploads%2FQIEyo11SzoqpIkDFrDYv%2Fdashboard-plan-block-performance-en.webp?alt=media" alt="The Plan block on the container Overview with the requests used this month"><figcaption><p>The Plan block on the container Overview.</p></figcaption></figure>

#### The Monthly usage page

Click **Plan and usage** in the sidebar, under **Container**. This opens the **Monthly usage** page with three blocks:

* **This month:** your requests so far, your monthly limit, the percentage of the limit you have used, and your strikes.
* **By month:** the last 12 months, with the month, a usage bar (the line marks your limit), the requests and the status of each month.
* **Where do your requests come from?** A breakdown of the usage of the selected month. See below.

Use **Subscription ›** at the top right to view or change your plan.

<figure><img src="https://1908438300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvuyv7mcuSvQb9yTkzfeA%2Fuploads%2FaYd7dlP5kO0l7gvFaI8Z%2Fmonthly-usage-en.webp?alt=media" alt="The Monthly usage page with the This month block and the usage of the last 12 months"><figcaption><p>The Monthly usage page.</p></figcaption></figure>

#### Where do your requests come from?

Below the **By month** table, a breakdown card shows how the usage of the selected month is built up. Click a month row in the table to see the breakdown of another month, and use **Refresh** to recalculate it. With a lot of traffic, calculating can take a moment.

**How your usage is built up** shows three rows:

* **Events via the AdPage data tag:** events your website sends through the AdPage data tag. They are broken down per event below the rows, with a view per day.
* **GA4 hits:** Google Analytics hits on your server container, broken down per event, such as `page_view`, `user_engagement` and `scroll`.
* **Other requests on your server container:** requests that are not logged per event.

Together, these rows add up to the total counted this month.

{% hint style="info" %}
If your container does not send events through the AdPage data tag, the card shows no breakdown per event or per day for those events.
{% endhint %}

**Where do they go?** shows what your server container forwards to your platforms, for example Meta and Google Analytics 4. These requests do not count toward your usage: one incoming event is sent to every connected platform, so this number is higher than your usage.

The breakdown is based on the logged requests of the selected month. Dates are in UTC.

<figure><img src="https://1908438300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvuyv7mcuSvQb9yTkzfeA%2Fuploads%2FM1W8ref30IQUzF0Ml6GC%2Fusage-breakdown-en.webp?alt=media" alt="The breakdown card with How your usage is built up, GA4 hits per event and Where do they go?"><figcaption><p>The breakdown card on the Monthly usage page.</p></figcaption></figure>

{% hint style="info" %}
Usage is shown per month. A breakdown per day is only available in the breakdown card, for events sent through the AdPage data tag. The Monthly usage page has no date range or export.
{% endhint %}

#### Looking at a shorter period

For events sent through the AdPage data tag, the breakdown card above shows a breakdown per day. For all other requests, or to look at a shorter period than a month, use one of these:

* **Data boosts › Server container** shows the requests your server container sent per destination, for **Today** or the last **7 days**, with the columns Destination, Requests, OK, 4xx, 5xx, Purchases, Unique orders and Origin.
* **Monitoring › Raw requests** lists each request your server container sent to your platforms in the last 7 days. Filter on a platform, or tick **Problems only**. There is no export. See [The Monitoring page](https://docs.adpage.io/optimize-your-setup/the-monitoring-page).
* **Daily numbers:** ask Brent, for example "How many incoming requests did my container receive per day over the last 30 days?" Or query the `incoming_requests` and `outgoing_requests` tables of [AdPage Tracking](https://docs.adpage.io/data-and-insights/marketing-integrations/adpage-tracking) yourself.

<figure><img src="https://1908438300-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fvuyv7mcuSvQb9yTkzfeA%2Fuploads%2F7wiOtOULeQuetet51W8s%2Fdata-streams-server-container-7days-en.webp?alt=media" alt="Data boosts › Server container with the 7 days view selected"><figcaption><p>Data boosts › Server container, with the 7 days view selected.</p></figcaption></figure>

### What happens if you exceed your limit

Exceeding the monthly allowance of your plan does not immediately result in your server container being stopped. Instead, a strike is given for that month. Only after a certain amount of strikes (paid: 3, free: 1) is the server container stopped. You can see your strikes in the **This month** block of the Monthly usage page.

{% hint style="warning" %}
When your container is blocked, incoming requests receive a `429 Too Many Requests` status. This means the data is no longer processed and no longer forwarded to your connected platforms. Any conversions and events that occur during that period are lost.
{% endhint %}

### Investigating a sudden spike in usage

A spike in monthly usage without a matching increase in GA4 events or visitors may be caused by the following:

1. **Session comparison:** Check what the normal amount of sessions are in GA4 per month. Multiply this by 25. If that amount is what you see per month in usage, that should be normal. If it's substantially more, it's a reason to dive deeper.
2. **Bot/scraper traffic:** AdPage increments the monthly usage for every incoming event, before it reaches your server container and GA4. In the reporting of GA4, the events of some visitors may be filtered out (under the suspicion of being a bot or scraper), causing a discrepancy.
3. **Requests per visitor:** compare AdPage's requests per day against GA4's events per day for the same period. Apart from the breakdown per day for events sent through the AdPage data tag, the app does not show requests per day, so ask Brent for the daily numbers or query the `incoming_requests` table of [AdPage Tracking](https://docs.adpage.io/data-and-insights/marketing-integrations/adpage-tracking). It may be the case that the number of requests per visitor has increased, due to: script-load frequency (caching), cookie-recovery calls, or newly added tags.
4. **Check what changed around the start of the spike.** A new script version, a Cookie Herstel/consent setting change, or a newly published server container version can all change the request ratio overnight.
5. **Ask Brent** which GA4 events are measured a lot in the `ga4_event_logs` compared to other events.

Believe a strike was caused by something outside of your control? Ask your AdPage account manager for an in-depth analysis of your requests.


---

# 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/accountmanagement/container-management/monthly-usage.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.
