General

In order for ad-serving systems to track clicks when displaying Flash banners, the Flash banners must be programmed to use clickTAG variables instead of pre-defined URLs. The clickTAG variables are passed to the Flash file by the HTML page that shows the Flash banner. Thereby, the ad-serving systems can track the number of clicks and change the URL real-time, without having to modify the Flash banner.

  • File size is limited to 60 KB
  • Flash banners must be compiled with Flash 8 or higher versions
  • Fallback *.gif banners must always be supplied for all formats
  • Flash Clicks/Links use clickTAG’s
  • Clicks/Links must avoid being blocked by pop-up blocks
  • CPU usage must be limited

Please also follow Media (Publisher) restrictions for Loops, FPS, etc.

CPU Recommendations

Complexive flash banners may be the reason of high CPU usage. Some publishers are paying attention not only to file size but also to CPU usage. We recommend checking some common High CPU usage factors:

  1. Frame Rate is over 18 frames per second; reducing the number to 18 in most cases does not degrade visual performance.
  2. Multiple animated sequences across many layers animating at the same time.
  3. Animated sequences set to be translucent and animating on top of an imported graphic (ex: jpeg, png, etc.).
  4. Action Script-generated events set to randomly generate (ex: fog and rain).
  5. Imported graphics scaled up over a long period of time.
  6. Masking and animated masking techniques can also require a large amount of CPU resources.

Flash Banners Restrictions

Due to possible security issues Adform does not accept:

  • obfuscated Flash banners;
  • banners with some restricted AS functions;
  • banners which are Flash cookie dependant.

Please use the Test Section to check if the banners meet the requirements. Alternatively, you can contact Adform Traffic department for testing and suggestions on compatibility.

Also, Adform warns that when using the dynamic publishing method in Internet Explorer or Firefox on Mac stage.stageWidth and stage.stageHeight might initially return 0 (note that for Internet Explorer the stage size will be available on first load, however when reloading or revisiting a page it will initially be 0). The solution is to define a resize handler in your ActionScript code:

stage.addEventListener(Event.RESIZE, resizeHandler);
stage.dispatchEvent(new Event(Event.RESIZE)); // force stage resize event for normal cases 

function resizeHandler(event:Event):void {
  if (stage.stageHeight > 0 && stage.stageWidth > 0) {
    stage.removeEventListener(Event.RESIZE, resizeHandler); // only execute once
    // your initialization code here
  }
}

clickTAG variables

Methods for implementing the clickTAG variables in Flash banners depend on the ActionScript version used in the banners. The methods do the same job and are only different in the coding. Adform supports both ActionScript 2 and ActionScript 3 coded banners. If there is more than one target URL, please see the naming convention below:

var clickTAG;  // variable no. 1
var clickTAG2; // variable no. 2
var clickTAG3; // variable no. 3
var clickTAG4; // variable no. 4
var clickTAG5; // variable no. 5

Implementation of clickTAG variable

Implementation of the clickTAG variable depends on the version of ActionScript you are using. Also, due to constantly increasing online security measures in internet browsers, pop-up blocking is becoming a common problem in online advertising.

ActionScript 2.0 code:

on (release) {
    getURL(_root.clickTAG, "_blank");
}

ActionScript 3.0 code:

  1. Download and install "Adform Creative Toolkit" extension (detailed info can be found here).
  2. When "Adform Creative Toolkit" is installed, all Adform components are placed in your Adobe Flash installation directory. You are able to see them by selecting WindowComponents in the top Flash API menu:


     
  3. Then drag and drop the AdformCore on the stage.
  4. Create a button symbol on Flash API stage, and give it an instance name (e.g. button).
  5. ClickTAG then can be implemented by following example:
button.addEventListener(MouseEvent.CLICK, ADFclicked);

function ADFclicked(event:MouseEvent) {
    AdfURLNavigator.navigateToUrl( AdfFlashVarsUtil.getParameter("clickTAG"));
}

Note: always make sure you attach the ActionScript code that opens a new browser window to an instance of a button, not a movie clip. Also, the event, which triggers the opening of a new window, must be "release", not "press" because opening a new window on "press" event will definitely trigger the pop-up blockers.

Note: AdformCore can also be used in Flex 2/Flex 3/Flash Builder 4 by adding its swc in to the project library and using the following ActionScript 3 code:

var adformCore:AdformCore = new AdformCore(this.stage);

For testing clickTAG implementation, please use the Test Section.
 

Avoiding Pop-Up Blockers

Due to constantly increasing online security measures in internet browsers, pop-up blocking is becoming a common problem in online advertising. Adform has compiled a list of tips how to create banners that do not trigger pop-up blockers.

1. Always make sure you attach the Action Script code that opens a new browser window to an instance of a button, not a movie clip.

 

2. Make sure that the opening of the new browser window is the first action that happens after user clicks the banner/button (any delay between click and call to the function that opens a new window increases the possibility of triggering the pop-up blocker). E.g. the code in green is much less likely to trigger the pop-up blockers than the code in red:

  • When using ActionScript 2:

Correct:

         on(release) {
              getURL (_root.clickTAG, "_blank");
              SOME_FUNCTION();
         }

Incorrect:

         on (release) {
               SOME_FUNCTION();
                getURL (_root.clickTAG, "_blank");
         }

  • When using ActionScript 3:

Correct:

         button.addEventListener(MouseEvent.CLICK, ADFclicked);
         function ADFclicked(event:MouseEvent) {
         AdfURLNavigator.navigateToUrl(AdfFlashVarsUtil.getParameter("clickTAG"));
         SOME_FUNCTION();
         }

Incorrect:

        button.addEventListener(MouseEvent.CLICK, ADFclicked);
        function ADFclicked(event:MouseEvent) {
        SOME_FUNCTION();
        AdfURLNavigator.navigateToUrl(AdfFlashVarsUtil.getParameter("clickTAG"));
        }

3. Make sure the clickTAG method is implemented exactly as described below.

  • When using ActionScript 2:

on(release) {
      getURL(_root.clickTAG, "_blank");
}

Note: The event, which triggers the opening of a new window, must be “release”, not “press” because opening a new window on “press” event will definitely trigger the pop-up blockers.

  • When using ActionScript 3:

Create a button symbol on Flash API stage, and give it a name (e.g. button – pic. below).

Download Adform Core Component and paste this code to the same Flash API timeline frame where you created the button (replace the name "button" with how you actually called the button):

button.addEventListener(MouseEvent.CLICK, ADFclicked);
function ADFclicked(event:MouseEvent) {
AdfURLNavigator.navigateToUrl(
AdfFlashVarsUtil.getParameter("clickTAG"));
}

4. Banners should be compiled with Flash 8 or higher version. According to Adobe bug (http://bugs.adobe.com/jira/browse/FP-1065) there might be pop-up problems when interacting with lower version banners in Internet Explorer 7.

5. Test the Flash banner in live web environment for pop-up blocking. You can use Adform Creative Test Module which can be found here.

Transferring Variables in Query string

Transferring variables in the querystring is often desired when the user inputs some data interactively in the Flash banner, e.g. his/her e-mail or telephone number etc. This can be achieved by appending a ";cppar=1&" parameter to the clickTAG. This method to transfer these variables in the querystring is best described by an example:

ActionScript 2.0 code:

var EmailFlashVariable = "aa@aa.com";
on (release) {
    getURL(_root.clickTAG+";cppar=1&EmailURLVariable="+ EmailFlashVariable, "_blank");
}

ActionScript 3.0 code:

var EmailFlashVariable = "aa@aa.com";
button.addEventListener(MouseEvent.CLICK, ADFclicked);
function ADFclicked(event:MouseEvent) {
    AdfURLNavigator.navigateToUrl( AdfFlashVarsUtil.getParameter("clickTAG")
        + ";cppar=1&EmailURLVariable=" + EmailFlashVariable);
}

If the clickTAG is e.g. set to http://www.site.com the user gets redirected to http://www.site.com?EmailURLVariable= aa@aa.com when the Flash banner is clicked.

This method can be used for multiple querystring values:

ActionScript 2.0 code:

var a = 1;
var b = 2;
var c = "Hello";
on (release) {
    getURL(_root.clickTAG+";cppar=1&a="+a+"&b="+b+"&c="+c, "_blank");
}

ActionScript 3.0 code:

var a = 1;
var b = 2;
var c = "Hello";
button.addEventListener(MouseEvent.CLICK, ADFclicked);
function ADFclicked(event:MouseEvent) {
    AdfURLNavigator.navigateToUrl( AdfFlashVarsUtil.getParameter("clickTAG")
        + ";cppar=1&a=" + a + "&b=" + b + "&c=" + c;);
}

The corresponding target URL then becomes http://www.site.com?a=1&b=2&c=hello.

However the parameter ";cppar=1&" works only when landing page contains symbol "?". In other cases there should be used ";urlappend=" parameter:

ActionScript 2.0 code:

var DestinationVariable = "London";
on (release) {
    getURL(_root.clickTAG+";urlappend=" + DestinationVariable, "_blank");
}

ActionScript 3.0 code:

var DestinationVariable = "London";
button.addEventListener(MouseEvent.CLICK, ADFclicked);
function ADFclicked(event:MouseEvent) {
    AdfURLNavigator.navigateToUrl( AdfFlashVarsUtil.getParameter("clickTAG")
        + ";urlappend=" + DestinationVariable);
}

AdPages (powered by ISSUU)

AdPages is a way to link flash banners with easy-to-read AdPages. AdPages is created by merging a standard flash banner with a text document (PDF, Word, PowerPoint).

Preview:

Examples:

Creating Flash banner

In order to have a „book“ in the banner, the flash banner must have a movieClip object with an instance name „droppHolder“.

 The droppHolder movieclip:

  • The instance name of the movieclip should be named droppHolder
  • The droppHolder object has to have an element inside it, as an empty movieclip doesn't have any size. Adding a simple box with transparent fill is the easiest.
  • The publication preview doesn't follow the droppHolders dimensions exactly, but takes up as much space as possible while maintaing the pulication preview's aspect ratio.

Note: only banners made with ActionScript3 are supported

Requirements for uploading documents

  • The PDF should be Web-ready, meaning that it should be less than 100 mb and not have the large top/bottom/side margins as in normal print version;
  • The total number of pages should be no more than 500 pages;
  • Supported formats: PDF, Word (DOC), PowerPoint (PPT), Open Office (ODS, ODP), WordPerfect (WPD), Rich text format (RTF), Star Office (SXI, SXW);
  • Optimal image resolution: 150 ppi (higher resolution will be scaled down);
  • Supported PDF versions: 1.0 to 1.5;
  • Do not include bleed, crop, or other print markings;
  • The PDF should be 1-page-to-1-page, meaning that two actual pages (a spread) should not be 1 page in the PDF;

Info: for further info contact Adform technical support technical@adform.com

Expanding banner

Adform strongly recommends to use „Adform Creative Toolkit“ extension for creating Expanding banners. More info can be found here.

However, it's also possible to create Expanding banners without Adform Toolkit, below you will find detailed instructions on this.

Previews

Single Expand:

Expanding from two files:

Examples: 

Single Expand:

Expanding from two files: 

Instructions

Adform accepts two types of expanding banners:

  • Single file expanding
  • Expanding made Two files

Creating Single File Expanding banners

1. Banner should have one expanded size file.

2. The single file expanding banner uses one Flash file for both: expanded and collapsed views. On banner expand/collapse the viewable content is resized. This means that expand/collapse animation is more attractive comparing to expanding banners made from two assets.

3. Also when using Single File solution it is possible to track following events:

  • EXPAND_START - when banners starts to expand
  • EXPAND_END - when banner stops to expand
  • EXPAND_UPDATE - while banner is expanding
  • COLLAPSE_START - when banners starts to collapse
  • COLLAPSE _END - when banner stops to collapse
  • COLLAPSE _UPDATE - while banner is collapsing

Note: in order to track single file expand events banner must have Adform SingleFile component which can be downloaded together with Adform Creative Toolkit

4. If you need banner to expand/collapse on specific action, you should call such functions:

Expand:

a) In case you are using ActionScript 2:

import flash.external.ExternalInterface;

this.expandButton.onRelease = function():Void
{
  try
  {
       ExternalInterface.call('ADFExpand',_root.adId);
  }
  catch (e:Error)
  {
  }
};

b) In case you are using ActionScript 3:

import flash.external.ExternalInterface;
btn.addEventListener(MouseEvent.CLICK, onClick);
function onClick(e:MouseEvent):void
{
        try{
                   ExternalInterface.call('ADFExpand',
                   LoaderInfo(stage.loaderInfo).parameters.adId);
        }catch (e:Error) { };
}

Collapse:

a) In case you are using ActionScript 2:

import flash.external.ExternalInterface;

this.closeButton.onRelease = function():Void
{
  try
  {
       ExternalInterface.call('ADFClose',_root.adId);
  }
  catch (e:Error)
  {
  }
};

b) In case you are using ActionScript 3:

import flash.external.ExternalInterface;
btn.addEventListener(MouseEvent.CLICK, onClick);
function onClick(e:MouseEvent):void
{
          try{
                 ExternalInterface.call('ADFClose',
                 LoaderInfo(stage.loaderInfo).parameters.adId);
          }catch (e:Error) { };
}

3. You need to implement the clickTAG variable. Detailed instructions for clickTAG implementation can be found here.

4. Banners should be compiled with Flash 8 or higher version. There might be pop-up blocker problems when interacting with lower version banners in Internet Explorer 7.

5. Test the Flash banner in live web environment using Adform Creative Test Module.

Creating Expanding banners from Two Files

1. Banner should have one normal size file and one expanded size file and two backup gif’s in corresponding sizes, e.g. a 728x90 expanding banner consists of a 728x90 normal size file and a 728x300 expanded size file.

2. If you need banner to expand/collapse on specific action, you should call such functions:

Expand:

a) In case you are using ActionScript 2:

import flash.external.ExternalInterface;

this.expandButton.onRelease = function():Void
{
  try
  {
       ExternalInterface.call('ADFExpand',_root.adId);
  }
  catch (e:Error)
  {
  }
};

b) In case you are using ActionScript 3:

import flash.external.ExternalInterface;
btn.addEventListener(MouseEvent.CLICK, onClick);
function onClick(e:MouseEvent):void
{
        try{
                   ExternalInterface.call('ADFExpand',
                   LoaderInfo(stage.loaderInfo).parameters.adId);
        }catch (e:Error) { };
}

Collapse:

a) In case you are using ActionScript 2:

import flash.external.ExternalInterface;

this.closeButton.onRelease = function():Void
{
  try
  {
       ExternalInterface.call('ADFClose',_root.adId);
  }
  catch (e:Error)
  {
  }
};

b) In case you are using ActionScript 3:

import flash.external.ExternalInterface;
btn.addEventListener(MouseEvent.CLICK, onClick);
function onClick(e:MouseEvent):void
{
          try{
                 ExternalInterface.call('ADFClose',
                 LoaderInfo(stage.loaderInfo).parameters.adId);
          }catch (e:Error) { };
}

3. You need to implement the clickTAG variable. Detailed instructions for clickTAG implementation can be found here.

4. Banners should be compiled with Flash 8 or higher version. There might be pop-up blocker problems when interacting with lower version banners in Internet Explorer 7.

5. Test the Flash banner in live web environment using Adform Creative Test Module.

Tear back banner

Tear Back Flash Banners are an alternative way to get the user's attention and provide the advertisement message in a more interesting way which enhances the browsing experience. Tear Back Flash Banners (also known as Peel Back Banners) consist of two Flash files. An initial Flash banner resides in the upper right corner of the web page. When the user clicks on the initial banner, it tears down the page to reveal the full content banner. There are no limitations for the size or content of both – initial and content banners. These banners can combine several banner techniques (video streaming, interactive content, order/purchase forms, etc.).

Adform strongly recommends to use „Adform Creative Toolkit“ extension for creating Tear Back banners. The manual of „Adform Creative Toolkit“ can be found here.

However, it's also possible to create Tear Back banners without Adform Toolkit. Below you will find instructions on this.

Preview:

Examples:

Instructions

1. There must be two banners – initial and content.

2. Content banner must have a close button, which executes the following JavaScript code:

a) In case you are using ActionScript 2:

import flash.external.ExternalInterface;

this.closeButton.onRelease = function():Void
{
  try
  {
       ExternalInterface.call('ADFClose',_root.adId);
  }
  catch (e:Error)
  {
  }
};

b) In case you are using ActionScript 3:

import flash.external.ExternalInterface;
import flash.display.LoaderInfo;
ExternalInterface.call("ADFClose", LoaderInfo(this.root.loaderInfo).parameters.adId);

3. You need to implement the clickTAG variable. Detailed instructions for clickTAG implementation can be found here.

4. Banners should be compiled with Flash 8 or higher version. There might be pop-up blocker problems when interacting with lower version banners in Internet Explorer 7.

5. Test the Flash banner in live web environment using Adform Creative Test Module.

Banners for Adform Content Manager

Adform Content Manager allows creating a universal Flash banner which can dynamically change according to content definitions in Adform system. When using Adform banner elements, there is no need to physically alter the banners when the changes need to be applied to text, various properties (colors, alignment, etc.) or graphics. Below you will find detailed instructions on how to create Adform Content Manager compatible Flash banners.

Preview:

Examples:

Installation

For creating Adform Content Manager banners you need to download specific Adform components. This is done by downloading and installing „Adform Creative Toolkit“ extension. More info about installing this plugin can be found here.

Creating banner

Adform strongly recommends to use „Adform Creative Toolkit“ extension for creating banners with dynamic content. For opening this extenstion follow to Window --> Other Panels --> Adform in your Flash API top menu. The manual of „Adform Creative Toolkit“ can be found here.

However, you are able to create Adform Content Manager banners without „Adform Creative Toolkit“. You should follow these steps for creating such type banners:

1. When „Adform Creative Toolkit“ is installed, all Adform components are placed in your Adobe Flash installation directory. You are able to see them by selecting Window --> Components in the top menu.

2. Then drag and drop the AdformCore and AdformXMLManager components on the stage.

3. AdformXMLManager component has the following methods:

  • For loading a text variable value to a assigned textField:
AdformXMLManager.setText(varName:String, tf:TextField);

       varName - variable name in content xml at selected group;
       tf – textfield instance name.

  • For loading image to assigned movieClip with a preloader:
AdformXMLManager.loadFile(varName:String, mc:*,
loadCompleteHandler:Function, loadProgressHandler:Function);

         varName – variable name in content xml at selected group;
         mc – movieClip instance name;
         loadCompleteHandler – function to call when file has been loaded;
         loadProgressHandler - function to call while file is loading; properties arebytesLoaded and bytesTotal.

  • For retrieving variable values:
AdformXMLManager.getVarValue(type:String, name:TextField);

          type – variable type in the context xml, possible types are: text and graphic;
          name – variable name in the context xml.

Note: You are not able to access variable value until XML is completely loaded. You must listen to “AdformXMLManager.XML_LOAD_COPLETE” event.

  • Adding event listener:
AdformXMLManager. addEventListener (event:String, handler:Function);

          event – event name;
          handler – event handle function.

4. AdformXMLManager component has event which fires when XML is completely loaded:

AdformXMLManager. addEventListener (AdformXMLManager. XML_LOAD_COMPLETE, onXMLLoaded:Function);

5. For setting test XML location (this is ONLY for testing purposes, when publishing final banners this method should not be used as the AdformXMLManagers find the XML automatically):

AdformXMLManager.pathToXMLFile = “url:String”

url – valid URL to a content xml. Possible values are relative (ex.: metadata.xml) or full paths.

Note: examples and events of XMLManager component can be found here.

XML template

1. The XML structure is shown below – when using a local XML for testing purposes, please make sure that naming is correct: <root>, <TextVars> and <Graphics>.

<root>
<TextVars>
<TextVar name="BackgroundColor" value="F3F3F3"/>
<TextVar name="Text" value="Adform Banner Elements XML Example."/>
</TextVars>
<Graphics>
    <Graphic name="Logo" value="http://adform.com/en/images/logo.jpg" />
</Graphics>
</root>

2. You can validate your own XML against the below Adform Content Manager DTD – Document Type Definition:

<!DOCTYPE root [
<!ELEMENT root (TextVars,Graphics,Groups)>
<!ELEMENT TextVars (TextVar+)>
<!ELEMENT TextVar EMPTY>
<!ELEMENT Graphics (Graphic+)>
<!ELEMENT Graphic EMPTY>
<!ELEMENT Groups (Group+)>
<!ELEMENT Group (TextVars,Graphics)>

<!ATTLIST root xmlns:xsi CDATA #FIXED "http://www.w3.org/2001/XMLSchemainstance">
<!ATTLIST root xmlns:xsd CDATA #FIXED "http://www.w3.org/2001/XMLSchema">
<!ATTLIST TextVar name CDATA #REQUIRED>
<!ATTLIST TextVar value CDATA #REQUIRED>
<!ATTLIST Graphic name CDATA #REQUIRED>
<!ATTLIST Graphic value CDATA #REQUIRED>
<!ATTLIST Graphic assetID CDATA #REQUIRED>
<!ATTLIST Graphic av CDATA #REQUIRED>
<!ATTLIST Group name CDATA #REQUIRED>
<!ATTLIST Group id CDATA #REQUIRED>
]>

3. You need to implement the clickTAG variable. Detailed instructions for clickTAG implementation can be found here.

4. Banners should be compiled with Flash 8 or higher version. There might be pop-up blocker problems when interacting with lower version banners in Internet Explorer 7.

5. Test the Flash banner in live web environment using Adform Creative Test Module.