Flash Units
- Flash files served via DART must be coded properly for proper click and impression tracking
- All Flash files must be submitted as a .SWF file with accompanying back up gif/jpg for display to users who do not accept Flash. We accept Flash versions 8 and lower
- A click through URL and Default image must also be supplied for each .SWF ad unit
Detailed instructions for SWF file coding for DART Ad Serving:
- Create an invisible button over the area that you want 'active/clickable' to users
- On that invisible button |Action script, put the following action (Case Sensitive):
on (release) {getURL(_level0.clickTag, "_blank");} - Export the swf and test by opening the swf and clicking on the intended 'active' area. If a new browser or Explorer window opens upon click, the ad has been coded correctly for DART tracking. The ad must spawn a new browser window
- Please confirm the redirect for each swf file on a separate spreadsheet or word document
CPU Usage:
Idle CPU usage typically falls within 8-12%. When testing a Flash file for this ad, CPU usage after the initial loading of the file must be between 20% to 30%. An initial spike of up to 60% is acceptable in the first seconds. Idle CPU usage devised upon computer with a 1.8 GHz Intel Pentium Processor and 512 MB of RAM running standard programs.
CPU Usage Guidelines:
Macromedia's Flash Player utilizes a computer's CPU (central processing unit) in handlling all animation, masking, and computation contained within a Flash file. If a Flash file contains heavy amounts of mathematical computation for elements such as animation, loops, or timers, it will require a much greater percentage of CPU usage. As a result, the Flash file is forced to compete with other Flash files and other applications for CPU usage, which causes all Flash elements on the page to slow down significantly. There are several ways to help cut down on the CPU usage your Flash file requires. One way is to limit the amount of "math-based" animation - animation which is controlled by mathematical-based action script. Another way is to limit or eliminate looping functions in action script. Looping functions are usually associated with timers. Masking and animated masking techniques can also requires a large amount of CPU resources.
One way to estimate how CPU intensive your Flash file may be is to open the "Task Manager" (control+alt+delete) and view the "Performance" tab -- this gives a graphical estimate of CPU usage. With the Task Manager open your swf file in Flash player - you may see a spike as your Flash file is animating.
For more information on optimizing Flash files, see Macromedia's article, "Streaming and file optimization techniques for Flash Player".