How to upload an HTML5 ZIP to Google Ads (without failing policy)

PlayableRun exports a single ZIP your UA team can attach to Google Ads. This guide is original PlayableRun documentation. It does not copy Google’s help text; we cite the official articles so you can verify the platform rules. ## What must be in the ZIP Your package should unpack with index.html at the root (not inside a nested folder). PlayableRun also writes style.css plus assets/*.webp. That layout matches how HTML5 ads are typically uploaded as a self-contained bundle. Keep the archive under 5MB. We convert icons and screenshots to WebP at max 512px so the creative stays inside that budget. ## App Campaign vs Display - App campaigns use Google’s Exit API. The creative loads exitapi.js from Google’s syndication host and calls ExitApi.exit() when the user taps Install. Do not use window.open on this path. - Display HTML5 ads use a clickTag variable and window.open(window.clickTag) for the destination. Mixing those two patterns is the fastest way to fail a QA checklist. PlayableRun’s generator is locked to one campaign type per ZIP. ## What we never put in the file External CDNs, Google Fonts links, and Base64 images inflate size and violate the “self-contained HTML5” expectation. Fake system alerts or invisible close buttons are policy risks — our validator rejects them before you download. ## How to use it in Ads 1. Generate the ZIP in the PlayableRun workspace. 2. In Google Ads, create or edit the campaign that matches the ZIP (App vs Display). 3. Upload the HTML5 asset where the UI asks for an HTML5 bundle. 4. Confirm the preview click-through matches ExitApi or clickTag. For platform-specific UI labels and eligibility, always read Google’s current Help article rather than screenshots from a third-party blog. ## Sources - About HTML5 ads - About App campaigns