Campaign Delivery Settings

Timezone Notice: All daily limits are calculated based on the EST (GMT-5) timezone.

QPS (Queries Per Second) and Automatic Caps

The QPS limit controls the number of ad requests sent to a campaign per second.

Whenever you set a QPS value, the system automatically calculates and applies both the Hourly and Daily Ad Request Caps. This ensures your campaigns are always protected from oversupply.

Example:
If QPS = 1,000
Hourly Cap = 3,600,000 requests
Daily Cap = 86,400,000 requests

These caps are recalculated automatically each time you update your QPS. While they are not visible in the UI yet, they are applied in the background to safeguard traffic flow and keep campaign delivery balanced.

IMPORTANT: Aligning QPS and Daily/Hourly Limits

If you use both QPS and Daily or Hourly limits, please make sure they are aligned. If your Daily/Hourly cap is higher than the cap calculated from QPS, the system will apply both limits, and filtering will start once either one is reached.

Example:
If QPS = 100
Hourly Cap = 360,000 requests
Daily Cap = 8,640,000 requests

But if your Hourly Limit = 500,000 ad requests, the system will still enforce the backend Hourly Cap of 360,000 requests first.

Daily Revenue Cap

The Daily Revenue Cap allows you to define the maximum revenue that a particular demand campaign can generate within a 24-hour period.

Volume Limits

You can set limits for the following metrics:

• Ad Requests
• Ad Opportunities
• Impressions
• Revenue

Each of these can be capped on:

• An hourly basis
• A daily basis (defined as a rolling 24-hour period)

Frequency Cap

The Frequency Cap allows you to limit how many times a user can be exposed to a specific campaign over a defined period, helping to prevent ad fatigue and improve user experience.

The configuration options include:

• By – defines how the user is identified for frequency control:

  • IDFA – limits based on the Identifier for Advertisers (typically used on iOS devices).

  • IP – limits based on the user’s IP address.

  • IDFA & IP – both conditions must be met; frequency will be capped only if both IDFA and IP match.

• Impressions – the number of impressions allowed per user within the selected time frame.
  For example, setting this to 1,000 means each user (based on the chosen identifier) can receive up to 1,000 impressions.

• Per – defines how many impressions are allowed per unit of time.

• Time period – the duration over which the cap applies:
  Options include MINUTE, HOUR, DAY, and WEEK.

You can configure multiple frequency caps for more granular control. For instance, "1 impression per hour" combined with "3 per day".