Browse Video Advertising Error Codes
Error Codes – Index
100 – 102: VAST XML Document Errors
200 – 203: VAST Creative File Errors
300 – 303: VAST Ad Request Errors
400 – 410: VAST Linear Tag Errors
500 – 503: VAST Non-Linear Tag Errors
600 – 604: VAST Companion Ad Errors
900 – 901: VPAID Errors
Brightcove Player Ad Errors
JWPlayer Ad Errors
1005 – 2048: IMA3 SDK Errors
Freewheel Errors
Brightcove Player Ad Errors
| Code | Fatal | Definition | Likely Cause | Remedial Action |
|---|---|---|---|---|
| adtimeout | Yes | IMA3 has timed out | A timeout managed by the plugin has expired and regular video content has begun to play. Ad integrations have a fixed amount of time to inform the plugin of their intent during playback. If the ad integration is blocked by network conditions or an error, this event will fire and regular playback resumes rather than stalling the player indefinitely | |
| ima3-hardtimeout | Yes | IMA3 hard timeout reached | A timeout managed by the Brightcove Player has expired and the ad execution has been abandoned with regular video content started. Brightcove has a setting that gives the IMA plugin a fixed amount of time to complete its execution. If it fails to do so the Player will abandon the ad execution irrespective of how far it has reached in its cycle. | If you see a high rate of this error type it’s advisable to adjust the levels accordingly in your Brightcove player settings |
| ima3error | Yes | IMA3 SDK failed to load | There was an error loading the IMA3 SDK from Google. If it occurs, no ads will be displayed and regular content will be started. The cause of this could be due to an active ad blocker intercepting the call to load the SDK. Or other network conditions might have caused the IMA3 SDK to not load properly. | If you see a high rate of this error it’s advisable to contact your Brightcove Support rep to investigate further |
Error severity levels:
Non-Fatal – An error is triggered but the video ad request is not interrupted and a video ad is successfully served.
Fatal – An error is triggered and the video ad request is stopped, preventing an ad being played. This is either followed by video content playback or a new ad request being triggered (depending on player configuration).