Publisher Caps monitor and control traffic using limits such as volume, conversions, revenue, or spend. For the most flexible hourly, rolling-window, and financial guardrails, use Advanced Caps.
Choose the correct scope
Publisher scope: applies across the publisher's eligible traffic according to the configured cap.
Campaign–Publisher scope: applies only to that publisher's traffic within the selected campaign.
Choose the scope deliberately. A publisher-wide cap and a Campaign–Publisher cap can measure different traffic and produce different outcomes.
Available guardrails
Advanced Caps support hourly, daily, weekly, monthly, and rolling-window controls, depending on the metric and configuration available in the portal. Guardrails can evaluate measures such as total calls, connected calls, conversions, publisher payout/spend, or buyer revenue.
Actions and financial side
The cap location determines the financial side affected by a reduction action:
A publisher-side cap can reduce publisher payout or make the publisher's traffic ineligible.
A buyer-side cap can reduce buyer-side revenue or make that route ineligible.
Review the scope, metric, and action together before saving. “Lower Bid” or another financial action should not be interpreted without checking where the cap is configured.
Setup checklist
Open the Publisher or Campaign–Publisher configuration that matches the intended scope.
Select the metric and period.
Set the threshold and action.
If live-call counting or a rolling window is available and required, configure it explicitly.
Save and test with controlled traffic.
Review reporting to confirm which calls and financial values are counted.
Concurrency
This article does not establish that a publisher-specific concurrency limit exists inside an individual campaign. Confirm the exact campaign, publisher, and concurrency requirement before promising or applying that setup.
Overlapping caps
When multiple caps overlap, test the combined behavior with controlled traffic. Do not assume which cap will determine the outcome without verifying the current implementation and reporting.