IronSource, AppLovin, and Mintegral all support playable ads and interactive end cards as self-contained HTML. Delivering the right format, size, and tracking for each network avoids rejection and keeps your UA campaigns running. This guide walks through what the three networks expect and how to export once and upload with confidence.
Common Requirements
All three typically want a single HTML file; all major networks support up to 5 MB per creative. Assets must be embedded—no hot-linked images, external CSS, or third-party scripts. The creative should detect the user’s device and open the correct App Store or Google Play URL when they tap the CTA. If any asset fails to load offline, the creative may be rejected in automated checks.
IronSource, AppLovin, and Mintegral each have their own dashboard and upload flow. You attach the HTML when creating or editing a playable or interactive end card placement. The underlying file format is the same; differences are usually limited to network-specific measurement snippets or wrappers that a good export tool applies for you.
Per-Network Notes
IronSource and AppLovin are widely used for mobile game user acquisition worldwide. Mintegral is especially strong in certain APAC and global programmatic mixes. All support playable and interactive end card formats for app install campaigns. Always pick the exact network in your export tool so the output matches that partner’s template and tracking expectations.
Upload Workflow in Each Dashboard
After export, log in to the network where the campaign will run. Navigate to creatives or playable assets for your app, upload the HTML, and wait for validation. Use clear internal names (e.g. game title + date + network) so UA teams can find the right file later. If validation fails, read the error message: it is usually file size, a blocked external request, or a broken CTA link.
Exporting With a Playable End Card Maker
Use a playable end card maker that lists IronSource, AppLovin, and Mintegral in its export options. Design your end card or playable once—background, copy, CTA, optional animation—then export once per network. The tool should inject any network-specific tracking or wrappers and output one HTML file per destination. Upload each file in the corresponding dashboard; you do not need to hand-edit HTML for basic campaigns.
Testing Before You Scale Spend
Before you attach a high budget, open the exported HTML on real iOS and Android devices. Confirm the CTA opens the correct store listing, images render, and load time feels acceptable on mobile data. Small fixes at this stage are cheaper than pausing a live campaign after poor performance or policy flags.
Create playable end cards in minutes—no code required.
Open Playable End Card Maker