VAST Error Codes
VAST Error Codes are used to debug problems with ad serving. The IAB has created a standard set of Error Codes. In addition SpringServe has created custom error codes to give more insight into "901: General VPAID Errors". This will help debug specific issues with effecting fill.
Vast Error codes are captured in four ways.
- When the player fires the SpringServe Vast Error Pixel
- When the SpringServe VPAID captures a Vast Error when trying to call and process a demand tag
- When SpringServe captures an error code for OpenRTB use-cases when we don't get a valid bid response back from bidders.
- When SpringServe captures an error code for Vast only Server Side calls when trying to call and process a demand tag and we could not send a valid vast response back to the player.
IAB VAST Error Codes
Below is a table of the IAB Vast Error Codes along with SpringServe specific information that will help you debug demand tags that have a high error rate.
Code | Description | Time of Occurrence |
---|---|---|
100 | XML parsing error. | Pre-Ad |
101 | VAST schema validation error. | Pre-Ad |
102 | VAST version of response not supported. | Pre-Ad |
200 | Trafficking error. The video player received an ad type that it was not expecting and/or cannot display. | Pre-Ad |
201 | Video player expecting different linearity. | Pre-Ad |
202 | Video player expecting different duration. | Pre-Ad |
203 | Video player expecting different size. | Pre-Ad |
300 | General wrapper error. | Pre-Ad |
301 | Timeout of VAST URI provided in wrapper element or of VAST URI provided in a subsequent wrapper element. (RI was either unavailable or reached a timeout as defined by the video player.) | Pre-Ad |
302 | Wrapper limit reached, as defined by the video player. Too many wrapper responses have been received with no inLine response. | Pre-Ad |
303 | No ads VAST response after one or more wrappers. This also includes the number of empty VAST responses from fallback. | Pre-Ad |
400 | General linear error. The video player is unable to display the linear ad. | Pre-Ad |
401 | File not found. Unable to find linear/mediaFile from URI. | Pre-Ad |
402 | Unable to download or timeout of MediaFile URI. | Pre-Ad |
403 | Could not find a media file that is supported by this video player, based on the attributes of the MediaFile element. | Post-Ad |
405 | Problem displaying a media file. Video player found a MediaFile with supported type but couldn't display it. MediaFile may include: unsupported codecs, different MIME type than MediaFile@type, unsupported delivery method, etc. | Post-Ad |
406 | A mezzanine file was required, but not provided. | Pre-Ad |
407 | The mezzanine file was downloaded for the first time, so the ad did not serve. | Pre-Ad |
408 | The ad returned in the VAST response was rejected. | Pre-Ad |
409 | The interactive creative defined in the InteractiveCreativeFile node was not executed. | Pre-Ad |
410 | The code referenced in the Verification node was not executed. | Pre-Ad |
500 | General NonLinearAds error. | Pre-Ad |
501 | Unable to display non-linear ad because creative dimensions do not align with creative display area (in other words, the creative dimension was too large). | Pre-Ad |
502 | Unable to fetch NonLinearAds/NonLinear resource. | Pre-Ad |
503 | Could not find NonLinear resource with supported type. | Pre-Ad |
600 | General CompanionAds error. | Pre-Ad |
601 | Unable to display companion because creative dimensions do not fit within the companion display area (in other words, space was not available). | Pre-Ad |
602 | Unable to display required companion. | Pre-Ad |
603 | Unable to fetch CompanionAds/Companion resource. | Pre-Ad |
604 | Could not find Companion resource with supported type. | Pre-Ad |
900 | VAST 2 error. | Pre-Ad |
901 | General VPAID error. | Post-Opportunity |
SpringServe Custom VAST Error Codes
SpringServe Custom VAST 1500 Error Codes give you more insight into errors that normally fit into "901: General VPAID Error". These error codes will give you more insight into SpringServe specific issues.
Error Code | Description | Time of Occurence | SpringServe Specific Details |
---|---|---|---|
1301 | The demand partner did not return a bid | Pre-Ad | |
1302 | HTTP timeout while requesting VAST | Pre-Ad | |
1303 | HTTP error while requesting VAST | Pre-Ad | |
1304 | No HTTP response from VAST request | Pre-Ad | |
1305 | HTTP 4XX status from VAST request | Pre-Ad | |
1306 | HTTP 5XX status from VAST request | Pre-Ad | |
1307 | all other non HTTP 200 status codes from VAST request | Pre-Ad | |
1308 | VAST request timeout | Pre-Ad | Springserve VAST timeout is 3 seconds |
1309 | Wrapper chain timeout | Pre-Ad | Springserve wrapper chain timeout is 5 seconds |
1310 | Demand partner bid below the floor | Pre-Ad | |
1311 | Mixed Content Error | Pre-Ad | non secure ad returned for a secure tag |
1312 | Index Request Timeout | Pre-Ad | Index's json call timed out |
1313 | Header bidding error Requesting VAST | Pre-Ad | |
1314 | Header bidding missing request parameters | Pre-Ad | |
1315 | Header Bidding Bid Request Timeout | Pre-Ad | |
1316 | Max Broadcast Timeout | Pre-Ad | A broadcast tier timed out at 5 seconds |
1317 | Openrtb Request Timeout | Pre-Ad | There was a timeout on the openrtb request to our adserver |
1318 | Openrtb Request Error | Pre-Ad | There was an error getting the openrtb responses from our adserver |
1319 | Openrtb No Bids | Pre-Ad | Openrtb request returned no bids |
1320 | IMA Manager Loader Error | Pre-Ad | There was an error loading the IMA Ads Manager. |
1321 | IMA Manager Loader Timeout | Pre-Ad | Timeout while loading the IMA Ads Manager |
1323 | Invalid Header Bidding Bid Response | Post-Opportunity | The Bid Response from client-side HB could not be parsed. |
1501 | Error Loading Flash Bridge | Post-Opportunity | |
1502 | Error Playing Flash Bridge | Post-Opportunity | The flash bridge was loaded ok, but when trying to actually start the ad there was an error |
1503 | Error Loading IMA Wrapper | Post-Opportunity | This is for Adx tags that require the IMA sdk to be loaded to run the tags. There was an error loading/playing the demand tag through the IMA sdx |
1504 | Error Playing Video Asset | Post-Opportunity | There was an error trying to play an video asset (mp4, webm) that resulted from a demand tag |
1505 | Child Handshake Error | Post-Opportunity | Error calling the handshake method on the child vpaid loaded from a demand tag |
1506 | Child INIT VPAID Error | Post-Opportunity | Error initializing the child vpaid that resulted from a demand tag |
1507 | Child Set Volume Error | Post-Opportunity | Attempted to set the volume on a child VPAID but received an exception |
1508 | Unexpected VAST Processing Exception | Post-Opportunity | |
1509 | Error loading child VPAID | Post-Opportunity | |
1510 | General Demand Tag Error | Post-Opportunity | |
1511 | SpringServe Vast Validation Error | Post-Opportunity | This error means that information expected within the VAST xml is missing. For example missing impression or error pixels, missing linear add element within the VAST xml |
1512 | Error sending a js demand opportunity event | Post-Opportunity | |
1513 | Parent Called Stop Ad | Post-Opportunity | |
1514 | Parent Called Skip Ad | Post-Opportunity | |
1515 | Complete Without Impression | Post-Opportunity | |
1516 | Supply Tag Timeout | Post-Opportunity | |
1517 | Demand Tag Timeout | Post-Opportunity | |
1518 | Broadcast Timeout | Post-Opportunity | |
1519 | Max Broadcast Timeout | Post-Opportunity | |
1520 | Demand Partner Timeout | Post-Opportunity | |
1521 | There was an error requesting an ad from IMA | Post-Opportunity | |
1522 | There was an error loading the IMA ad | Post-Opportunity | |
1523 | There was an error playing the IMA ad | Post-Opportunity | |
1524 | There was an error initializing the IMA AdsManager when attempting to start the ad | Post-Opportunity | |
1525 | General error initializing the IMA ad | Post-Opportunity | |
1526 | Error initializing the IMA wrapper | Post-Opportunity | |
1527 | Uncaught Error Requesting Flash Demand | Post-Opportunity | |
1528 | Uncaught Error Requesting IMA Demand | Post-Opportunity | |
1529 | Uncaught Error Requesting Media Demand | Post-Opportunity | |
1530 | Uncaught Error Requesting VPAID Demand | Post-Opportunity | |
1531 | Openrtb bidder did not fill | Post-Opportunity | (Bidder Error Code) |
1532 | Openrtb no fill | Post-Opportunity | none of the openrtb bids resulted in an impression (Standard Error Code) |
SpringServe Custom Error Codes for SSB, OpenRTB, and TC+
The error codes below are designed to give you more insight into server side use-cases when there isn't a VPAID involved and also for OpenRTB when there is an error receiving valid bid responses from bidders.
Vast Error Code | Description | Occurrence | Notes |
---|---|---|---|
1601 | VAST XML Parsing Error | Pre-Ad | Invalid XML in vast response |
1604 | Error No Bid | Pre-Ad | No bid received from demand partner |
1605 | HTTP timeout while requesting VAST | Pre-Ad | Timed out before getting a vast response from bidder |
1606 | HTTP error while requesting VAST | Pre-Ad | Generic HTTP Error getting a vast response from bidder |
1607 | No HTTP response from VAST request | Pre-Ad | No HTTP response received |
1608 | HTTP 4XX status from VAST request | Pre-Ad | HTTP 400 Status Code in vast response |
1609 | HTTP 5XX status from VAST request | Pre-Ad | HTTP 500 Status Codes in vast response |
1610 | all other non HTTP 200 status codes from VAST request | Pre-Ad | catch-all in case this is something not in error codes 1605 through 1609 |
1611 | VAST request timeout | Pre-Ad | Response took longer than maximum allocated time |
1612 | Wrapper chain timeout | Pre-Ad | wrapper chain exceeded max auction duration |
1613 | Bad Demand Tag Endpoint URL | Pre-Ad | Endpoint URL with spaces, &'s or other un-parseable and/or invalid characters. |
1614 | Max number of wrappers for SSB | Pre-Ad | Number of wrappers more than 3 |
1615 | Bid below the floor | Pre-Ad | Bid received had a value below bid floor |
1616 | Mixed Content Error | Pre-Ad | http ad returned for https ad call |
1619 | No Duration | Pre-Ad | On ad pods the vast is missing <duration> attribute |
1620 | Invalid URL in wrapper | Pre-Ad | Invalid URL found in wrapper |
1621 | Invalid URL in redirect | Pre-Ad | Invalid URL found in redirect while getting demand |
1622 | Invalid Json | Pre-Ad | The JSON rendered was invalid |
1623 | Not included in ad pod | Post-Ad | |
1624 | Empty Vast Response | Pre-Ad | |
1625 | Only VPAID ad(s) returned but not allowed | Pre-Ad | |
1626 | Ad discarded due to pod opt out | Post-Ad | Ad(s) were returned but the pod opted out due to too many empty slots |
1627 | Pod slots full | Post-Ad | |
1628 | Ad duration greater than pod time unfilled | Post-Ad | |
1629 | Ad duration greater than slot max | Post-Ad | |
1630 | Ad duration less than slot min | Post-Ad | |
1631 | VastAdTagUri element incorrectly formatted in the vast response of a wrapper. | Pre-Ad | |
1632 | Wrapper leads to an empty VAST response. | Pre-Ad | |
1633 | Redirect URL Invalid | Pre-Ad | |
1634 | Advertiser Domain not in whitelist | Post-Ad | |
1635 | Advertiser Domain in Blacklist | Post-Ad | |
1636 | Targeting block for unknown advertiser domain | Post-Ad | |
1637 | Ad excluded from pod due to duplicate creative | Post-Ad | |
1638 | Not enough time left to follow wrapper request | Pre-Ad | |
1639 | Ad excluded from pod due to competitive exclusions block | Post-Ad | |
1640 | Duplicate removed due to unique pod ID | Post-Ad | |
1641 | Targeting block for Media File Duration | Post-Ad | |
1642 | Targeting block for Media File Bitrate | Post-Ad | |
1643 | Targeting block for Media File Mime Type | Post-Ad | |
1644 | Creative excluded due to demand partner's competitive exclusion list | Post-Ad | |
1645 | Creative excluded due to campaign's competitive exclusion list | Post-Ad | |
1646 | Creative excluded due to audio volume targeting | Post-Ad | |
1647 | The bid price was above our maximum allowed | Post-Ad | |
1648 | Ad excluded due to advertiser domain that has content that was not brand-safe | Post-Ad | |
1649 | Ad excluded due to advertiser domain that has malicious content | Post-Ad | |
1650 | Ad excluded due to advertiser domain that has objectionable content | Post-Ad | |
1651 | Ad excluded due to demand tag's IAB Category competitive exclusion list | Post-Ad | |
1652 | Ad excluded due to demand partner's IAB Category competitive exclusion list | Post-Ad | |
1653 | Ad excluded due to campaign's IAB Category competitive exclusion list | Post-Ad | |
1654 | Ad excluded as advertiser domain belongs to IAB categories in blocklist | Post-Ad | |
1655 | Ad Excluded as advertiser domain belongs to IAB categories not in allowlist | Post-Ad | |
1656 | Ad excluded as advertiser domain belongs to IAB categories do not meet targeting requirements | Post-Ad | |
1657 | Creative excluded due to media container targeting | Post-Ad | |
1658 | Creative excluded due to stitched creative targeting | Post-Ad | |
1659 | Ad excluded from pod due to duplicate advertiser domain | Post-Ad | |
1660 | Ad excluded from Pod due to detected adomain's content category being blocked due to competitive exclusions | Post-Ad | |
1662 | Ad excluded from pod due to duplicate IAB Tier 1 category | Post-Ad | |
1663 | Ad excluded from pod due to duplicate IAB Tier 2 category | Post-Ad | |
1667 | Ad excluded as overridden advertiser domain belongs to IAB categories in blocklist | Post-Ad | |
1668 | Ad discarded due to Political Ad Targeting | Post-Ad | |
1669 | Ad excluded due to creative audit status | Post-Ad | |
1670 | VAST XML pixel processing error | Post-Ad | Issue adding SpringServe pixels to ads due to problematic XML in response |
1671 | Creative was excluded because it had no valid video format paths | Post-Ad | |
1672 | Ad excluded from pod due to duplicate advertiser domain | Post-Ad | |
1673 | Ad excluded due to creative frequency cap | Post-Ad | |
1674 | Ad excluded from pod due to duplicate detected advertiser domain | Post-Ad | |
1675 | Ad excluded from pod due to competitive exclusions block on detected advertiser domain | Post-Ad | |
1676 | Ad discarded due to Companion Ad block | Post-Ad | |
1677 | Ad excluded from unique pod id due to duplicate advertiser domain | Post-Ad | |
1678 | Ad excluded due to Language Targeting | Post-Ad | |
1679 | Rejected by Request Governor | Pre-Ad | Magnite Streaming error |
1680 | Rejected Supply Domain | Pre-Ad | Magnite Streaming error |
1681 | Rejected Bundle ID | Pre-Ad | Magnite Streaming error |
1682 | IP Blacklisted | Pre-Ad | Magnite Streaming error |
1683 | Error No Bid | Pre-Ad | Magnite Streaming error |
1684 | Ad Ok | Pre-Ad | Magnite Streaming error |
1685 | General Error | Pre-Ad | Magnite Streaming error |
1686 | Bad Ad Call | Pre-Ad | Magnite Streaming error |
1687 | Invalid Ad Unit | Pre-Ad | Magnite Streaming error |
1688 | Rejected by Request Limit | Pre-Ad | Magnite Streaming error |
1689 | VAST Rendering Error | Pre-Ad | Magnite Streaming error |
1690 | Rejected by Regulation | Pre-Ad | Magnite Streaming error |
1691 | Detected Advertiser Domain not in allowlist | Post-Ad | |
1692 | Detected Advertiser Domain in block list | Post-Ad | |
1693 | Rejected by regulation | Post-Ad | Magnite Streaming error |
1694 | No Ad | Pre-Ad | Magnite Streaming error |
1696 | Scanned creative not in allowlist | Post-Ad | |
1697 | Scanned creative in blocklist | Post-Ad | |
2000 | Bid price less than minimum price bucket | Post-Ad | |
2001 | Bid price less than minimum bucket for specific duration | Post-Ad | |
2020 | Duration below minimum | Post-Ad | |
2021 | Duration above maximum | Post-Ad | |
2022 | Duration invalid | Post-Ad | |
2023 | Bid price less than bid floor for deal | Post-Ad | |
2024 | Bid returned does not contain deal id(s) forwarded in bid request | Post-Ad | |
4000 | Demand Tag filtered due to ultra low fill rate | Pre-Ad | Demand tag has not been called because of it's very low fill rate. |