VAST Validator
Ek VAST tag paste karein aur use IAB VAST rules ke against apne browser mein check karein. XML kabhi aapke device se bahar nahi jaata.
VAST Validator jo tag aap paste karte hain use poori tarah aapke browser mein parse karta hai. Remote ad tags, tracking pixels aur MediaFile URLs kabhi fetch nahi hote, aur jo aap paste karte hain woh ArrayKit ko upload nahi hota.
XML Formatter kholein
VAST Validator ke baare mein
VAST Validator ek VAST (Video Ad Serving Template) tag ko parse karta hai aur use IAB VAST rules ke against check karta hai, taaki aap ek broken creative ship hone se pehle pakad sakein. Ek InLine ya Wrapper document paste karein aur yeh version detect karta hai, phir required nodes verify karta hai — AdSystem, AdTitle, Impression, Creatives aur wrappers par ek VASTAdTagURI — plus MediaFile delivery, type, width aur height aur HH:MM:SS Duration. Har issue ko errors aur warnings mein group kiya jaata hai, poore node path ke saath, isliye aapko pata chal jaata hai ki kaunsa Ad, Creative ya MediaFile fix karna hai. Yeh un ad-ops engineers, publishers aur DSP integrators ke liye bana hai jo din bhar video ad tags debug karte hain. Kuch bhi fetch ya upload nahi hota — jo tag aap paste karte hain woh poori tarah aapke browser mein parse hota hai.
Features
- <VAST version> attribute se VAST version detect karta hai (2.0 se 4.3 tak)
- Required InLine nodes check karta hai: AdSystem, AdTitle, Impression aur Creatives
- Wrapper structure aur downstream tags ke liye ek non-empty VASTAdTagURI check karta hai
- Linear creatives par delivery, type, width aur height ke saath kam se kam ek MediaFile zaroori karta hai
- Duration ko HH:MM:SS aur skipoffset ko ek time offset ya percentage ke roop mein validate karta hai
- Misplaced nodes flag karta hai, jaise InLine mein VASTAdTagURI ya Wrapper mein AdTitle
- Results ko errors aur warnings mein group karta hai, har ek exact node path ke saath tagged
- Ek ticket mein daalne ke liye plain-text report copy karein — saara parsing aapke browser mein hi rehta hai
VAST Validator kaise use karein
- Apni VAST XML (InLine ya Wrapper) box mein paste karein, ya ek sample load karein
- Top par detected version aur error / warning count padhein
- Har finding kholkar node path aur kya fix karna hai dekhein
- Apni ad-ops team ke saath results share karne ke liye report copy karein
Example
Input
<VAST version="4.0"><Ad><InLine>
<AdSystem>Server</AdSystem><AdTitle>Ad</AdTitle>
<Impression>https://ex/imp</Impression>
<Creatives><Creative><Linear>
<Duration>0:30</Duration>
</Linear></Creative></Creatives>
</InLine></Ad></VAST>
Output
VAST 4.0 — 2 error(s), 0 warning(s)
[ERROR] …Linear > Duration — Duration "0:30" is not in HH:MM:SS format
[ERROR] …Linear — InLine Linear creative must contain a <MediaFiles> element
Version 4.0 detect ho jaata hai; kharab Duration aur missing MediaFiles dono apne node paths ke saath flag ho jaate hain.
Common errors aur troubleshooting
- Duration "0:30" HH:MM:SS format mein nahi hai. — VAST Duration zero-padded HH:MM:SS hona chahiye (optionally HH:MM:SS.mmm). Ek 30-second spot ko 00:00:30 likhein, 0:30 ya 30 nahi.
- MediaFile mein required delivery / type / width / height attribute missing hai. — Har MediaFile ko delivery ("progressive" ya "streaming"), ek MIME type jaise video/mp4, aur integer width aur height pixels mein chahiye.
- Wrapper mein ek <VASTAdTagURI> hona zaroori hai. — Ek Wrapper ek downstream tag ko delegate karta hai, isliye use MediaFiles wale Creatives ke bajaye ek non-empty VASTAdTagURI chahiye (aksar CDATA mein wrapped).
- <VAST> element mein required version attribute missing hai. — Root mein version add karein, jaise <VAST version="4.0">. Iske bina parser sahi rule set nahi chun sakta aur players tag reject kar sakte hain.
Aksar pooche jaane wale sawaal
- Yeh validator kaunse VAST versions support karta hai?
- Yeh root <VAST> element par version attribute padhta hai aur VAST 2.0, 3.0, 4.0, 4.1, 4.2 aur 4.3 samajhta hai. Ek unknown version ko warning ke roop mein flag kiya jaata hai taaki aap baaki structural checks phir bhi dekh sakein.
- Kya yeh ek Wrapper ko InLine se alag validate karta hai?
- Haan. Ek InLine ad mein AdSystem, AdTitle, Impression, Creatives aur, ek Linear creative ke liye, ek Duration aur kam se kam ek MediaFile hona chahiye. Ek Wrapper ko iske bajaye ek non-empty VASTAdTagURI chahiye aur MediaFiles ki zaroorat nahi, isliye dono alag rules se check hote hain.
- Mera MediaFile flag kyun hota hai jab ad kuch players mein phir bhi chalta hai?
- Lenient players defaults par fall back karte hain, lekin IAB spec har MediaFile par delivery, type, width aur height zaroori karta hai. Validator tag ko spec ke standard par rakhta hai taaki yeh strict SSPs aur players ke across chale, sirf us ek par nahi jise aapne test kiya.
- VAST kaunsa Duration format expect karta hai?
- Ek zero-padded HH:MM:SS value, optionally milliseconds ke saath HH:MM:SS.mmm. Toh 00:00:15 valid hai lekin 0:15, 15 ya 00:15 nahi. skipoffset attribute iske bajaye ek percentage jaise 25% ho sakta hai.
- Kya yeh ek VASTAdTagURI follow karke wrapped tag validate kar sakta hai?
- Nahi — validator kabhi remote URLs fetch nahi karta. Yeh check karta hai ki VASTAdTagURI present aur non-empty hai, lekin downstream response inspect karne ke liye aap woh VAST XML alag se paste karke use apne aap validate karein.
- Kya validator mera VAST tag fetch ya upload karta hai?
- Dono nahi. Jo XML aap paste karte hain woh aapke device par parse hota hai, aur remote ad tags, trackers aur MediaFile URLs kabhi request nahi hote. Tag ke baare mein kuch bhi ArrayKit ya kisi ad server ko nahi bheja jaata.
Related tools
Saare ArrayKit tools