OpenRTB Bid Response Validator
Bid response mein gayab field, galat type wale price aur chhoot gaye macro pakadiye.
OpenRTB Bid Response Validator poori tarah aapke browser mein chalta hai, isliye asli deal id aur price wali response aapke device par hi jaanchi jaati hai.
Bid request jaanchiye
OpenRTB Bid Response Validator ke baare mein
Bid response OpenRTB baatcheet ka chhota hissa hai, aur usme jo bhi bigadta hai wo aksar structural hota hai, chalaak nahi: aisi bid jisme impid nahi hai, price string mein bheja gaya, aisa creative jo apna advertiser domain kabhi nahi batata, ya wo win notice jo auction price macro bhool jaata hai aur isliye galat clearing price likhta hai. Ye validator response ko waise hi padhta hai jaise koi exchange padhta, aur specification ke zaroori field ko un field se alag rakhta hai jinhe buyer aur publisher vyavhaar mein maangte hain.
Features
- Response, seatbid aur bid — teeno star par zaroori field jaanchta hai
- Error, warning aur note alag, har ek ke saath JSON path
- Price, dimension, adomain aur id field par type checking
- mtype ke liye version ke hisaab se vyavhaar, jo OpenRTB 2.6 mein aaya
- Bina price macro wale win notice aur asurakshit notice URL pakadta hai
- No-bid response aur unke nbr code jaanchta hai
- Duplicate bid id aur ek hi impression par kai bid pakadta hai
- No-bid reason aur media type ki reference table
OpenRTB Bid Response Validator kaise use karein
- Apne bidder ka lautaaya hua JSON paste kijiye
- Exchange jo protocol version chala raha hai wo chuniye
- Pehle error theek kijiye, phir warning
- Har finding ke JSON path se sambandhit bid dhoondhiye
Example
Input
{ "id": "1", "seatbid": [{ "bid": [{ "id": "b1", "impid": "1", "price": "2.15" }] }] }
Output
error seatbid[0].bid[0].price — price has to be a number, not a string
Quotes mein diya gaya price wo sabse aam wajah hai jisse bid chupchaap hata di jaati hai.
Common errors aur troubleshooting
- Bid yahan valid hai par exchange phir bhi hata deta hai. — Exchange apni shartein jodte hain: pehchana hua seat id, kisi khaas taxonomy ki category, ya pehle se approve creative. Unki integration guide bhi dekhiye.
- House ad par adomain ki warning aa rahi hai. — Phir bhi bhariye. Publisher advertiser domain se block karte hain, aur uske bina bid aksar aur kuchh dekhe bina hi hata di jaati hai.
- 2.5 integration par mtype flag ho raha hai. — Wo OpenRTB 2.6 mein aaya aur 2.5 exchange use ignore karta hai. Version selector ko wahi rakhiye jo exchange sach mein chala raha hai.
- Khaali seatbid array par sirf warning aati hai. — Kyunki ye kanoonan sahi par bekaar hai. Mana karne ka saaf tareeka HTTP 204 hai, ya nbr code wali response taaki exchange wajah likh sake.
Aksar pooche jaane wale sawaal
- OpenRTB bid response mein kaunse field zaroori hain?
- Response mein request ki id lautaane wala id chahiye. Har bid mein id, kisi impression se milta impid, price, aur adm ya nurl ke roop mein creative chahiye. Baaki specification mein optional hai.
- nbr field ka kya matlab hai?
- No-bid reason. Ek integer code jo batata hai ki bid kyun nahi aayi — 2 invalid request ke liye, 8 anjaan user ke liye — taaki exchange rapat rakh sake.
- nurl ko AUCTION_PRICE macro kyun chahiye?
- Kyunki jeetne par exchange usme clearing price rakh deta hai. Macro na ho to win notice bina price ke chalti hai aur aapke log bid likhte hain, jo diya wo nahi.
- adm aur nurl mein kya antar hai?
- adm creative ko response ke andar hi le aata hai; nurl wo URL hai jise jeetne par exchange bulata hai. Aaj inline hi aam hai kyunki wo ek round trip bachaata hai.
- Kya mtype 2.5 ki kisi cheez ki jagah leta hai?
- Wo us baat ko saaf karta hai jo pehle andaze se tay hoti thi. 2.5 mein media type impression ke object se aata tha, jo multi-format impression par toot jaata tha.
Related tools
Saare ArrayKit tools