RE: "bidresponse proto could not be parsed" error

30 views

Skip to first unread message

Authorized Buyers API Forum Advisor

unread,

Dec 17, 2024, 2:37:41 PM 12/17/24

to youngkw...@ptbwa.com, google-doubleclick-a...@googlegroups.com

Hello,

I've been looking at your included bid responses, in addition to more recent ones you've been submitting since your initial posting. The structure and field typing generally look fine, though I do see some fields unnecessarily populated with empty values in some cases. There are a lot of variables that can affect how your response is interpreted, so I'll list everything that I've noticed that you may want to investigate:

The URL you specify in adm doesn't seem to link to a VAST document. Bidding with an approved video creative may impact the error response.
Generally speaking, successful responses consistently return the BidResponse.seatbid.bid.ext.billing_id extension ( cid would also work, but is deprecated.) It seems that you don't consistently include this in your response.
Generally speaking, successful responses consistently return BidResponse.seatbid.bid.crid . It seems that you don't consistently include this in your response.

I'd recommend adjusting your response based on these points and then checking back to see if your bids are making it to the auction in RTB Breakout.

This message is in relation to case "ref:!00D1U01174p.!5004Q02vGpJ6:ref" (ADR-00278966)

Thanks,

Mark Saniscalchi

Authorized Buyers API Team

Feedback
How was our support today?

Reply all

Reply to author

Forward

0 new messages