> For the complete documentation index, see [llms.txt](https://support.gamoshi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.gamoshi.com/gamoshi-wiki/general-information/capping-metrics.md).

# Capping metrics

This section provides the full list of capping metrics for advertisers and campaigns.

## Advertiser Capping

| **Advertiser Capping**      | **Description**                                                                       |
| --------------------------- | ------------------------------------------------------------------------------------- |
| Max QPS                     | The maximum QPS (=queries per second) allowed for the advertiser. 0/empty = no limit. |
| Max Impressions Daily       | The daily limit. 0/empty = no limit.                                                  |
| Max Video Impressions Daily | The daily limit. 0/empty = no limit.                                                  |
| Max Clicks Daily            | The daily limit. 0/empty = no limit.                                                  |
| Total Budget                | The total budget for all of the advertiser's campaigns. 0/empty = no limit.           |
| Daily Budget                | The daily budget for all of the advertiser's campaigns. 0/empty = no limit.           |
| Hourly Budget               | The hourly budget for all of the advertiser's campaigns. 0/empty = no limit.          |

***

## Campaign Capping

| **Campaign Capping**                   | **Description**                       |
| -------------------------------------- | ------------------------------------- |
| Max QPS                                | Maximum QPS allowed for the campaign. |
| Banner Impressions / Video Impressions | Daily campaign caps.                  |
| Clicks                                 | Daily campaign caps.                  |
| Banner Impressions / Video Impressions | Daily user frequency caps.            |

***

## Campaign Spending Mode

**Availability:** DSP accounts and PE Enterprise accounts → DSP campaigns (Internal).

In **Campaign → General tab → Budget** section, you can choose the campaign's spending mode: **Regular** (default) or **Aggressive**.

* **Regular Spending Mode:** Paces spend evenly across campaign hours, per the defined budget.
* **Aggressive Spending Mode:** Removes limits and attempts to spend the budget as quickly as possible.

**Impact on Max QPS (Capping tab):**

* **Regular Mode:** The Max QPS cap is greyed out and marked **"Managed QPS."** The system's algorithms automatically manage the campaign's QPS cap to match the required budget, calculated per hour.
* **Aggressive Mode:** The Max QPS cap becomes editable, with a default of 50 QPS (50 queries per second), letting you adjust it based on how aggressive you want to be and the volume of incoming requests for the campaign per the campaign filters.

***

## Campaign User/Device ID Frequency Capping

In addition to daily impression and click volume capping, you can add a user/device ID frequency cap to a campaign:

* **User frequency cap** – for web activity.
* **Device ID frequency cap** – for in-app activity.

You can choose the time window granularity (day, week, or month) and the number of impressions/video impressions allowed within it.

***

## Important Notes

{% stepper %}
{% step %}

### Processing time

The capping process may take a few minutes to complete across all distributed servers.
{% endstep %}

{% step %}

### Budget vs. spend rate

Setting a budget below an advertiser's or campaign's 5-minute spend rate (how much is spent in 5 minutes) may cause spending to exceed the budget. The minimum hourly budget is $2. The minimum daily budget is $10.
{% endstep %}

{% step %}

### User frequency cap (web)

Works only if the inventory sends user identifiers in the request. Applying this cap will filter out all in-app requests that don't include a user identifier. It is most effective when it relies on user IDs, which requires cookie sync, and less effective when relying on other identifiers.
{% endstep %}

{% step %}

### Device ID frequency cap (in-app)

Works only if the inventory sends the device ID in the request. Applying this cap will filter out all in-app requests that don't include a device ID.
{% endstep %}
{% endstepper %}