Playable Preview Tool
Use the tool on this page to check whether your playable will execute correctly in the AppLovin SDK.
To use this tool, do one of the following:
- Enter the URL of where your HTML playable is hosted and click Preview Playable, or
- Upload a file containing your HTML playable by dragging-and-dropping that file to the field below, or by clicking Click here to upload and selecting that file from your local file system.
Your playable will begin to execute in a simulated device screen on this page. Test your playable there to see that it behaves as expected. Click Rotate to also test your playable in the landscape orientation. When you click the call to action in your playable, this tool should display the message “You have successfully clicked.” If it does not, your playable will also not function correctly in the AppLovin SDK.
In some circumstances, a playable behaves properly when you test it on this page but fails to work correctly on real-world devices. For this reason, after you successfully test your playable on this page, you should also test it in the Playable Preview app, which better simulates the real-world environment in which your playable will execute.
Playable Preview app
Use the Playable Preview app to test whether your playable will execute correctly in the AppLovin SDK. This app is available for iOS and Android.
Upload or preview your playable by using the form on this page. This causes a QR code to appear at the bottom of the page. Then, open the Playable Preview app. Use that app to scan the QR code. Your playable then opens in the Playable Preview app. Test your playable to see that it behaves as expected. Test both in landscape and in portrait orientations. Click your playable’s call to action: if your playable is working correctly, you should see a redirect take place. Note: The actual result of the redirect can be ignored. Redirects within the Playable Preview app are only to confirm that a redirect takes place when expected.
HTML Playable Specifications
Behavioral Requirements
- File Size: Each ad must be 5 MB or smaller.
-
File Type: Each ad must be a single HTML file.
- All resources must be embedded in either base64 or base122 format; external resources are prohibited.
- Orientation Compatibility: Each ad must work in both landscape and portrait orientations.
- Ad Timer Initialization: Each ad’s timer must start only after the first user interaction.
- Interactivity: Each ad must be playable and must not redirect to app stores on the first tap/click.
- Load Time: Each ad must fully load and become interactive within a reasonable time frame.
-
No Auto-Play:
- Audio must remain muted until the first user interaction.
- Audio must stop or be muted when the ad closes or becomes hidden.
- No Auto-Click: Each ad must not auto-click or auto-redirect to app stores or other landing pages without user interaction.
-
No External Requests:
- External network calls are prohibited.
Technical Requirements
-
MRAID
- HTML ads must support MRAID v2.0.
-
Wait for the
readyevent (or confirmmraid.getState()is not'loading') before calling any MRAID APIs or making layout/sizing decisions. - Use
mraid.open()for click-through actions.
-
WebGL
- If using WebGL, provide a UI fallback if initialization fails or the context is lost.
