List of all Ad Validation tests - AdMeIn
Explore our ad validation tests designed to ensure your video ad tags comply with industry standards and function seamlessly across platforms
Ad Validation Tests
Below is a comprehensive list of all ad validation tests available on AdMeIn. These tests help ensure that your video ad tags comply with industry standards and function correctly across various platforms and devices.
For more detailed information on each test and how to interpret the results, please refer to our Help Center.
VAST Video Tag Testing
VAST Version
Checks if the VAST version is supported and valid.We currently support all versions of VAST: 2.0, 3.0, 4.0, 4.1, 4.2
Why we test this:
Different VAST versions introduce new elements and deprecate old ones. Testing ensures the XML structure and features align with the supported version, preventing compatibility issues with players and ad servers.
Media Files
Ensures media files are present and properly formatted.We support various media file types including MP4, WebM, and Ogg.
Why we test this:
Media files are the core of any video ad. Testing ensures the file type, codec, bitrate, and delivery method meet player compatibility standards, preventing playback errors and poor viewing experiences.
Ad Duration
Validates that the ad duration is specified and reasonable.We recommend a duration of 15–30 seconds for most ads.
Why we test this:
A defined duration helps players allocate correct playback time and manage ad pods efficiently. Missing or invalid durations can cause playback interruptions or failed ad requests.
Tracking Events
Checks for required tracking events and their correctness.We support various tracking events including start, firstQuartile, midpoint, and complete.
Why we test this:
Tracking events provide essential performance metrics such as completion rate and viewer engagement. Missing or incorrect events lead to inaccurate analytics and reporting discrepancies.
Click Tracking
Verifies click tracking URLs are present.Click tracking is essential for measuring ad engagement.
Why we test this:
Click tracking URLs record user interactions with the ad. Without proper click tracking, advertisers lose insight into engagement and campaign effectiveness, affecting billing and performance analysis.
Impression Tracking
Ensures impression tracking is implemented.Impression tracking helps monitor ad views and performance.
Why we test this:
Impression tracking confirms when an ad has been served and viewed. It’s a critical metric for verifying delivery, preventing fraud, and ensuring accurate reporting to advertisers and publishers.
Companion Ads
Checks for valid companion ads if present.Companion ads enhance user engagement alongside video ads.
Why we test this:
Companion ads extend the ad experience across formats and screens. Testing ensures they are correctly linked and formatted, avoiding display issues and maintaining creative consistency.
Ad System
Validates the AdSystem element.AdSystem identifies the ad server or system that provided the ad.
Why we test this:
The AdSystem element provides transparency about the ad’s origin and helps with troubleshooting, analytics, and attribution across ad delivery chains.
API Framework
Checks for correct API framework usage.Common API frameworks include VPAID and SIMID.
Why we test this:
The API framework defines how the creative interacts with the player. Testing ensures compatibility with supported frameworks, avoiding execution failures or blocked interactions on CTV and desktop environments.
Ad Sequence
Validates ad pod sequence numbers (for sequential ads).Ensures ad sequence numbers are unique and properly ordered.
Why we test this:
Ad sequence testing guarantees that ads play in the intended order within a pod, ensuring storytelling, pacing, and compliance with campaign delivery requirements.
Sequence Timing
Checks total duration and timing of ad pods.Ensures total ad pod duration is within acceptable limits.
Why we test this:
Proper sequence timing maintains a smooth viewing experience. Overly long or poorly timed ad pods can cause user drop-off, violate publisher limits, or fail ad insertion rules.
VMAP Version
Checks VMAP version (for VMAP tags).We currently support VMAP 1.0.
Why we test this:
VMAP defines how ad breaks are scheduled in long-form content. Testing ensures compliance with supported VMAP standards, preventing scheduling conflicts or playback errors in ad stitching systems.
Ad Breaks
Validates ad breaks in VMAP.Ensures ad breaks are properly defined and formatted.
Why we test this:
Ad breaks determine when and how ads appear during content playback. Validating them ensures correct structure, preventing missing mid-rolls or misaligned ad placements.
Ad Break Timing
Checks timing of ad breaks in VMAP.Ad breaks should be scheduled at appropriate intervals.
Why we test this:
Properly timed ad breaks maintain viewer engagement and balance monetization with user experience. Poorly spaced breaks can lead to audience frustration or reduced ad revenue.
VAST References
Ensures VMAP ad breaks reference valid VAST tags.We currently support VAST 2.0, 3.0, and 4.0+
Why we test this:
Each ad break in a VMAP should point to a valid VAST tag. Testing ensures referenced VAST URLs are accessible and well-formed, avoiding empty breaks or failed ad requests during playback.
HTML5 Ad Tag Validation
Common Ad Tag Issues
Analyzes the ad tag for common code issues before running a full analysis.
What is analyzed
This analysis checks for common issues found in the ad tag code, like missing or malformed elements, double quotes, unclosed tags, and other common mistakes that can lead to ad serving problems.
Resource Load Weight
Analyzes the total weight of all resources loaded by the ad tag to ensure it doesn't negatively impact ad performance.
What is analyzed
Heavy ads can lead to slower load times and a poor user experience. This analysis checks the total size of all resources loaded when the ad serves, including images, scripts, and other assets. Keeping resource load weight within recommended limits helps ensure optimal ad performance across various devices and network conditions.
HTTP Call Limit
Checks if the number of HTTP calls made by the ad tag exceeds the allowed maximum (100). This includes all external trackers and resources loaded by the ad.
What is analyzed
A maximum of 100 HTTP calls is allowed per ad, including external trackers and resources. Confirm with advertiser and media company/publisher's ad server. Dynamic loading, iframes, redirects, or third-party content may increase the total HTTP call count.
File Size
Checks if the total file size of all assets loaded by the ad tag exceeds the allowed maximum (4MB).
What is analyzed
Google Ads recommends keeping the total file size under 150KB for optimal performance when display ads are not video. Exceeding file size limits can or will cause Chrome heavy ad intervention to trigger. The total file size includes all resources loaded when the ad serves, not just the initial HTML. Some publishers may require a smaller file size—always check publisher specifications. Keeping file size within limits ensures faster load times and better user experience.
ClickTag Presence
Checks for the presence and value of the clickTag variable in the ad tag. Ensures the clickTag is not minified and is easily readable by the ad server.
What is analyzed
HTML5 display ads must use click tags to direct users to a landing page. The clickTag must be easily readable by the ad server—do not minify the clickTag code. The landing page must open in a new tab or window upon click. Some ad tags may use alternative methods for handling click-through URLs, but clickTag is the standard.
Autoplay Audio
Checks if the ad tag attempts to autoplay audio or video with sound.
What is analyzed
Audio autoplay is typically prohibited. Video autoplay is allowed, but the audio must remain muted by default. If no audio or video resources are detected, this analysis will be skipped. Always check publisher creative specs for exceptions.
Popup
Checks if the ad tag attempts to open popups or spawn additional windows.
What is analyzed
Pop-up ads and surveys are prohibited. Ads must not spawn additional windows or overlay content that disrupts the user experience.
Ad Tag Errors
The Ad tag is analysed for common errors during execution.
What is analyzed
This analysis checks for common errors that may occur like copying tags from CSV files, double quotes, unclosed tags, and other mistakes that can lead to ad serving problems.
Creative ZIP File Validation
Entry HTML Present
Validates that a valid entry HTML file exists
What is analyzed
Verifies the creative has a primary HTML file that serves as the entry point. Ad servers need to know which HTML file to load first. The system looks for 'index.html' first, then falls back to a single .html file, or the first alphabetically.
Creative Dimensions
Detects creative dimensions from HTML markup
What is analyzed
Attempts to detect the creative's width and height by scanning HTML attributes (width="300"), inline styles (style="width: 300px"), CSS rules, aspect-ratio properties, and JavaScript object literals. Knowing the dimensions helps with trafficking and ensures proper rendering.
ZIP Total Size
Validates that the total ZIP file size is within acceptable limits
What is analyzed
Validates the total uncompressed size of all files in the creative. Large file sizes can impact load times and may exceed ad platform serving limits. Most platforms recommend keeping creatives under 5-10 MB.
ZIP File Count
Validates that the ZIP contains a reasonable number of files
What is analyzed
Checks the number of files in the creative package. An excessive number of files can slow down processing, increase load times, and may indicate poor organization or unnecessary assets.
Individual File Size
Validates that individual files are not excessively large
What is analyzed
Validates that no single file is excessively large. Large individual files (especially images or videos) can cause significant performance issues and may fail to load on slower connections. Consider optimizing or compressing large assets.
Compression Ratio
Validates compression ratio to detect potential zip bombs
What is analyzed
Detects potential zip bombs by analyzing the compression ratio. A zip bomb is a malicious archive that expands to an enormous size when decompressed, potentially exhausting system resources. Normal compression ratios are typically under 10:1.
File Extensions
Validates that all files have allowed extensions
What is analyzed
Checks that all files use standard web-safe file extensions. Ad platforms typically only support common web formats (HTML, CSS, JS, images, fonts, video). Unsupported file types may be rejected or fail to load properly.
Directory Structure
Validates that directory structure is not excessively nested
What is analyzed
Validates directory structure complexity. Deeply nested folders can cause path length issues on some platforms, complicate maintenance, and indicate poor organization. Keep your creative structure simple and flat when possible.
File Naming
Validates file naming conventions (no spaces, special characters)
What is analyzed
Ensures file names use only web-safe characters (alphanumeric, hyphens, underscores). Spaces and special characters in file names can cause issues with URL encoding, server configurations, and cross-platform compatibility.
Image Assets
Validates image asset usage and sizing
What is analyzed
Provides an inventory of image assets and their total size. Images are often the largest assets in display ads. Consider using modern formats (WebP), appropriate compression, and serving different sizes for different screens to optimize performance.
Script Assets
Validates JavaScript asset inventory
What is analyzed
Catalogs JavaScript files and their combined size. JavaScript is executed by the browser and can impact ad performance. Large or numerous script files may slow down ad rendering and user interaction.
Stylesheet Assets
Validates stylesheet asset inventory
What is analyzed
Lists CSS files and their total size. Stylesheets control the visual presentation of your ad. Multiple or large CSS files can delay rendering as browsers must download and parse them before displaying content.
Video Assets
Validates video asset sizing
What is analyzed
Checks video file sizes. Video ads are typically the largest assets and require careful optimization. Large video files consume significant bandwidth and may not load on slower connections. Consider using streaming or external hosting for large videos.
HTML Validity
Validates basic HTML structure and syntax
What is analyzed
Performs basic HTML validation checks including proper tag structure, required elements (html, head, body), and common syntax errors. Valid HTML ensures consistent rendering across different browsers and ad platforms.
HTML Meta Tags
Validates presence of important meta tags
What is analyzed
Checks for essential meta tags like charset (UTF-8) and viewport settings. These tags ensure proper character encoding and responsive behavior across different devices and screen sizes.
Inline Script Size
Validates inline script size limits
What is analyzed
Checks the total size of inline JavaScript code embedded directly in HTML. Large inline scripts can slow down page parsing and should generally be moved to external files for better caching and performance.
External Resources
Inventories external resource dependencies
What is analyzed
Identifies all external resources (URLs) referenced in the creative. External dependencies create additional network requests and potential points of failure. Each external resource should be evaluated for necessity and performance impact.
JavaScript Minification
Checks if JavaScript files appear to be minified
What is analyzed
Detects whether JavaScript files are minified by analyzing line length patterns. Minification removes whitespace, comments, and shortens variable names, significantly reducing file size. Unminified code wastes bandwidth and exposes your implementation details.
JavaScript Console Statements
Detects console.log and debug statements
What is analyzed
Scans for console.log, console.debug, and similar debugging statements. These should be removed from production code as they can leak information, impact performance, and create unnecessary browser console noise. Use a build process to strip debug code.
JavaScript Strict Mode
Checks if JavaScript uses strict mode
What is analyzed
Checks for 'use strict' directive in JavaScript files. Strict mode catches common coding errors, prevents unsafe actions, and disables confusing features. It's a best practice that helps avoid bugs and makes code more maintainable.
JavaScript Error Handling
Checks for error handling patterns
What is analyzed
Looks for try-catch error handling blocks in JavaScript. Proper error handling prevents your ad from breaking when unexpected conditions occur, provides graceful degradation, and helps with debugging issues in production.
ClickTag
Validates clickTag implementation for ad serving
What is analyzed
Validates presence of clickTag implementation. ClickTags allow ad servers to dynamically insert destination URLs without modifying the creative file. This is essential for trafficking the same creative to multiple destinations and is required by most ad platforms.
OMID
Validates OMID (Open Measurement) implementation
What is analyzed
Checks for Open Measurement SDK (OMID/OMSDK) implementation. OMID is an IAB standard that enables consistent viewability and verification measurement across different vendors. Many premium publishers and DSPs require or prefer OMID-compliant creatives.
Vendor Restrictions
Validates restricted vendor compliance
What is analyzed
Validates compliance with vendor restrictions. Some platforms and publishers block specific third-party vendors due to privacy policies, competitive restrictions, or performance concerns. Using restricted vendors will cause your ad to be rejected.
Third Party Scripts
Validates third-party script usage
What is analyzed
Catalogs external JavaScript resources loaded from third-party domains. Each external script adds a network request and potential point of failure. Excessive third-party scripts can slow down your ad, create security risks, and may be restricted by ad platforms.
Ad Tag Examples & Testing
Explore our collection of ad tag examples that you can test directly in the Ad Tag Tester. These examples include HTML5 display ads, JavaScript tags, VAST Tags, and other common ad formats.
Ad Tag Example Gallery
Browse examples of HTML5, display, JavaScript, and rich media ad tags with working code samples.
Video Asset Validation Testing
Video Duration Test
Test video duration to ensure it meets industry standards and delivers optimal performance across platforms.
Video duration is a critical factor in ad effectiveness. Different ad formats and platforms have varying optimal duration ranges to maximize viewer engagement.
Why we test this:
Video Duration test analysis value is total length of the video in seconds. For video ads, it is recommended to keep the duration between 3 to 60 seconds to maintain viewer engagement, where longer videos may lead to higher abandonment rates. For display ads, shorter durations of 15 to 30 seconds are often more effective. Display video ads exceeding 30 seconds may face heavy ad intervention.
Video Codec test
Test video codec to ensure it meets industry standards and delivers optimal performance across platforms.
Common video codecs include H.264 (AVC), H.265 (HEVC), VP8, VP9, and AV1. Using widely supported codecs ensures compatibility across various devices and platforms.
Why we test this:
Codec determines how video data is compressed and decompressed. Modern codecs like H.264 and H.265 offer better quality at lower bit rates compared to older codecs.
Video Frames Per Second test
Test video frames per second to ensure it meets industry standards and delivers optimal performance across platforms.
IAB does not mandate a specific frame rate for video ads but recommends using standard frame rates such as 23.976, 24, 25, 29.97, 30 fps to ensure compatibility across various devices and platforms.
Why we test this:
Value is how many frames per second (fps) your video plays. Standard frame rates are 23.976, 24, 25, 29.97, 30
Video Bitrate test
Test video bitrate to ensure it meets industry standards and delivers optimal performance across platforms.
Recommended bitrates vary based on ad format and resolution and frame rate. For example, a 1080p video for a CTV video ad might have a recommended bitrate range of 3,000 to 6,000 kbps, while a 720p video for a web display ad might be optimized between 1,500 to 3,000 kbps.
Why we test this:
Video Bit Rate test analysis (bitrate indicates video quality level) the higher the bit rate, the better the quality.
Video Resolution test
Test video resolution to ensure it meets industry standards and delivers optimal performance across platforms.
Common video resolutions used in advertising include 1920x1080 (Full HD), 1280x720 (HD), and 640x360 (SD). Higher resolutions provide better quality but require more bandwidth, so it is important to balance quality and performance based on the target platform and ad format.
Why we test this:
Video Resolution test analysis. Value is total pixel count (width * height).
Video File Size test
Test video file size to ensure it meets industry standards and delivers optimal performance across platforms.
There is no single IAB VAST file size standard; instead, the Interactive Advertising Bureau recommends providing multiple video files to optimize ad delivery for different connection speeds. The latest VAST 4.x specification emphasizes supplying low, medium, and high-quality options, as well as a "mezzanine" file, rather than enforcing a single file size limit.
Why we test this:
Video File Size test analysis describes the size of the video file in a human-readable format. The video file size is an important factor for ad delivery and user experience. Your video file size should be optimized to balance quality and loading times and sit within a minimum size of 500.00 KB and a maximum size of 2.00 MB for display ads and up to 10.00 MB for VAST video ads.
Video Aspect Ratio test
Accurate aspect ratios are essential for consistent visual rendering. Misaligned ratios can cause display issues, distortions, or rejections across ad delivery systems, ultimately reducing campaign effectiveness.
Common video aspect ratios include 16:9 (widescreen) and 4:3 (standard). Knowing the target platform’s requirements is crucial for optimal ad delivery.
Why we test this:
Video Aspect Ratio test analysis describes the proportional relationship between the width and height of the video. Common aspect ratios include 16:9 (widescreen) and 4:3 (standard). Using standard aspect ratios ensures compatibility across various devices and platforms, providing a better viewing experience.
Video Format test
Video File Format is the container that holds the video and metadata streams. Using a widely supported format ensures compatibility across different devices and platforms.
Best practices recommend using MP4 (with H.264 codec) for broad compatibility across web and mobile platforms. Other formats cause compatibility issues or unsupported playback issues.
Why we test this:
Video File Format test analysis checks if the video file format (e.g., MPEG-4, QuickTime) is supported for ad delivery.
Video Extension test
Test Video File Extension is the suffix at the end of a file name that indicates the file format..
Common video file extensions include .mp4, .webm, and .ogg. Using standard file extensions ensures compatibility across various devices and platforms.
Why we test this:
Video Extension test analysis checks if the video file extension (e.g., mp4, webm, ogg) is supported for ad delivery.
Video Moov Atom Location test
Test video Moov Atom location to ensure it meets industry standards and delivers optimal performance across platforms.
The MOOV atom should be located at the beginning of the file for optimal playback. This allows for faster streaming and playback start times by enabling the video player to access necessary metadata without downloading the entire file first.
Why we test this:
The MOOV atom contains important metadata for video files. It should be located at the beginning of the file for optimal playback. This allows for faster streaming and playback start times by enabling the video player to access necessary metadata without downloading the entire file first.
Video Color Space test
Video Color Space defines how colors are represented and displayed. Generally RGB (typically sRGB) is assumed, which is the standard color space for the internet and web-based content. sRGB is the de facto standard for web content, as it aligns with the broadcast standard for high-definition television (Rec. 709). The Interactive Advertising Bureau (IAB) does not mandate a universal color space standard. Instead, it provides contextual guidelines—favoring RGB (typically sRGB) for web display ads and YUV for video content. In digital video, industry standards commonly employ YUV chroma subsampling formats such as 4:2:0 or 4:2:2, with codec profiles like H.264 specifying further technical details.
Important Considerations: The specific color space and other technical requirements depend on the ad format (e.g., display vs. video) and the delivery platform (e.g., web vs. connected TV). The Interactive Advertising Bureau (IAB) does not mandate a universal color space standard. Instead, it provides contextual guidelines—favoring RGB (typically sRGB) for web display ads and YUV for video content. In digital video, industry standards commonly employ YUV chroma subsampling formats such as 4:2:0 or 4:2:2, with codec profiles like H.264 specifying further technical details.
Why we test this:
Color space defines how colors are represented and displayed. Common spaces include Rec. 709 (HD), Rec. 2020 (4K/HDR), and sRGB.
Video Scan Type test
Test video scan type to ensure it meets industry standards and delivers optimal performance across platforms.
Understanding the scan type can help optimize video content for its intended platform, ensuring the best possible viewing experience for the audience.
Why we test this:
Scan type indicates how the video frames are displayed. Progressive scan displays all lines in each frame sequentially, while interlaced scan alternates between odd and even lines. Progressive scan is preferred for online video content as it provides smoother motion and better quality on digital displays.