Usage, limits and billing¶
Server Tag Manager consumption is measured in requests. Every request that reaches a container counts as one — with no exception by method or by path.
AdPulse dashboard in Portuguese
The AdPulse dashboard interface is only available in Portuguese. The labels quoted in the steps below are exactly what you see in the product.
How to count¶
A request is any HTTP call your container receives:
- Loading the GTM script.
- Firing an event.
- Calling a tag — Analytics, Ads, conversion pixel.
- Any other path served by the container.
Requests the browser never sends do not reach the server and so are not counted. That is exactly why a first-party domain and the WordPress plugin matter: more requests arriving means more data and more attribution.
Where to check¶
On the container page you find the usage bar and the chart; on the container list, four cards summarize the whole organization:
| Card | What it shows |
|---|---|
| Requisições totais | Sum of the current month, across all containers. |
| Contêineres ativos | How many containers are Ativo, out of a total. |
| Uso médio | Average consumption across the containers. |
| Limite de requisições | Combined monthly capacity. |
On each container's usage bar, the panel shows the format X requests and Y% of Z, where Z is the plan limit.
Consumption ranges¶
| Range | Dashboard warning |
|---|---|
| Up to 50% | No warning. |
| 50% to 70% | No warning, only the bar changes color. |
| 70% to 90% | Uso elevado — "Você já usou X% do limite mensal de requisições." |
| 90% or more | Uso crítico — "Você já usou X% do limite mensal de requisições. Considere fazer upgrade do seu plano." |
When the numbers update¶
- Every 5 minutes — the counters are synced from the tag server to the dashboard. A recent spike can take a few minutes to show up.
- On the first day of each month — the monthly counter resets.
The counter can lag, but it never understates
A spike from right now only shows up at the next sync. The value shown, on the other hand, is always the real accumulated total for the month — it is not an estimate.
What happens when you reach the limit¶
When you reach the plan limit, the container is put into Bloqueado status and starts refusing requests with error 403. Traffic stops — there is no silent overage.
To get it working again:
- Upgrade the plan, or
- Talk to AdPulse support to review the limit.
A new container starts at 10,000
Newly created containers get an initial limit of 10,000 requests per month. The final limit is the one on your plan.
Other statuses that also stop traffic¶
Besides Bloqueado, the Suspenso and Erro statuses also block requests. See How to create a container for what each one means.