Fail Reasons
Axis
The Fail Reasons list on Axis provides a comprehensive overview of potential issues encountered during integrations. It serves as a valuable tool for troubleshooting and resolving integration challenges efficiently. By identifying specific reasons for failures, users can address issues promptly, ensuring smoother integration processes and minimizing downtime.
Description | Type | Explanation |
Valid Bid request is sent to DSP | req_valid | A valid bid request is sent from the SSP to the DSP. This means that there is an opportunity for an ad impression, and the system is attempting to find a suitable advertiser to fill that impression. |
Valid SSP request is dropped because no apropriate demand | ad_valid | The SSP receives a valid request, indicating an available ad impression. However, the request is dropped because there is no suitable demand or advertiser willing to bid on this specific impression at the given time. |
DSP is timeouting | res_drop | The DSP is taking longer than the specified time to respond to the bid request. This could be due to network issues, server problems, or other technical difficulties preventing the DSP from timely processing the request. |
GZIP unpacking error | res_drop | The bid request received by the DSP is compressed using GZIP, a file compression format. However, there is an error in unpacking or decompressing the GZIP file, leading to a failure in processing the bid request. |
DSP endpoint is not available | res_drop | The endpoint or server of the DSP is not reachable or available at the moment. This could be due to server maintenance, network issues, or other problems preventing the SSP from connecting to the DSP. This appears consequently from DSP's timeouts. |
Valid SSP request | ssp_valid | A valid request is sent from the SSP to the DSP, indicating an available ad impression and seeking bids from potential advertisers. |
SSP Bid Response | none | The SSP has received bids from various DSPs and the ad auction is taking place. |
Invalid SSP BidRequest | ssp_drop | The bid request received from the SSP is invalid, possibly due to missing or incorrect information, making it impossible for the DSP to provide a valid bid response. |
No bids from DSP | none | Despite receiving a valid bid request, the DSP does not submit any bids for the available ad impression. This could be because no advertisers are interested in bidding at the given time or for the specified criteria. |
Invalid DSP BidResponse | none | The bid response from the DSP is considered invalid, possibly due to missing or incorrect information, making it impossible for the SSP to process and act upon the bid. |
IP is missing | ssp_drop | The bid request is dropped because the IP address information is missing. IP address data is crucial for targeting and identifying the user, and without it, the bid may not be processed. |
Domain is missing | ssp_drop | The bid request lacks information about the domain where the ad is to be displayed. The domain is essential for contextual targeting and ensuring that the ad is displayed in a relevant context. |
Bundle is missing | ssp_drop | The bundle information is missing from the bid request. The bundle typically refers to the mobile app or site bundle, and its absence may hinder proper ad targeting. |
Bidfloor is more or equal to SSP fixed bid price | ssp_drop | Bidfloor is more or equal to SSP fixed bid price |
Domain/Bundle is not in SSP white list | ssp_drop | The bid request is dropped because the domain or bundle is not included in the SSP's whitelist. The whitelist is a pre-approved list of domains or bundles that are allowed to participate in the ad auction. |
Domain/Bundle is in SSP black list | ssp_drop | The bid request is dropped because the domain or bundle is on the SSP's blacklist. The blacklist contains domains or bundles that are prohibited from participating in the ad auction due to various reasons, such as content violations or fraud concerns. |
Tmax is less than 120ms | ssp_drop | The bid request is dropped because the maximum allowable response time (Tmax) specified by the SSP is less than the minimum required time for the DSP to process and respond to the bid request. |
Bidfloor is more than $50 | ssp_drop | The bid request is dropped because the bidfloor specified by the SSP is higher than the maximum bid amount the DSP is willing to offer, which in this case is set at $50. |
ADM is missing | res_drop | The bid response is dropped because the ad markup (ADM) is missing. The ADM contains the actual creative content of the ad, and its absence means that the SSP cannot display the ad. |
Bid price is missing | ssp_drop | The bid request is dropped because the bid price information is missing. The bid price is essential for determining the winning bid and the cost of the ad impression. |
Bid price is less than bidfloor | res_drop | Bid price is less than bidfloor |
CRID is blocked | res_drop | The bid request is dropped because the Creative ID is blocked. This could be due to the CRID being associated with inappropriate content, a violation of policies, or other reasons that make it unsuitable for display. |
Traffic type is undefined | ssp_drop | The bid request is dropped because the traffic type is not clearly defined. |
Category is in BCAT | res_drop | The bid reqsponse is dropped because the content category is found in the IAB Content Taxonomy (BCAT) list, which may include categories that are considered inappropriate or unsuitable. |
Attribute is in BATTR | res_drop | The bid response is dropped because the creative attributes match those in the IAB Creative Attributes (BATTR) list, indicating characteristics that may be undesirable or restricted by the SSPs. |
Site or app object in missing | ssp_drop | The bid request is dropped because essential information about the site or app where the ad is to be displayed is missing. This information is crucial for proper ad targeting. |
Impression object is missing | ssp_drop | The bid request is dropped because the impression object, which includes details about the ad impression such as ad size, format, and placement, is missing. This information is necessary for DSPs to make informed bidding decisions. |
Video is not allowed in SSP settings | ssp_drop | The bid request is dropped because video content is not allowed according to the SSP settings (due to the preferences set up in the integration). |
Banner is not allowed in SSP settings | ssp_drop | The bid request is dropped because banner ads are not permitted according to the SSP settings (due to the preferences set up in the integration). |
Native is not allowed in SSP settings | ssp_drop | The bid request is dropped because native ads are not allowed according to the SSP settings (due to the preferences set up in the integration). |
Ad size is missing | ssp_drop | The bid request is dropped because crucial information about the ad size is missing. Ad size is essential for proper rendering and display of the ad, and its absence hinders the processing of the bid request. |
Request parameter is missing in native | ssp_drop | The bid request is dropped because a necessary request parameter is missing in the native ad context. Without this parameter, the SSP may be unable to properly handle and serve the native ad. |
Mobile web is not allowed in SSP settings | ssp_drop | The bid request is dropped because mobile web traffic is not permitted according to the SSP settings (due to the preferences set up in the integration). |
Desktop is not allowed in SSP settings | ssp_drop | The bid request is dropped because desktop traffic is not allowed according to the SSP settings (due to the preferences set up in the integration). |
Mobile app is not allowed in SSP settings | ssp_drop | The bid request is dropped because mobile app traffic is not permitted according to the SSP settings (due to the preferences set up in the integration). |
Unsupported audio ad format | ssp_drop | Unsupported audio ad format |
CTV is not allowed in SSP | ssp_drop | The bid request is dropped because Connected TV traffic is not allowed according to the SSP settings (due to the preferences set up in the integration). |
DSP bidfloor is higher than fixed price | req_drop | DSP bidfloor is higher than fixed price |
Multiple ad formats | ssp_drop | The bid request is dropped because it contains multiple ad formats, and the system may only support a specific format. This helps maintain consistency and ensures proper rendering of ads on the publisher's site. |
DSP bidfloor is higher than bidfloor max | req_drop | DSP bidfloor is higher than bidfloor max |
Invalid web page | ssp_drop | The bid request is dropped because the web page associated with the impression is considered invalid. This could be due to issues with the URL or content of the page that make it unsuitable for serving ads. |
DSP partner is not in white list | none |
|
DSP is blocked for 5 sec due to high timeouts | req_drop | The bid request is dropped because the DSP is temporarily blocked for a specified duration (5 seconds in this case) due to a high number of timeouts. Timeouts may occur when the DSP takes too long to respond to bid requests. |
GEO QPS limit is reached | req_drop | The bid request is dropped because the Geo QPS limit has been reached. This limit helps manage the volume of bid requests from specific geographical regions. |
DSP is blocked in inventory settings | req_drop | The bid request is dropped because the DSP is explicitly blocked in the inventory settings of the SSP. This could be due to policy violations, disputes, or other reasons leading to the exclusion of the DSP from participating. |
Ad format is not allowed | none | Ad format is not allowed |
QPS limit is reached | req_drop | The bid request is dropped because the overall QPS limit set on the DSP side in the system has been reached. This helps manage the volume of bid requests and prevents overload on the DSP's according to their preferences. |
DSP tmax is higher than SSP tmax | req_drop | DSP tmax is higher than SSP tmax |
Inventory is blocked in DSP settings | req_drop | The bid request is dropped because the inventory associated with the ad impression is blocked in the settings of the DSP. This could be due to specific targeting preferences or other considerations. |
QPS limit is reached on SSP | ssp_drop |
|
Unauthorized traffic size | req_drop |
|
Bidfloor with markups is higher than DSP max bidfloor | req_drop | The bid request is dropped because the bidfloor, including any markups, exceeds the maximum bidfloor set by the DSP. Markups represent additional costs added to the bidfloor, and their total surpasses the DSP's acceptable limit. |
Fixed bid price is less than bidfloor | req_drop |
|
Web traffic is not allowed in DSP settings | req_drop | Explanation: The bid request is dropped because web traffic is not permitted according to the DSP settings. The DSP may have specific preferences or restrictions regarding the type of traffic it accepts. |
CTV traffic is not allowed in DSP settings | req_drop | The bid request is dropped because Connected TV traffic is not allowed according to the DSP settings. The DSP may have specific policies or preferences regarding the types of traffic it supports. |
inApp traffic is not allowed in DSP settings | req_drop | The bid request is dropped because in-app traffic is not permitted according to the DSP settings. The DSP may focus on web traffic or have specific preferences regarding the platforms it supports. |
Adapter configuration is not found | req_drop |
|
Blocked by Filter List Manager | req_drop |
|
Country is in DSP Geo BL | req_drop | Explanation: The bid request is dropped because the country specified in the request is on the DSP's Geo Black List. Requests from countries on this list are automatically rejected. |
Country is not in DSP Geo WL | req_drop | The bid request is dropped because the country specified in the request is not on the DSP's Geo White List. Requests from countries not on this whitelist are rejected. |
Traffic is not premium | req_drop | The bid request is dropped because the traffic is not considered premium. Premium traffic may be defined by specific characteristics, quality metrics, or other criteria, and anything falling below the premium threshold is rejected. |
DSP is not in Allowed list on SSP | req_drop | The bid request is dropped because the DSP is not included in the allowed list maintained by the SSP. Only DSPs on the allowed list are permitted to participate in the ad auction. |
SSP is not in Allowed list on DSP | req_drop | The bid request is dropped because the SSP is not included in the allowed list maintained by the DSP. Only SSPs on the allowed list are accepted for processing bid requests. |
IFA is missing | req_drop | The bid request is dropped because the Identifier for Advertisers (IFA) is missing. This identifier is crucial for tracking and targeting users, and its absence can impact the effectiveness of ad campaigns. |
Response is blocked by Filter List Manager | res_drop |
|
Allowed list is not ready | req_drop | The bid request is dropped because the allowed list, which specifies approved entities, is not ready or available for processing. This could be due to a delay in list updates or other operational issues. |
Request does not include buyer id | req_drop | The bid request is dropped because it does not include the buyer ID, which is essential for identifying the DSP or buyer associated with the bid request. |
DSP bid floor is more or equal to DSP CPM | req_drop |
|
DSP bid floor is greater than DSP max bid floor | req_drop |
|
Display manager value is not allowed | req_drop |
|
Creative size is not matching with ad request size | res_drop | The bid response is dropped because the size of the creative (ad) does not match the size specified in the ad request. Proper sizing is crucial for the accurate and appealing display of ads. |
Offer not found | req_drop | The bid request is dropped because the targeting in it doesn't match the appropriate DSP integration settings. |
Wrong targeting in matching integrations | req_drop | Quantifies targeting errors within matching integrations in offers. |
Vast Valid | vast_valid | The VAST (Video Ad Serving Template) response is valid and meets the required specifications. This reason typically indicates a successful and acceptable ad response. |
Integration mismatch | req_drop | Quantifies the number of non-matching integrations for the request |
Don`t hesitate to contact us in case you have any questions!