MRAID requirements
MRAID (Mobile Rich Media Ad Interface Definitions) is the industry standard protocol API for mobile rich media ads running in mobile apps. MRAID is injected by the ironSource 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. ironSource Ads also supports MRAID 2.0 protocol.
MRAID related requirements
- Your MRAID file should not have any reference of the “DAPI initialization script” (see here for example) or DAPI in general as it may disrupt upload process.
- Avoid accessing the top window object (it may cause an error) All URLs within the creative should be secured
- Correct: HTTPS://
- Wrong: HTTP://
- Creatives should be contained in a single HTML index file, with no links to other files or folders
- Ads are required to wait for the MRAID ready, stateChange events before starting playable content
- To redirect a user on click, methods mraid.open(URL_STRING) or mraid.openStoreURL() should be used
- The most recommended way to request mraid.js in MRAID ads is to directly include the <script src=”mraid.js”></script> tag within the <head> section of the HTML file.
This ensures the mraid.js script is requested as early as possible during the loading of your ad creative.