OpenRTB Bid Request Validator

Ek OpenRTB 2.5 ya 2.6 bid request ko IAB rules ke against apne browser mein validate karein. Jo JSON aap paste karte hain woh aapke device par rehta hai.

OpenRTB Bid Request Validator poori tarah aapke browser mein chalta hai. Jo bid request JSON aap paste karte hain woh aapke device par parse aur check hota hai aur kabhi ArrayKit ko upload ya kisi exchange ko nahi bheja jaata.

OpenRTB Bid Request Generator kholein

OpenRTB Bid Request Validator ke baare mein

OpenRTB Bid Request Validator ek real-time bidding request ko IAB OpenRTB 2.5 aur 2.6 rules ke against us pal lint karta hai jab aap use paste karte hain. Ek version chunein aur yeh confirm karta hai ki required id aur imp[] present hain, ki har impression bilkul ek media object carry karta hai (banner, video, native, ya audio), ki field types line up hain, aur ki har enumerated field — auction type, video protocols, placement ya plcmt, devicetype, connectiontype, aur api frameworks — ek aisa code rakhta hai jo us version mein sach mein exist karta hai. Findings ek pass/fail verdict plus ek path-addressed list ke roop mein aate hain jispar aap seedhe jump kar sakein. Ad-ops engineers aur SSP/DSP integrators yahan live traffic samples debug karte hain bina kisi third-party endpoint ko bid request POST kiye — yeh sab aapke device par chalta hai.

Features

OpenRTB Bid Request Validator kaise use karein

  1. Woh OpenRTB version chunein jo aapka exchange bolta hai (2.5 ya 2.6)
  2. Bid request JSON paste karein, ya expected shape dekhne ke liye sample load karein
  3. Pass/fail verdict aur path-addressed findings list padhein
  4. Har error ko flagged path par fix karein aur re-check karein jab tak request valid na ho

Example

Input

{
  "id": "r1",
  "imp": [{ "id": "1", "video": { "plcmt": 5 } }],
  "site": { "id": "s1" }
}

Output

Invalid (OpenRTB 2.6)
imp[0].video.plcmt — 5 is not a valid video plcmt for OpenRTB 2.6. Allowed: 1, 2, 3, 4.

plcmt field OpenRTB 2.6 mein sirf codes 1–4 accept karta hai.

Common errors aur troubleshooting

Aksar pooche jaane wale sawaal

OpenRTB Bid Request Validator kya check karta hai?
Yeh required id aur ek non-empty imp[] array confirm karta hai, ki har impression mein bilkul ek media object hai (banner, video, native, ya audio), ki field types correct hain, aur ki har enumerated field ek aisa code rakhta hai jo selected OpenRTB version ke liye valid hai.
OpenRTB 2.6 mein placement aur plcmt mein kya farak hai?
video.placement (Video Placement Types, codes 1–5) 2.5 field hai; OpenRTB 2.6 ise video.plcmt (Plcmt Subtypes, codes 1–4) ke favor mein deprecate karta hai. 2.6 mein validator plcmt check karta hai aur agar legacy placement field abhi bhi present ho toh warn karta hai.
Meri request fail kyun hoti hai jab ek impression banner aur video dono carry karta hai?
Validator per impression bilkul ek media object enforce karta hai, isliye ek hi imp par ek banner plus ek video ko us imp path par ek error report kiya jaata hai. Multi-format inventory ko iske bajaye alag impression objects ke roop mein model karein.
devicetype aur connectiontype ke liye kaunse codes allowed hain?
devicetype 2.5 mein 1–7 aur 2.6 mein 1–8 (8 = OOH Device) accept karta hai. connectiontype 2.5 mein 0–6 aur 2.6 mein 0–7 (7 = Cellular 5G) accept karta hai. Validator error message mein aapke selected version ke allowed codes list karta hai.
Kya OpenRTB 2.5 aur 2.6 ke beech switch karne se result badalta hai?
Haan. Enumeration sets version-aware hain, isliye 2.6 mein add hue codes (OOH devicetype, 5G connectiontype, SIMID api, plcmt field) 2.6 mein validate hote hain lekin 2.5 mein reject hote hain. Hamesha woh version chunein jo aapke exchange ne negotiate kiya.
Kya jab main validate karta hoon toh meri bid request ek ad server ko bheji jaati hai?
Nahi. Tool JSON ko aapke device par parse aur check karta hai aur kabhi ek remote ad tag fetch ya request POST nahi karta. Bid request ke baare mein kuch bhi ArrayKit ya kisi exchange ko upload nahi hota.

Related tools

Saare ArrayKit tools