QPS represents the number of queries processed by the system per second.
Note: QPS is calculated based on inbound and outbound ad requests - not ad calls.
How QPS is calculated
QPS = (inbound ad requests + outbound ad requests) per day
/ 24 hours
/ 60 minutes
/ 60 seconds
If you calculate QPS for a week, divide the total number of queries by 7 days first.
Always use data from a full day to avoid distorted results.
How QPS impacts revenue
QPS is a limited resource. Efficient allocation can directly increase profitability.
Recommendations:
Analyze demand partners
Identify which advertisers or campaigns receive the largest share of requests.
Compare the percentage of revenue they generate.
Limit or disable low-performing demand
If a partner consumes significant QPS but generates low revenue, consider limiting or disabling it.
This frees up QPS for more profitable demand.
Managing QPS
You can apply QPS limits:
At the Source level
At the Campaign level
Whenever you set a QPS value, the system automatically calculates and applies both the Hourly and Daily Ad Request Caps. This ensures your sources 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 cap. While they are not visible in the UI yet, they are applied in the background to safeguard traffic flow and keep source 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 = 1,000
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.