Skip to content

DEV Community

OpenRTB loss codes Series' Articles

Back to Aleksander Sekowski's Series

Aleksander Sekowski

Oct 14

Unity's first ten loss codes are validator failures and publisher blocks.

#openrtb #adtech #api #debugging

1 min read

Aleksander Sekowski

Oct 15

Unity loss 1011 means the bid never named a billing URL.

#openrtb #adtech #api #debugging

1 min read

Aleksander Sekowski

Oct 16

Unity uses one review reason for loss codes 1200 through 1208.

#openrtb #adtech #api #debugging

1 min read

Aleksander Sekowski

Oct 17

Unity loss codes 1213 through 1222 are the offensive-content bucket.

#openrtb #adtech #api #debugging

1 min read

Aleksander Sekowski

Oct 18

Equativ explains ten loss codes a bidder can fix in the response.

#openrtb #adtech #api #debugging

1 min read

Aleksander Sekowski

Oct 19

Equativ loss codes 1001 through 1007 are not in the OpenRTB list.

#openrtb #adtech #api #debugging

1 min read

Aleksander Sekowski

Oct 20

Chartboost loss 211 is a missing MRAID crtype, and 1000 through 1003 are Chartboost's own.

#openrtb #adtech #api #debugging

1 min read

Aleksander Sekowski

Oct 21

Digital Turbine loss 1010 is a malformed bundle, and 206 is still a bundle block.

#openrtb #adtech #api #debugging

1 min read

Aleksander Sekowski

Oct 22

Google loss 501 is the mediation waterfall, and these statuses are auction results.

#openrtb #adtech #api #debugging

2 min read

Aleksander Sekowski

Oct 23

Google rejects a VAST when the media file type is missing.

#openrtb #adtech #api #debugging

1 min read

Aleksander Sekowski

Oct 24

Google creative status codes for consent, vendors, and SDKs.

#openrtb #adtech #api #debugging

1 min read

Aleksander Sekowski

Oct 25

Xandr publishes ten loss codes for a response it will not price.

#openrtb #adtech #api #debugging

1 min read