Media KitRates & Ad Specifications

SourceForge Ad Specs: Adobe Flash

There are three options for serving Flash-based media on the SourceForge network: via a third-party; SourceForge-hosted tracking impressions only, and SourceForge-hosted tracking both impressions and clicks.

Following these three options is a General Guideline for Flash-based media, however, please note whatever option you choose, a backup GIF file is required for all Flash media. If you wish to track clicks separately for the backup GIF, separate from the .swf Flash creative, you must designate this different URL within your third-party server ad tag generator when you create your tags.

Option 1: Hosted by third-party:

  • Third-party-served Flash ads must include “sniffer” or “browser detection” code with the Flash creative.
Flash sniffer code is configured to detect major browsers and operating systems. Most major third-party servers such as Falk, Dart/Doubleclick, AtlasDMT, or Mediaplex, generate “sniffer” code behind the scenes when an ad tag is created in their system with the intent to publish. If you are unsure, check with your ad server support or customer service to make sure this necessary feature is enabled.

Option 2: Hosted by SourceForge for impression tracking only:
  • Supply a .swf Flash ad with embedded destination URL
  • Provide a click-thru URL for the backup GIF. This click-thru URL may be the same as the .swf click -thru, or different—you can choose to distinguish clicks between the Flash .swf and the generic backup GIF
  • Flash .swf files must be submitted with an embedded destination URL and a GIF backup. Any click tracking that takes place within the .swf Flash ad will only be through the embedded URL—therefore it is your responsibility to ensure the embedded URL is configured correctly. SourceForge will track impressions.
Option 3: Hosted by SourceForge for impression tracking AND click thru tracking:
  • Supply a .swf Flash ad with embedded clickTag variable (instructions below). Please also provide a destination click-thru URL to pair with the Flash ad. Do not embed the destination click-thru URL within the Flash file. The embedded code must be clickTag (below)
  • A backup GIF with a click-thru is required for all Flash media. This click thru URL may be the same as the Flash click thru, or different. The choice is yours should you choose to distinguish clicks between the Flash .swf and the generic backup GIF. SourceForge will track impressions and click-thrus
  • If submitting flash files for SourceForge to host AND track click-thru the flash files MUST be sent per the instructions below in order for SourceForge to track the click-thru. In order for SourceForge to track clicks on locally hosted Flash files, the variable called “clickTag” must be embedded inside the .fla file and published out as .swf. This clickTag variable is applied to the “button” of your Flash ad like so, with no modifications:
on (release) {
getURL(clickTag, “_blank”);
}


General Guidelines
  • Flash should be published at Version 8 or lower
  • Audio may not play automatically—all audio must be user-initiated. Embedded video is not allowed. Please see the audio and video guidelines.
  • The max file size for a Flash file is the same as standard media found in Ad Specifications.
  • Care should be taken that the fps (frames per second) be no faster than 12—18 fps
  • All links should be configured target=_blank
  • All Flash-based media must be submitted three (3) days before the campaign start date to ensure adequate testing.
Questions? Contact your sales manager, or [email protected]

Back to Ad Specifications Page