Skip to main content

Slot Requests (Source level)

Updated

Slot Requests control how many outgoing requests are sent to campaigns for one incoming request from the source.

By default:

1 incoming request → 1 outgoing request to 1 connected campaign

Slot Requests can be used with or without Ad Pods.

 

 

Slot Requests Options

  • Disabled 

    Default behavior - 1 incoming request → 1 outgoing request to 1 connected campaign

     

  • Use Number of Slots

The system uses slot information only if it is sent by the publisher.

This option works best together with Ad Pods, because slot values can be derived from pod parameters:

  • directly from pod_ad_slots, or

  • automatically from pod_max_dur
    (calculated as pod_max_dur ÷ 15, capped at 6 slots)

If no pod parameters are sent: 1 incoming request → 1 outgoing request to 1 connected campaign

 

  • Custom

You manually define how many outgoing requests should be generated.

Example: 1 incoming request → 3 outgoing requests to 1 connected campaign
 Works even when Ad Pods are not used.

A similar Slot Requests section is also available on the Campaign level.
Campaign settings can override Source settings.  See Slot Requests (Campaign Level) article.

 

Source & Campaign Settings Logic

Source level Campaign level Result
Disabled Use source settings 1 request
Disabled Disable slot requests 1 request
Disabled Custom Campaign settings are used
Use number of slots Use source settings Slots taken from pod_ad_slots OR calculated as pod_max_dur ÷ 15, capped at 6 slots
Use number of slots Disable slot requests 1 request
Use number of slots Custom Campaign settings are used
Custom Use source settings Source custom value is used
Custom Disable slot requests 1 request
Custom Custom Campaign settings are used