
Playable Ads
Part of Playable advertising
Testing loading time for a playable creative
A playable that takes too long to become usable can lose a viewer before its idea appears. Test time to first visible instruction and first responsive action, not …
What you're actually timing in a playable
Time the gap between the ad being requested and the first interaction that actually registers: a tap, swipe or drag the creative responds to. Download completion is an earlier milestone, and stopping the clock there understates how long the user waited.
Google Ads counts an engagement when a user first interacts with, or clicks, an HTML5/Playable ad. A slow start shifts the moment that engagement is recorded, not just the visual.
Between request and first touch sit several layers: total bundle weight, unzipping and parsing the .ZIP, decoding images and audio, the first render, and the delay before the first touch is accepted.
Name the layer each measurement covers so two builds are compared on the same basis — a download figure and a first-interaction figure are not interchangeable.
Shrink the bundle before you stopwatch anything
Google Ads accepts .ZIP uploads of up to 5 MB containing no more than 512 files. In the interstitial dimensions 320x480 and 480x320, assets can be up to 5.2 MB; anything larger is rejected immediately.
A file sitting close to the limit can still cause problems, so trim it a little rather than shaving a few bytes. Unity's specification check puts the initial file size under 6 MB.
Count the files and confirm only supported types are inside. The accepted set covers HTML, CSS, JavaScript and image formats such as PNG, JPEG and GIF; unsupported files must be removed or replaced.
Check that code is correctly minified rather than left expanded, and that non-ASCII characters use UTF-8.
Choosing devices, networks and orientations to test on
Set a support floor and test at it. Unity's specification checks require content to function on iOS 8 or greater and Android 4.4 or greater, with no polyfill issues on older Android versions.
Test both portrait and landscape. Set orientation explicitly: if no meta tag is used, or the orientation value is wrong, the asset is not rejected at upload but renders only in portrait.
Playables render full screen across a range of display sizes and must scale to the device screen, so include a small handset and a large one, in each orientation.
Throttle the connection and simulate dropouts. Timing taken on office wi-fi says nothing about a user on a weak mobile connection.
Recording time to first interaction on device
Start the timer when the ad is requested and stop it when the first touch, swipe or drag produces a visible response. That response is the point at which the creative is genuinely playable.
Watch the same run for slow or stuttering frames across the whole sequence, a pixelated or incomplete first frame, console log errors, and external requests that add data usage and delay. These are the functionality checks Unity applies to creatives.
Because an engagement is counted at first interaction or click, a sluggish start delays the measured engagement itself rather than only the picture.
Repeat the run for each build and note the spread rather than the single best figure, so a lucky load is not mistaken for an improvement.
Testing sound, orientation flips and interruptions
On iOS, sound must follow the physical mute switch: with the switch enabled, audio turns off, and flipping it activates or deactivates sound.
Lock and unlock the screen mid-demo. Sound should stop when the screen locks and restart when it is unlocked.
Rotate the device during play and confirm the layout does not break; compatibility with orientation changes is part of Unity's functionality checks.
Confirm the install button is accessible, not obstructed, and leads to the correct store. Google also advises that sound should not be enabled before the user interacts with a playable.
Diagnosing files that stall, stutter or get rejected
Oversized or near-limit files are the first thing to check. Reduce the file size, and remember that in the interstitial dimensions anything above 5.2 MB is rejected immediately.
Folder and file names inside the .ZIP may only contain letters, numbers, periods, hyphens and underscores. Spaces and other unsupported characters trigger an error, so rename the files and every directory in the path.
After renaming, update the references in your source code as well, otherwise the file will not render correctly.
An unsupported type error means a file must be removed or replaced. For dimension errors, switch to 320x480 or 480x320, or set the ad.orientation meta tag; where both tags are declared, the ad.orientation value is used.
Turning load-time findings into the next build
Log the bundle weight and the first-interaction time for every build, so a change in either figure can be tied to a specific edit.
Trim the demo toward a short interactive window and make the opening prompt obvious. On-screen cues such as 'Swipe to start' tell players what to do in the first seconds instead of letting them drift.
Aim for around 15 to 30 seconds of interactive play. Where a user has not interacted, TikTok recommends auto-advancing after 10 seconds while keeping a download call to action visible throughout the experience.
Cut or defer assets that load late, re-test the revised bundle, then check the asset and engagement reports to confirm the lighter build still holds attention.



