Documentation

​
​

Development

User Acquisition

Monetization

Industry

Unity Ads User Acquisition

Advertising Management API

Advertising Statistics API

Open User Acquisition dashboard

Unity Ads User Acquisition

Unity Ads User Acquisition
​
​
Creative packs setup
  • Creative packs
  • Introduction to creative packs
  • Making creative packs
  • Preview creative packs with the Ad Testing app
Creative moderation
  • Creative pack moderation
  • Introduction to creative moderation
  • Creative moderation checks
  • Check your moderation status
  • Moderation status references
Creative assets
  • Creative types
  • Video ad creatives
  • Playable ad creatives
    • Playable asset specifications
    • Playable ad best practices
  • End card ad creatives
  • Product pages
  1. Grow your game
  3. Unity Ads User Acquisition
  5. Creative packs setup

Playable asset specifications

Review the required asset specifications for Playable ads with Unity Ads User Acquisition.
Read time 2 minutes
Last updated a year ago
Playable ads allow users to play a quick interactive demo of your game. Playable creatives must be:
  • Contained in a single HTML index file (
    index.html
    ), with no links to other files or folders.
  • An inlined, minified file (optimized for machine-reading by removing empty spaces).
  • Under 5 MB.
  • Compliant with the Mobile Rich Media Ad Interface Definitions (MRAID) 3.0 specifications.
In addition, Unity requires the following specifications outside of MRAID:
  • Advertisements must be contained in a single HTML file, with all assets inlined.
  • Android games must use Android version 4.4 or higher.
  • iOS games must use iOS version 9.0 or higher.
  • Ads must not block the close button or any other container UI elements in a way that prevents users from closing the ad.
  • Ads should support both portrait and landscape orientations.
  • Ads should not need any network requests (XHR), but analytic calls to collect player interaction data may be permitted if they do not contain personal data (such as user or device identifiers) and otherwise comply with all applicable laws and platform policies.
  • Ads should not automatically (for instance, without explicit user action or a call-to-action) redirect to the app store.
  • Ad call-to-actions should link directly to the app store using mraid.open.
  • Ads should wait for the MRAID 
    viewableChange
    event before starting playable content.

Introduction to MRAID

MRAID (Mobile Rich Media Ad Interface Definitions) is the common API for mobile rich media ads running in mobile apps. MRAID is injected by the Unity Ads webview, so you can use MRAID methods detailed in the guidelines. To learn more, review the IAB's documentation for detailed information on MRAID 3.0 methods, best practices, and standards.
Copyright © 2026 Unity Technologies
LegalPrivacy PolicyCookiesDocumentation Terms of UseDo Not Sell or Share My Personal InformationYour Privacy Choices (Cookie Settings)

"Unity", Unity logos, and other Unity trademarks are trademarks or registered trademarks of Unity Technologies or its affiliates in the U.S and elsewhere (more info here). Other names or brands are trademarks of their respective owners.

Some pages are machine-translated for convenience, and may contain inaccuracies. In the event of conflicting information, the English version is authoritative.

  • On this page

    • Introduction to MRAID

Report a problem with this page