VAST-3.0-minmaxbitrate-pair
VAST-3.0-minmaxbitrate-pair
<MediaFile> must have both minBitrate and maxBitrate or neither
ErrorValuesIAB VAST 3.0 §2.4.1VAST 3.0, 4.0, 4.1, 4.2, and 4.3
Short answer
minBitrate and maxBitrate must be used together. Specifying one without the other leaves the range undefined.
Why this matters in production
This rule is usually a delivery blocker. Many players, SDKs, and ad servers will discard the response or skip the affected creative once this condition is hit. Value-format rules tend to fail at the moment a player interprets a field such as duration, skipoffset, bitrate, or versioning. They are especially painful because the XML can look valid at a glance. Affected scope: VAST 3.0, 4.0, 4.1, 4.2, and 4.3.
How to fix
Either provide both minBitrate and maxBitrate, or use the single bitrate attribute — not a mix of the two.
Check your VAST tag for
VAST-3.0-minmaxbitrate-pair and other issues instantly.Open the VAST tag validator →Other Values rules
VAST-4.1-expires-integer<Expires> value must be an integer number of secondsVAST-4.0-category-authority-not-uri<Category> authority attribute is not a valid authority URLVAST-4.0-category-authority-unknown<Category> authority is not a recognised IAB Content Taxonomy authorityVAST-4.1-blockedadcategories-authority-not-uri<BlockedAdCategories> authority attribute is not a valid authority URLVAST-4.1-blockedadcategories-authority-unknown<BlockedAdCategories> authority is not a recognised IAB Content Taxonomy authorityVAST-4.1-verification-vendor-format<Verification> vendor should use a domain-qualified identifier such as company.com-omidVAST-4.1-verification-tracking-reasonverificationNotExecuted tracking URI should include the [REASON] macroVAST-2.0-duration-format<Duration> value does not match HH:MM:SS[.mmm] format