Skip to main content

Slot Requests (Campaign Level)

Updated

The Slot Requests setting on the campaign level controls how many outgoing requests are generated for a campaign from a single incoming request.

Campaign-level settings can override Source-level Slot Requests logic.

 

Campaign Slot Requests settings

 

Available options

  • Use source settings

The campaign inherits Slot Requests behavior from the Source.

  • If Source uses Ad Pods or slot-based logic, it will be applied to this campaign.

  • If Source does not multiply requests, the campaign will receive a single request.

 

  • Disable slot requests

Disables request multiplication for this campaign.

  • Always results in: 1 incoming request → 1 outgoing request

  • Use this option when the campaign must receive only a single request, regardless of Source or Ad Pod settings.

 

  • Custom

Manually define how many outgoing requests should be generated for this campaign.

  • Example: 1 incoming request → 3 outgoing requests

  • Fully overrides Source-level settings

  • Works with or without Ad Pods

Max Slot Requests - defines the maximum number of outgoing requests that can be generated for this campaign when Custom is selected.

 

Source & Campaign Settings Logic

Source levelCampaign levelResult
DisabledUse source settings1 request
DisabledDisable slot requests1 request
DisabledCustomCampaign settings are used
Use number of slotsUse source settingsSlots taken from pod_ad_slots OR calculated as pod_max_dur ÷ 15, capped at 6 slots
Use number of slotsDisable slot requests1 request
Use number of slotsCustomCampaign settings are used
CustomUse source settingsSource custom value is used
CustomDisable slot requests1 request
CustomCustomCampaign settings are used

 

Key notes

  • Custom on the campaign level always has priority over Source settings.

  • Use source settings strictly follows the Source configuration.

  • This setting is useful for fine-tuning traffic distribution and campaign load independently of Source behavior.