Advanced Caps let you apply volume and financial guardrails at the Publisher, Campaign–Publisher, buyer, or other supported scope shown in the portal.
Start with scope
Publisher: measures the publisher's eligible traffic across the configured scope.
Campaign–Publisher: measures that publisher only inside the selected campaign.
Buyer-side configuration: measures or changes buyer-side routing or revenue.
The configured location determines both which traffic is counted and which financial side can be changed.
Periods and metrics
Advanced Caps can use hourly, daily, weekly, monthly, and rolling-window controls. Available metrics can include total calls, connected calls, conversions, publisher payout/spend, buyer revenue, and other supported values shown in the portal.
If active-call counting is available for the selected cap, enable it when the guardrail must account for calls that are still in progress.
Actions
Notify: alert the configured team or integration without changing eligibility.
Make ineligible: stop the scoped traffic from qualifying while the cap condition applies.
Financial reduction: reduce publisher payout on the publisher side or buyer revenue on the buyer side, according to where the cap is configured.
Configure notifications from the current Integrations area in the portal. Navigation labels can change; use the integration surface shown in your account rather than relying on an older Settings path.
Configure an Advanced Cap
Open the Publisher, Campaign–Publisher, buyer, or other supported object that matches the intended scope.
Add an Advanced Cap.
Select the metric, period or rolling window, threshold, and action.
Confirm whether calls in progress should be counted.
Save and run controlled tests below, at, and above the threshold.
Verify reporting, eligibility, notifications, and any financial adjustment.
Overlapping caps
More than one cap can apply to the same traffic. Test overlapping caps with controlled traffic and verify the resulting eligibility and financial values. Do not assume a single strictest-cap rule will determine every eligibility or financial outcome.
Concurrency is separate
Advanced Caps provide volume and spend guardrails. This guide does not establish a publisher-specific concurrency limit inside an individual campaign. Confirm that requirement separately before promising a configuration.
Verification checklist
The cap is attached at the intended scope.
The metric and period match the business rule.
The action affects the intended publisher or buyer financial side.
Notifications reach the configured destination.
Overlapping caps and threshold resets behave as expected.
Reporting reflects the calls and amounts used by the cap.