Playable Ad Network Specifications: A Maintained Production Matrix

Use this matrix as a research starting point

Requirements can change by network, product, placement, account, and upload path. This table records what the linked public source supported on 19 September 2026. Re-open the official page and use the current account upload or preview tool before delivery.

Unity details that affect implementation

Unity's current playable asset specification says the creative is one inlined and minified index.html under 5 MB, requires MRAID 3.0, should support portrait and landscape, should not need XHR, should use mraid.open for the app-store CTA, must not redirect automatically, and should wait for viewableChange. Those requirements belong to this Unity product and should not be generalized to every network.

Google is a different packaging route

Google's uploaded display ad example creates a media-bundle asset from an HTML5 ZIP and associates it with an HTML5 upload ad. Google's eligibility page also lists account conditions for uploaded HTML5 ads. That is enough to establish that ‘one universal HTML file’ is not a safe cross-network packaging rule.

MRAID is an interface, not a universal acceptance certificate

The IAB Tech Lab MRAID page describes MRAID as the common API used by mobile rich-media ads to communicate with host apps. A creative can use MRAID correctly and still fail a network-specific package, policy, weight, lifecycle, or account rule.

Validation workflow

1. Name the exact network, product, placement, account, language, and orientation in the brief.
2. Open the current official specification and record its URL and checked date.
3. Package from the accepted master or variant without unrecorded creative changes.
4. Run static package checks, then behavioral checks in the closest available harness.
5. Use the current network upload, validator, preview, or test environment when access is available.
6. Attach a QA receipt to the exact package and label unknown or account-specific checks.

Common rejection risks

• Wrong entry point or archive shape.
• File weight over the current limit.
• Remote assets or network calls not allowed by the target.
• CTA opens outside the required host API or fires without user action.
• Creative starts before the host says it is viewable.
• Orientation, viewport, safe-area, or close-button collisions.
• A package tested locally but not in the destination's current tool.

Change log

19 September 2026: rebuilt the matrix from the linked Unity, Google, IAB Tech Lab, and Meta public sources. Exact limits are stated only where the public source supports them. Meta and unspecified networks remain marked for live account verification rather than filled with copied third-party numbers.