IronSource, AppLovin, and Mintegral all support playable ads and interactive end cards. Delivering the right format and size for each network avoids rejection and improves performance. Here’s how to export playable ads for these networks.
Common Requirements
All three typically want a single HTML file; all ad networks support up to 5 MB. Assets must be embedded; no external resources. The creative should detect device and send users to the correct app store when they tap the CTA.
IronSource, AppLovin, and Mintegral each have their own dashboard and upload flow. You upload the HTML file when creating or editing the playable creative in that network. The format is the same; only the upload destination and any network-specific tracking differ.
Per-Network Notes
IronSource and AppLovin are widely used for mobile game UA. Mintegral is popular in certain regions. All support playable and interactive end card formats. Use a playable end card maker that lists these networks in its export options so you get the correct output for each.
Exporting With a Playable End Card Maker
Use a playable end card maker that lists IronSource, AppLovin, and Mintegral in its export options. Design once, then export once per network. The tool should add any network-specific tracking or wrappers and output a single HTML file per network. Upload each file in the corresponding network’s dashboard.
Create playable end cards in minutes—no code required.
Open Playable End Card Maker