Expanding build guide
Review your work
Now that you've completed the Expanding build guide, take a minute to check your creative.
Make sure your Expanding creative:
- has all files saved in one root folder
- includes the Enabler component in the parent file and the proxy Enabler in all child files
- includes at least one exit
- includes a close button
- conforms to site spec limitations for file size. Many sites have a file weight limit of 40k initial load (parent file) and total file weight of 100k.
Test your creative in Flash
It's easy to review your creative in Flash before uploading it to the Studio Web UI. Verify that your creative functions properly by interacting with it and checking the traces in the Flash Output Panel.
By checking these traces in Flash, you can catch any errors before submitting to QA, which will ensure that your creative timeline runs smoothly.
|Function to test||What should trace in the Output Panel|
|exits||Enabler: Exit triggered: “Your exit name”
|counters||Enabler: Counter: “Your counter name”
|starting timers||Enabler: Start timer: “Your timer name”
|stopping timers||Enabler: Stop timer: “Your timer name”|
|expand||Enabler: Event: expand
Enabler: Ad expanded.
Expanding component event: expand
Expanding component event: loadInit
Expanding component event: load
|collapse||Enabler: Logged manual close.
Expanding component event: collapseBegin
Enabler: Ad collapsed.
Expanding component event: collapseComplete
Sarah is a DoubleClick Studio expert and author of this help page. Help her improve this article by leaving feedback below.