schain (SupplyChain) object kya hai?

Yeh ek IAB Tech Lab object hai jo OpenRTB mein source.ext.schain par carry hota hai aur order mein har us advertising system ko list karta hai jisne publisher aur exchange ke beech bid request ko touch kiya, taaki buyers supply path verify kar sakein.

Har node par asi, sid, aur hp ka kya matlab hai?

asi advertising system ka canonical domain hai, sid us system ke andar seller ya reseller account id hai (uski sellers.json se matching), aur hp 1 hai jab woh node payment flow mein involved ho. Teenon per node required hain.

JSON object aur serialized string mein kya farak hai?

JSON object poora source.ext.schain structure hai jo ek bid request body mein use hota hai. Serialized string ek compact URL-encoded form hai — ver,complete!node!node — jahan har node asi,sid,hp,rid,name,domain hai, wahan use hota hai jahan ek header ya query parameter chahiye.

complete 0 versus 1 kab hona chahiye?

complete=1 sirf tab set karein jab publisher se aage har intermediary nodes array mein declared ho. Agar koi upstream hop unknown ya omitted hai, toh complete=0 set karein taaki bidders jaanein ki chain incomplete hai.

Kya yeh tool mera ad tag ya bid request ek server se fetch karta hai?

Nahi. Aap schain paste ya build karte hain aur sab kuch — serialization, parsing, aur validation — aapke browser mein locally hota hai. Jo seller ids, domains, aur node data aap enter karte hain woh kabhi ArrayKit ko nahi bheje jaate.

Kya yeh ek live bid request se copy ki gayi schain validate kar sakta hai?

Haan. Use Validate mode mein JSON object (ek wrapping source.ext.schain samet) ya serialized string ke roop mein paste karein, aur tool required node fields, complete flag, ver check karta hai, aur hop chain draw karta hai.

schain Builder aur Validator

OpenRTB ke liye IAB SupplyChain object (schain) banayein aur validate karein, aur source.ext.schain JSON aur serialized string dono export karein — sab aapke browser mein.

schain Builder aur Validator poori tarah aapke browser mein chalta hai. Jo seller ids, domains, aur supply chain nodes aap build ya paste karte hain woh aapke device par rehte hain aur kabhi ArrayKit ko upload nahi hote.

OpenRTB Enum Reference kholein

schain Builder ke baare mein

schain Builder aur Validator us IAB Tech Lab SupplyChain object ko assemble karta hai jo OpenRTB bid requests mein source.ext.schain par ride karta hai. Har intermediary ko ek ordered node ke roop mein uske asi, sid, aur hp (payment) flag ke saath add karein, complete aur ver values set karein, phir JSON object aur URL-encoded serialized string dono copy karein jo exchanges expect karte hain. Ek maujood schain paste karne ke liye Validate mode par switch karein — JSON ya ek serialized string ke roop mein — aur turant dekhein missing required fields, ek bad complete flag, ya ek unexpected version, hop chain node by node draw hoti hui. Ad-ops, SSP, aur header-bidding engineers supply paths yahin audit aur repair kar sakte hain; jo nodes aur seller ids aap paste karte hain woh aapke device par parse hote hain aur kabhi upload nahi hote.

Features

Ordered supply chain nodes (asi, sid, hp, rid, name, domain) add, reorder, aur remove karein
complete flag toggle karein aur ver ko current 1.0 spec par pin karein
OpenRTB source.ext.schain JSON object export karta hai jo ek bid request mein daalne ke liye ready hai
URL-encoded serialized string generate karta hai jo exchanges accept karte hain (ver,complete!node!node)
Validate mode ek JSON schain ya ek serialized string dono accept karta hai
Missing asi, sid, ya hp, ek invalid complete flag, aur ek unexpected ver flag karta hai
Hop chain visualize karta hai taaki aap ek nazar mein node order confirm kar sakein
Poori tarah aapke browser mein chalta hai — seller ids aur domains aapke device par rehte hain

schain Builder kaise use karein

Build tab selected rakhein aur har node ke liye asi, sid, aur hp flag bharein
Aur nodes add karein aur unhe publisher-to-exchange order mein rakhne ke liye arrows use karein
complete flag set karein (1 jab poora path declared ho) aur JSON ya serialized string copy karein
Validate par switch karein aur required fields aur node order check karne ke liye ek maujood schain paste karein

Example

Input

asi: exchange1.com
sid: 1234
hp: 1
complete: 1

Output

1.0,1!exchange1.com,1234,1

Ek node ver,complete!asi,sid,hp mein serialize hota hai; JSON source.ext.schain mein jaata hai.

Common errors aur troubleshooting

Validate report karta hai ki ek node mein asi, sid, ya hp missing hai. — Har node ko teenon required fields chahiye: asi advertising system ka canonical domain hai, sid us system se seller/reseller id hai, aur hp 0 ya 1 hona chahiye.
Exchange serialized string ko reject karta hai. — Fields URL-encoded aur asi,sid,hp,rid,name,domain order mein hone chahiye, fields ke beech commas aur nodes ke beech ! ke saath; header segment ver,complete hai.
complete 1 set hai lekin aapne ek upstream reseller drop kar diya. — complete=1 assert karta hai ki har intermediary declared hai. Agar koi hop unknown hai, toh complete=0 set karein taaki downstream bidders jaanein ki path partial hai.
sid sellers.json ke seller id se match nahi karta. — Har node par sid us seller_id ke barabar hona chahiye jo corresponding system apni sellers.json mein publish karta hai, warna buyers path ko unverified maanenge.

Aksar pooche jaane wale sawaal

schain (SupplyChain) object kya hai?: Yeh ek IAB Tech Lab object hai jo OpenRTB mein source.ext.schain par carry hota hai aur order mein har us advertising system ko list karta hai jisne publisher aur exchange ke beech bid request ko touch kiya, taaki buyers supply path verify kar sakein.
Har node par asi, sid, aur hp ka kya matlab hai?: asi advertising system ka canonical domain hai, sid us system ke andar seller ya reseller account id hai (uski sellers.json se matching), aur hp 1 hai jab woh node payment flow mein involved ho. Teenon per node required hain.
JSON object aur serialized string mein kya farak hai?: JSON object poora source.ext.schain structure hai jo ek bid request body mein use hota hai. Serialized string ek compact URL-encoded form hai — ver,complete!node!node — jahan har node asi,sid,hp,rid,name,domain hai, wahan use hota hai jahan ek header ya query parameter chahiye.
complete 0 versus 1 kab hona chahiye?: complete=1 sirf tab set karein jab publisher se aage har intermediary nodes array mein declared ho. Agar koi upstream hop unknown ya omitted hai, toh complete=0 set karein taaki bidders jaanein ki chain incomplete hai.
Kya yeh tool mera ad tag ya bid request ek server se fetch karta hai?: Nahi. Aap schain paste ya build karte hain aur sab kuch — serialization, parsing, aur validation — aapke browser mein locally hota hai. Jo seller ids, domains, aur node data aap enter karte hain woh kabhi ArrayKit ko nahi bheje jaate.
Kya yeh ek live bid request se copy ki gayi schain validate kar sakta hai?: Haan. Use Validate mode mein JSON object (ek wrapping source.ext.schain samet) ya serialized string ke roop mein paste karein, aur tool required node fields, complete flag, ver check karta hai, aur hop chain draw karta hai.

Related tools

sellers.json Validator — Ek sellers.json document ko IAB Tech Lab spec ke against validate karein.
ads.txt Validator — ads.txt ya app-ads.txt ko line by line browser mein validate karein.
OpenRTB Bid Request Generator — Ek form se spec-valid OpenRTB 2.5 ya 2.6 bid request JSON banayein.
OpenRTB Enum Reference — Har OpenRTB 2.x enumerated list — code aur matlab — search karein.
Prebid Ad Unit Generator — Ek Prebid.js ad unit config aur pbjs.addAdUnits() snippet banayein.
TCF Consent Decoder — Ek IAB TCF v2.2 consent string decode karke CMP, purpose aur vendor grids dekhein.