error "BidResponse proto could not be parsed" (Additional inquiry.)
배선기
I am on the same team as 'Kei' and would like to follow up on Kei's inquiry.
We have updated our logic based on your feedback and responded to the following Google BidRequest (# Request) with the following BidResponse (# Response).
However, all responses are still resulting in the "BidResponse proto could not be parsed" error.
Are there any additional factors we should check?
# BidRequest
{
"id": "5se1r7J1i3CztptiJ4qoMA",
"imp": [
{
"id": "1",
"video": {
"mimes": [
"video/mp4"
],
"linearity": 1,
"w": 384,
"h": 320,
"playbackmethod": [
6
],
"pos": 3,
"api": [
7
],
"protocols": [
2,
3,
7,
5,
6,
8
],
"skip": 1,
"placement": 3,
"playbackend": 2,
"plcmt": 4,
"ext": {
"inferredplcmt": 4
}
},
"displaymanager": "GOOGLE",
"tagid": "3577761145",
"bidfloor": 0.01,
"bidfloorcur": "SGD",
"secure": 1,
"exp": 3600,
"metric": [
{
"type": "viewability",
"value": 0.49,
"vendor": "EXCHANGE"
}
],
"ext": {
"billing_id": [
"_Our's Billing ID_"
],
"publisher_settings_list_id": [
"10001781683066928693",
"13175584563926960322"
],
"allowed_vendor_type": [
39523,
566,
113,
4648,
4651,
38523,
4680,
40824,
797,
4374,
445,
704,
4697,
776,
474,
44523,
41423,
4513,
485,
237,
780,
79,
550,
489,
144,
331,
342,
698,
414,
745,
238,
828,
767,
785
],
"ampad": 2,
"allowed_restricted_category": [
33,
32
],
"creative_enforcement_settings": {
"policy_enforcement": 2,
"scan_enforcement": 1,
"publisher_blocks_enforcement": 1
},
"auction_environment": 0,
"ae": 0
}
}
],
"site": {
"page": "https://m.fmkorea.com/index.php",
"publisher": {
"id": "pub-2430764006993310",
"ext": {
"country": "KR"
}
},
"content": {
"livestream": 0,
"producer": {},
"language": "ko"
},
"mobile": 1,
"ext": {
"amp": 0,
"page_visibility": 1,
"inventorypartnerdomain": "",
"uact": {
"wasact": 0,
"isact": 0
},
"ntype": 1
}
},
"device": {
"ua": "REDACTED FOR PRIVACY REASONS",
"ip": "REDACTED FOR PRIVACY REASONS",
"geo": {
"lat": 37.7,
"lon": 127.9,
"country": "KOR",
"region": "KR-42",
"city": "Hongcheon-gun",
"type": 2,
"utcoffset": 540,
"accuracy": 24048,
"ext": {
"geo_criteria_id": 1030735
}
},
"make": "Android",
"model": "generic",
"os": "REDACTED FOR PRIVACY REASONS",
"osv": "REDACTED FOR PRIVACY REASONS",
"devicetype": 4,
"lmt": 0,
"w": 384,
"h": 653,
"pxratio": 2.813,
"sua": {
"browsers": [
{
"brand": "REDACTED FOR PRIVACY REASONS",
"version": [
"REDACTED FOR PRIVACY REASONS"
]
},
{
"brand": "REDACTED FOR PRIVACY REASONS",
"version": [
"REDACTED FOR PRIVACY REASONS"
]
},
{
"brand": "REDACTED FOR PRIVACY REASONS",
"version": [
"REDACTED FOR PRIVACY REASONS"
]
}
],
"platform": {
"brand": "REDACTED FOR PRIVACY REASONS",
"version": [
"REDACTED FOR PRIVACY REASONS"
]
},
"mobile": 1,
"model": "REDACTED FOR PRIVACY REASONS",
"source": 2
},
"ext": {}
},
"user": {
"ext": {}
},
"at": 1,
"tmax": 350,
"cur": [
"SGD",
"USD"
],
"bcat": [
"IAB7",
"IAB7-39"
],
"source": {
"schain": {
"complete": 1,
"nodes": [
{
"asi": "google.com",
"sid": "pub-2430764006993310",
"hp": 1
}
],
"ver": "1.0"
},
"ext": {
"schain": {
"complete": 1,
"nodes": [
{
"asi": "google.com",
"sid": "pub-2430764006993310",
"hp": 1
}
],
"ver": "1.0"
}
}
},
"ext": {
"google_query_id": "REDACTED FOR PRIVACY REASONS",
"fcap_scope": 5,
"privacy_treatments": {
"allow_user_data_collection": 1
}
}
}
# BidResponse
{
"id": "ptbwa_e259c223-8779-4cc7-acef-f0415c52039c",
"cur": "SGD",
"seatbid": [
{
"bid": [
{
"id": "5se1r7J1i3CztptiJ4qoMA",
"impid": "1",
"price": 0.010768,
"nurl": "https://auc.ptbwa.com/ptbwa/v1/rtb.nurl?tag=7FSKQOXZPOUX&res_id=ptbwa_e259c223-8779-4cc7-acef-f0415c52039c&auction_price=${AUCTION_PRICE}&min_win_auction_price=${AUCTION_MIN_TO_WIN}&is_cpvc=0&imp_id=1&imp_idx=0",
"iurl": "https://creative.ptbwa.com/creatives/video/2024/12/03/17/20241203171328001.mp4",
"lurl": "https://auc.ptbwa.com/ptbwa/v1/rtb.lurl?tag=7FSKQOXZPOUX&res_id=ptbwa_e259c223-8779-4cc7-acef-f0415c52039c&lossreason=${AUCTION_LOSS}&min_win_auction_price=${AUCTION_MIN_TO_WIN}&is_cpvc=0&imp_id=1&imp_idx=0",
"adm": "https://auc.ptbwa.com/ptbwa/v1/adm_vast?tid=ptbwa_e259c223-8779-4cc7-acef-f0415c52039c&auction_price=${AUCTION_PRICE}",
"adomain": [
"ptbwa.com"
],
"crid": "VIDEO_Creative_184_491_190",
"ext": {
"billing_id": _Our's Billing ID (number)_
}
}
],
"seat": "seat_id_0"
}
]
}
Thank you.
===================================================================
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.
Thanks,
Mark Saniscalchi
Authorized Buyers API Team
I am reaching out to inquire about the "BidResponse proto could not be parsed" error. During AB testing, we have observed this error consistently for all responses. Upon reviewing the syntax, no apparent issues were found. However, the error persists in both JSON and Protobuf formats.
Below are the detailed BidResponse samples for your reference:
# Response JSon
{
"id": "_e92efedc-2e85-4083-8931-15d34694a91b",
"cur": "SGD",
"seatbid": [
{
"bid": [
{
"id": "vIflo0RGy3gI8J6Yj_4arA",
"impid": "1",
"price": 0.01035,
"nurl": "https://auc.test.com/v1/rtb.nurl?tag=7FSKQOXZPOUX&res_id=_e92efedc-2e85-4083-8931-15d34694a91b&auction_price=${AUCTION_PRICE}&min_win_auction_price=${AUCTION_MIN_TO_WIN}&is_cpvc=0&imp_id=1&imp_idx=0",
"iurl": "https://creative.test.com/creatives/video/2024/12/03/17/20241203171328001.mp4",
"lurl": "https://auc.test.com/v1/rtb.lurl?tag=7FSKQOXZPOUX&res_id=_e92efedc-2e85-4083-8931-15d34694a91b&lossreason=${AUCTION_LOSS}&min_win_auction_price=${AUCTION_MIN_TO_WIN}&is_cpvc=0&imp_id=1&imp_idx=0",
"adm": "https://auc.test.com/v1/adm_vast?tid=_e92efedc-2e85-4083-8931-15d34694a91b&auction_price=${AUCTION_PRICE}",
"adomain": [
"test.com"
],
"bundle": "",
"cat": [],
"cid": "184_491",
"crid": "VIDEO_Creative_184_491_190",
"attr": [],
"adid": "VIDEO_Creative_184_491_190",
"w": 1920,
"h": 1080
}
],
"seat": "seat_id_0"
}
],
"bidid": "_e92efedc-2e85-4083-8931-15d34694a91b"
}
# Response ProtoBuf
id: "_673f52e6-dc01-4958-9408-2bf4dac16e17"
seatbid {
bid {
id: "Tj-5QRsKeRfgEHocPNHrUg"
impid: "1"
price: 0.010226
nurl: "https://auc.test.com/v1/rtb.nurl?tag=7FSKQOXZPOUX&res_id=_673f52e6-dc01-4958-9408-2bf4dac16e17&auction_price=${AUCTION_PRICE}&min_win_auction_price=${AUCTION_MIN_TO_WIN}&is_cpvc=0&imp_id=1&imp_idx=0"
adm: "https://auc.test.com/v1/adm_vast?tid=_673f52e6-dc01-4958-9408-2bf4dac16e17&auction_price=${AUCTION_PRICE}"
adomain: "test.com"
iurl: "https://creative.test.com/creatives/video/2024/12/03/17/20241203171328001.mp4"
cid: "184_491"
crid: "190"
bundle: ""
w: 1920
h: 1080
lurl: "https://auc.test.com/v1/rtb.lurl?tag=7FSKQOXZPOUX&res_id=_673f52e6-dc01-4958-9408-2bf4dac16e17&lossreason=${AUCTION_LOSS}&min_win_auction_price=${AUCTION_MIN_TO_WIN}&is_cpvc=0&imp_id=1&imp_idx=0"
}
seat: "seat_id_0"
}
cur: "SGD"
Authorized Buyers API Forum Advisor
Looking over your included bid response, I am seeing that it populates required fields such as the billing_id extension, is valid JSON, and has the same overall structure as other bid responses that successfully enter the auction. While there could be other valid reasons that this bid response wouldn't be entered into the auction, I wouldn't expect the reason to be because the response as a whole can't be parsed. Additionally, we don't currently have any ongoing outages or bugs that would impact our ability to parse JSON OpenRTB bid responses, so this seems to be specifically affecting your bidder.
I suspect that this might be related to the fact that your account (the one associated with the specified creative) is currently in testing mode, but the specifics of that mode aren't familiar to me since it is initiated as part of the onboarding process. Generally speaking, customers with accounts in testing mode have a technical account manager working with them to ramp up their bidder integration–in the short term it might be helpful to verify with them how testing mode's dropped bids are intended to be represented in the RTB Breakout. It might just be that this is how they are displayed.
If that is not the case though, it would probably make sense to have an engineer investigate as the next step.
Thanks,
|
|
||||
Feedback
How was our support today?
