VAST-3.0-bitrate-conflict
<MediaFile> has both bitrate and minBitrate/maxBitrate
WarningValuesIAB VAST 3.0 §2.4.1VAST 3.0, 4.0, 4.1, 4.2, and 4.3
Providing both `bitrate` (a fixed value) and `minBitrate`/`maxBitrate` (a range) on the same `<MediaFile>` is contradictory. Use one or the other.
How to fix
Remove either bitrate (fixed value) or the minBitrate/maxBitrate pair from <MediaFile> — they are mutually exclusive.
Check your VAST tag for
VAST-3.0-bitrate-conflict and other issues instantly.Validate a tag →Other Values rules
VAST-2.0-duration-format<Duration> value does not match HH:MM:SS[.mmm] formatVAST-2.0-mediafile-delivery-enum<MediaFile> delivery must be "progressive" or "streaming"VAST-3.0-skipoffset-formatLinear skipoffset does not match HH:MM:SS[.mmm] or n% formatVAST-3.0-progress-offset-formatTracking progress offset does not match required formatVAST-3.0-skip-event-no-skipoffsetskip tracking event present but Linear has no skipoffset attributeVAST-3.0-minmaxbitrate-pair<MediaFile> must have both minBitrate and maxBitrate or neitherVAST-4.0-tracking-event-removedfullscreen/exitFullscreen tracking events were removed in VAST 4.0VAST-4.1-tracking-event-valueTracking event attribute not in the valid set for this VAST version