Dropped Requests Report

Dropped Requests Report allows you to analyze the traffic that did not reach DSPs or invalid one. You can manipulate your partner activity, having realized the causes of throttling. It displays all the possible reasons of traffic drop both before and after sending it to DSPs. 

You should know that the Dropped request report is more detailed than the DSP/SSP statistic. In DSP/SSP statistic you will see just valid bid requests, while in the Dropped Requests report you may see all requests, even invalid. 

 

Note: when comparing the number of requests, consider the following formula:
SSP Incoming Requests = Outgoing Requests + sum of Dropped requests.

Incoming requests are declared per SSP, so this metric is duplicated per each line as much times as many DSPs are connected to the SSP. Outgoing requests are replicated per DSP within one supplier.


 

1. To work with Dropped Requests Report, go to Statistics -> Dropped Requests Report.

 

2. Choose Period, SSP Endpoint, DSP Endpoint. 

3. Click ‘Generate’ button.

 

4. Work with your report. You will see the columns:
Date - The Date of current data.
SSP Endpoint - Name of SSP Endpoint from which the requests were received.
DSP Endpoint - Name of DSP Endpoint to which the requests were sent (The ‘Not set’ value in the DSP Endpoint cell means that the requests were invalid for sending to the DSP).
Incoming requests - The number of incoming requests.
Requests Sent to DSP - The number of requests that were valid for sending to DSP.

Dropped requests - The number of requests that didn’t match the DSP or didn’t pass the filters.
Failure description -  Error description.


 

 

5. Use the dropdown to select the necessary columns.