OpenRTB Object aur Enum Reference
Har OpenRTB 2.x enumerated list dekhein — har integer code apne matlab ke saath — aur un sab ke across apne browser mein search karein.
OpenRTB Object aur Enum Reference har enumerated list ko page ke saath bundle karta hai, isliye saare lookups aur searches aapke browser mein chalte hain. Jo bhi bid request snippet aap ek code decode karne ke liye paste karte hain woh aapke device par rehta hai aur kabhi ArrayKit ko upload nahi hota.
OpenRTB Bid Request Validator kholein
OpenRTB Enum Reference ke baare mein
OpenRTB Object aur Enum Reference IAB Tech Lab OpenRTB 2.x spec ki enumerated lists ke liye ek searchable lookup hai. Har list — devicetype, connectiontype, api, protocols, linearity, playbackmethod, plcmt, placement, pos, banner.btype aur battr, contentcontext, video.delivery, feed, volume normalization aur more — apne integer code, plain-English matlab, owning object aur dotted attribute path ke saath bundled hai. Ek code, ek name, ya ek synonym jaise CTV ya wifi type karein aur yeh har list ke across ek saath match karta hai, isliye aap ek bid request field ko PDF mein dhoonde bina decode kar sakte hain. Ad-ops engineers, SSP aur DSP developers, aur QA teams build, validate, ya debug karte waqt codes ko matlab se map kar sakte hain. Sab kuch aapke browser mein chalta hai, isliye jo bid request snippets aap paste karte hain woh aapke device par rehte hain.
Features
- at aur devicetype se lekar protocols, plcmt aur battr tak har OpenRTB 2.x enumerated list cover karta hai
- Har value apna integer code ek plain-English matlab aur note ke saath dikhata hai
- Global search code, name, ya synonym se match karta hai (devicetype 3 dhoondhne ke liye CTV search karein)
- Filter chips kisi bhi list par seedhe jump karte hain — devicetype, protocols, playbackmethod, contentcontext
- Kisi bhi value ke liye ek paste-ready "attr": code snippet copy karke bid request mein daalein
- Owning object aur dotted attribute path dikhata hai, jaise device.devicetype
- OpenRTB 2.6 additions (VAST 4.2, 5G, OOH device, plcmt) shaamil karta hai aur deprecations flag karta hai
- Poori tarah aapke browser mein chalta hai — jo bid request data aap paste karte hain woh kabhi aapke device se bahar nahi jaata
OpenRTB Enum Reference kaise use karein
- Ek code, name, ya synonym jaise CTV ya wifi search box mein type karein taaki saari lists ke across match ho
- Ya filter chips se ek list pick karke use upar se neeche browse karein
- Har integer code ko uske matlab, note, aur dotted attribute path ke saath padhein
- "attr": code snippet copy karke seedhe apni OpenRTB bid request mein paste karein
Example
Input
{ "device": { "devicetype": 3, "connectiontype": 2 } }
Output
devicetype 3 = Connected TV
connectiontype 2 = Wi-Fi
Ek bid request ke integer codes ko unke OpenRTB matlab mein decode karein.
Common errors aur troubleshooting
- Ek partner devicetype 8 bhejta hai aur aapki pipeline use invalid keh kar reject karti hai. — devicetype 8 OOH Device hai, OpenRTB 2.6 mein add hua. Apne allowed set ko update karein taaki yeh newer codes (5G, VAST 4.2, plcmt) bhi accept kare.
- Aap video.placement set karte hain lekin SSP signal ignore karta hai. — placement (Video Placement Types) OpenRTB 2.6 mein deprecated hai. Iske bajaye plcmt (Plcmt Subtypes — Video) bhejein: 1 Instream, 2 Accompanying Content, 3 Interstitial, 4 Standalone.
- protocols 13 aapke validator mein fail hota hai. — protocols 13 VAST 4.2 hai, ek OpenRTB 2.6 addition. Confirm karein ki dono ends 2.6 target karte hain, ya protocols ko un versions tak restrict karein jinhe aapka player support karta hai.
- at=3 aapki bidding logic ko confuse karta hai. — Auction type 3 ka matlab hai bidfloor agreed-upon deal price hai. Values 1 aur 2 First Price aur Second Price Plus hain; 500 aur usse zyada exchange-specific hain.
Aksar pooche jaane wale sawaal
- OpenRTB Object aur Enum Reference kya hai?
- Yeh IAB OpenRTB 2.x specification ki enumerated lists ka ek searchable index hai. Har list mein har value — jaise devicetype, protocols, ya plcmt — apne integer code, matlab, owning object, aur dotted attribute path ke saath dikhayi jaati hai taaki aap bid request fields jaldi decode kar sakein.
- Yeh enumerated lists kaunse OpenRTB version cover karti hain?
- Tables OpenRTB 2.5 aur 2.6 follow karti hain. 2.6 mein add hue values, jaise connectiontype 7 (5G), devicetype 8 (OOH Device), protocols 13/14 (VAST 4.2), aur plcmt subtypes, shaamil aur noted hain, aur deprecated entries jaise placement list flag hoti hain.
- OpenRTB placement aur plcmt mein kya farak hai?
- placement legacy Video Placement Types list hai (In-Stream, In-Banner, In-Article, In-Feed, Interstitial), OpenRTB 2.6 mein deprecated. plcmt newer Plcmt Subtypes — Video list hai (Instream, Accompanying Content, Interstitial, Standalone) jo use replace karti hai. Dono yahan saath-saath listed hain.
- Ek OpenRTB bid request mein devicetype 3 ka kya matlab hai?
- devicetype 3 Connected TV hai — ek big-screen CTV ya OTT device. Is reference mein CTV ya 3 search karein aur yeh Connected TV entry par resolve hota hai, doosre device types jaise Phone (4), Tablet (5), aur OOH Device (8) ke saath.
- Main in OpenRTB lists ko code ya synonym se kaise search karoon?
- Search box mein type karein: ek integer jaise 429, ek phrase jaise second price, ya ek synonym jaise CTV ya wifi. Reference har list ke across ek saath match karta hai aur results ko list se group karta hai, isliye aapko yeh jaanne ki zaroorat nahi ki field kaunse object se belong karta hai.
- Kya yeh OpenRTB reference meri bid request data kahin bhejta hai?
- Nahi. Enumerated lists page ke saath bundled hain aur har lookup aapke browser mein hota hai. Jo bhi bid request JSON aap ek code check karne ke liye paste karte hain woh aapke device par rehta hai aur kabhi ArrayKit ko upload nahi hota.
Related tools
Saare ArrayKit tools