Glider

Introduction

"Glider" is a rich media banner type with 3D effects which loads and animates custom contents. A full banner set consists of a minimum of 3 assets:

  • initial banner - usually it is a standard (300x250) or a single expanding (300x250 collapsed and 970x450 expanded) banner;
  • actual glider - SWF / PNG / JPG / GIF (gif animation is not supported).

Glider banner solution loads AdCapture snapshots from the Adform Servers.

Info: Read more on MSN Homepage Rich Media: Glider

Glider.fla structure

  • preloader - will be shown on the initial load in a small banner.
  • controls - custom control bar (add custom buttons here).
  • banner - a snapshot of banner in site → set X, Y positions according to the position in a website - position also can be set through the flashvars 'bannerX' and 'bannerY' (flash vars override the banner position in the flash).
  • site (site snapshot holder- a snapshot URL must be specified through the flash var 'snapshot'.

             - site → page → image → the site snapshot will be loaded in this holder.

             - site → page → add custom assets if needed.

  • content (content holder)

             - content → preloader → will be showed durring the content load.

             - content → content → the content panel will be loaded here (content must contain an invisible asset in order to pre-calculate content 'width' and 'height' for animations).

  • background (wallpaper of a glider)

             - add assets to this container in order for them to be displayed as a wallpaper during glide animations.

Public methods

  • addState (stateParamsObject) - adds transition state of a glide.

id - id of transition.
position - position where to glide (DEFAULT, LEFT, RIGHT, CLOSE).
contentURL - URL of content to be displayed after a glide animation.
- custom x position → works when the position is not defined.
- custom y position → works when the position is not defited.
angle - glide panel angle of transition.
duration - duration of transition.

Note: 'default' - state is mandatory while others are optional.

  • close() - closes Glider.
  • glideTo(transitionId) - glides according to the specified transition.

Flash vars

  • snapshot - a full URL to a snapshot image of a website.
  • bannerX - banner asset x position in flash (flash vars overrides banner position in flash).
  • bannerY - banner asset y position in flash (flash vars overrides banner position in flash).

Note

  • Write custom code in the 'init' frame.
  • Make sure that the 'content' and 'site' banners actionscript is not exported in the first frame.
  • Add GliderEvent.START listener in order to perform custom action on the start of an animation.
  • Add GliderEvent.END listener in order to perform custom action on the end of an animation.

GliderEvent

  • state - current transition 'id'

Example

import flash.events.MouseEvent;
import com.adform.glider.event.GliderEvent;
import com.adform.motion.AdformTween;
import com.adform.net.AdformEvents;
import com.adform.utils.AdformFlashVars;

stop();

addState({id: 'default', position: DEFAULT, contentURL: AdformFlashVars.getFlashVar( 'homePanel', 'homePanel.swf')}); 
addState({id: 'left', position: RIGHT, contentURL: AdformFlashVars.getFlashVar( 'leftPanel', 'leftPanel.swf')});
addState({id: 'right', position: LEFT, contentURL: AdformFlashVars.getFlashVar( 'rightPanel', 'rightPanel.swf') });

var homeBtn = controls.homeBtn;
var leftBtn = controls.leftBtn;
var rightBtn = controls.rightBtn;
var closeBtn = controls.closeButton;
var state : String = "";

leftBtn.addEventListener(MouseEvent.CLICK, onLeftBtnClick);
rightBtn.addEventListener(MouseEvent.CLICK, onRightBtnClick);
homeBtn.addEventListener(MouseEvent.CLICK, onHomeBtnClick);
closeBtn.addEventListener(MouseEvent.CLICK, onCloseBtnClick);

addEventListener(GliderEvent.START, onGlideStart);
addEventListener(GliderEvent.END, onGlideEnd);

disableControls();
controls.visible = false;

function disableControls() {
    controls.mouseEnabled = closeBtn.mouseEnabled = homeBtn.mouseEnabled = rightBtn.mouseEnabled = leftBtn.mouseEnabled = false;
}

function enableControls() : void {
    

    closeBtn.mouseEnabled = true;
    homeBtn.mouseEnabled = state != 'default';
    rightBtn.mouseEnabled = state != 'right';
    leftBtn.mouseEnabled = state != 'left';
    

    controls.mouseEnabled  = true;
}

function onGlideStart(event:GliderEvent) {
    AdformTween.to( controls, 0.2, { alpha : 0, onComplete: onControlsHideComplete } );
}

function onGlideEnd(event:GliderEvent) {
    

    state = event.state;
    

    enableControls();
    controls.alpha = 0;
    controls.visible = true;
    AdformTween.to( controls, 0.2, { alpha : 1 } );
}

function onLeftBtnClick(event:MouseEvent):void {
    AdformEvents.callEvent("165", "Left Panel shown");
    disableControls();
    glideTo('left');
}

function onRightBtnClick(event:MouseEvent):void {
    AdformEvents.callEvent("166", "Right Panel shown");
    disableControls();
    glideTo('right');
}

function onHomeBtnClick(event:MouseEvent):void {
    AdformEvents.callEvent("164", "Home Panel shown");
    disableControls();
    glideTo('default');
}

function onCloseBtnClick(event:MouseEvent):void {
    

    disableControls();
    close();
    AdformTween.to( controls, 0.2, { alpha : 0, onComplete: onControlsHideComplete } );
}

function onControlsHideComplete() {
    controls.visible = false;
}

IAB Mobile Filmstrip

The IAB Mobile Filmstrip is a scrolling multi-panel ad experience designed to provide a content-rich and interactive canvas for storytelling with consistent behaviors that keep the viewer firmly in control.

More information can be found here:

Tablet version

This is a standard HTML asset ad.
  • Both horizontal and vertical interactions can be configured.
  • Must have a clearly defined navigation icon located at the top and the bottom of each content panel.
  • The navigation can be triggered by click or swipe.

Behavior

Initialy banner loads the first two panels. Once the user scrolls to the second panel, the banner loads the third one and so forth. When expanded to the fullscreen, the banner responds to rotation and renders specific designs for vertical and horizontal orientations.

Supported browsers

This format supports only Desktop and Tablet browsers listed below. The backup image will be shown on unsupported browsers.

Windows
  • Internet Explorer 7
  • Internet Explorer 8
  • Internet Explorer 9
  • Mozilla Firefox 3.6
  • Mozilla Firefox latest version
  • Chrome latest version
  • Opera latest version
  • Safari latest version
Mac
  • Mozilla Firefox 3.6
  • Mozilla Firefox latest version
  • Chrome latest version
  • Opera latest version
  • Safari latest version
iPhone/iPad/iPod
  • Safari latest version
  • Chrome latest version
Tablet/Mobile Android
  • Internet latest version
  • Chrome latest version
  • Firefox latest version
  • Opera Mobile latest version

Tracking Events

Tablet Filmstrip template implements following tracking events:

Custom tracking events can be implemented using dhtml.sendEvent. More info can be found here.

Plug & Play

  • Download TabletFilmstrip.zip which includes manifest.json, HTML and assets.
  • Upload it as an asset.
  • Create Rich Media Floating banner using the uploaded asset.

Known Issues

  • Swipe is not supported on desktop IE7 and IE8 browsers.
  • On Android native browser in Samsung Galaxy Tablet swipe will only work if banner is aligned left.
  • Landing page target does not work in Android and iPad Chrome browser. Landing page will always be opened in the current window.

Examples

For demo banner please follow this link.
 
You can download the template by clicking here.

 

Phone version

  • Template consists of Adhesion banner and a filmstrip in the expanded section.
  • Both horizontal and vertical interactions can be configured.
  • Must have a clearly defined navigation icon located at the top and the bottom of each content panel.
  • The navigation can be triggered by click or swipe.
  • Zoom is not supported as mobile sites usually do not have zooming. Media is responsible for this.

Behavior

Initialy banner loads the first two panels. Once the user scrolls to the second panel, the banner loads the third one and so forth. When expanded to the fullscreen, the banner responds to rotation and renders specific designs for vertical and horizontal orientations.

Supported browsers

This format supports only Mobile browsers listed below. The backup image will be shown on unsupported browsers.

Windows
  • Internet Explorer 7
  • Internet Explorer 8
  • Internet Explorer 9
  • Mozilla Firefox 3.6
  • Mozilla Firefox latest version
  • Chrome latest version
  • Opera latest version
  • Safari latest version
Mac
  • Mozilla Firefox 3.6
  • Mozilla Firefox latest version
  • Chrome latest version
  • Opera latest version
  • Safari latest version
iPhone/iPad/iPod
  • Safari latest version
  • Chrome latest version
Tablet/Mobile Android
  • Internet latest version
  • Chrome latest version
  • Firefox latest version
  • Opera Mobile latest version

Tracking Events

Phone Filmstrip template implements following tracking events:

Custom tracking events can be implemented by using dhtml.sendEvent. More information can be found here.

Plug & Play

  • Download the PhoneFilmstrip.zip which includes manifest.json, HTML and assets;
  • Upload it as an asset;
  • Create Rich Media Floating banner using the uploaded asset;
  • Choose "center/bottom" option in the Position dropdown.
  • Mark position fixed checkbox

Note: It is recommended to turn on the floating overlay.

Known Issues

  • On OS Chrome all the click tags in current window (_self) are opened and target property is ignored.
  • Android Opera Mobile usually does not handle the rotation from landscape to portrait. The banner maintains its landscape proportions in portrait mode.
  • Banner does not hide on the orientation change start when it is in collapsed state. It is impossible to detect the orientation change start action.
  • On IE10 Windows phone does not have touchstart event. More information on IE10 touch events can be found hereNote: Google maps on their swipe fires touchstart event, so Adform's swipe works in that case.
  • Google maps has to be added in a <div>, not <iframe>. Otherwise, the banner will not work correctly on Opera Mobile.
  • The Google maps in the example is added without Google API key, that allows only 25000 views per day. When creating a banner, you should get your own key.

Example & Template

For demo banner please follow this link.
 
You can download the template by clicking here.

IAB Mobile Slider

The IAB Mobile Slider is a two component ad unit. It appears as a standard banner which on user interaction horizontally slides over publisher's content to a full screen ad offering audiovisual interaction and other rich media experiences. More information can be found in IAB Specifications.

2 templates are possible:
  • SyncSlider - synchronized banner as a solution for slider (Standard banner + Full Page Flex).
  • AdhesionSlider - Adhesion banner with sliding content.

Behaviour & States

In order to slide the banner a user needs to swipe a small member; while for sliding back, the back button in the Back panel has to be tapped. Therefore, the content has to be arranged in a manner allowing clear understanding on how to open and close the banner. 
 
The banner is composed of 2 states:
 
Collapsed
 
In the collapsed state the banner can be a simple standard banner or adhesion banner. It has to include a Swipe or Slide call to action with a directional icon indicating the horizontal direction from which the Full Page Ad Component will slide into frame.
 
Expanded
 
In the expanded state the banner should cover the whole screen of the device and should comply with the IAB Mobile Full Page Flex specifications. Mandatory close function of the Slider Full Page Ad Component is a Back Banner Bar which is of the exact size and in the same placement of the Base Ad Component with a back button and a directional icon indicating the horizontal direction from which the publisher content will slide into frame. Slider Full Page Ad Component will allow multi-panel ad experiences enabled by a swipe action within the ad unit, but not in the Back Banner Bar.
 

Overlay

For a better user experience it is recommended to turn on a floating overlay when the banner is in the expanded state. However, overlay blinking may appear once the banner is shown. To avoid this, ARMA script should be added before the tag (see the example). 

Examples

Adhesion solution

<script type="text/javascript">
    var _adform = _adform || [];
    _adform.push(
      [ '1403226.overlay.autoShow', false ]
    );
</script>
<script language="javascript" src="http://track.adform.net/adfscript/?bn=1403226"></script>
Synchronized solution
	<script type="text/javascript">
    var _adform = _adform || [];
    _adform.push(
      [ '1403253.overlay.autoShow', false ]
    );
</script>
<script language="javascript" src="http://track.adform.net/adfscript/?bn=1403253;compoundSeqNo=1;compoundImpr=1"></script>

Tracking Events

The following tracking events are implemented in both IAB Mobile Slider templates:

Adhesion solution

  • First Expand (id - 21) - when the banner expands for the first time.
  • Other Expands (id - 22) - whenever banner expands.
  • Banner Collapse (id - 143) - whenever banner collapses.
  • Close Button Press (id - 23) - whenever back button is clicked in the expanded state.
  • Floating Banner Shown (id - 24) - whenever the floating part (or whole banner if adhesion) is shown.

Synchronized solution

  • Close Button Press (id - 23) - whenever back button is clicked in the expanded state.
  • Floating Banner Shown (id - 24) - whenever the floating part (or whole banner if adhesion) is shown.

Custom tracking events can be implemented using dhtml.sendEvent. 

Supported Browsers

This banner format supports Mobile (Tablet and Phone) browsers listed below:

Windows
  • Internet Explorer 7
  • Internet Explorer 8
  • Internet Explorer 9
  • Mozilla Firefox 3.6
  • Mozilla Firefox latest version
  • Chrome latest version
  • Opera latest version
  • Safari latest version
Mac
  • Mozilla Firefox 3.6
  • Mozilla Firefox latest version
  • Chrome latest version
  • Opera latest version
  • Safari latest version
iPhone/iPad/iPod
  • Safari latest version
  • Chrome latest version
Mobile (Tablet/Phone) Android
  • Internet latest version
  • Chrome latest version
  • Firefox latest version
  • Opera Mobile latest version
Mobile (Tablet/Phone) Windows
  • IE Mobile

Known Issues

  • Android Opera Mobile usually does not handle rotation from landscape to portrait. The banner maintains its landscape proportions in the portrait mode.
  • Chrome browser on iOS opens all click tags as _self without depending on the property.
  • Banner is not hiden during the orientation change. It is impossible to detect the orientation change start action.
  • Sometimes native Samsung Galaxy tab browser does not hide adress bar when scrolling down the page. This means that some part of the page (and the banner in full screen state) stays behind that bar.
  • On IE10 Windows browser phone does not have touchstart event. More information on IE10 touch events can be found here.
  • If the banner is positioned at the top left (coordinates: [0;0]) on iOS Safari and Chrome browsers it will always have interaction with at least one mouse over. This happens due to the fact that the mentioned browsers return the mouse coordinates to [0;0].
Synchronized solution
  • Video player is not working after hide of the expanded member on iOS.
  • There are some rendering issues (animation is not smooth) of expanded member after rotation on Android Mobile Firefox.

Plug & Play

Adhesion solution
  • Download SliderAdhesion.zip which includes manifest.json, HTML and assets;
  • Upload it as an asset;
  • Create Rich Media Floating banner using the uploaded asset;
  • Choose "center/bottom" or "center/top" (depending on the placement) option in the Position dropdown;
  • Mark "position fixed" checkbox.
Synchronized solution
  • Download SliderSyncBase.zip and SliderSyncFullPage.zip templates which includes manifest.json, HTML and assets;
  • Upload them as assets;
  • Create Rich Media Standard and Floating Banners using uploaded asset;
  • Create a synchronized banner out of created the banners.

Example & Template

For demo banner as Adhesion solution please follow this link.

You can download Adhesion solution template here.

For demo banner as Synchronized solution please follow this link.

To get the full template for Synchronized solution download these two files: SyncSliderBase and SyncSliderFPF.

Adform Direct Integrations

Common Technical RTB Ad Requirements

  • Animation length: not longer than 30 sec.
  • Accepted file types: JPEG, .GIF, .SWF (Flash), DHTML.
  • Cannot contain auto-video, auto-audio, or auto-expandable.
  • All Flash ads should support the clickTAG variable.
  • Take Over creative is not allowed.
  • Animated GIF ads must have a frame rate not faster than 5 fps.
  • Flash ads must have a frame rate not faster than 18 fps.
  • Ads that shake or have high frequency flicker rates (between 5 – 30 transitions per second) are not allowed.
  • Creative cannot be from or make a call to an unapproved adserver.
  • Pop ups, surveys, or any ads that spawn them are not allowed.
  • Colonizing ads that spawn additional windows or messages beyond the original advertising message are not allowed. Ads must open in a new tab or a new window only.

Ad Exchanges

Admeld Adtech BT Google AdX Jubii Rubicon
Admeta Adquota ConceptCPH Gule Sider Konverto.be Specific Media
Adright Pro AppNexus Inventory Sources Criteo iBillboard Microsoft Ad Exchange Talentum
AdScale Behrentz media Facebook Ad Exchange Improve Digital Pil Media WhiteRabbit
AdShark Berlingske Gaysir.no Yieldlab Pubmatic 4 Media Network
Adspine          

Admeld

The ad must match the following Admeld-specific requirements.
 
Technical Requirements
 
The following ad dimensions are accepted:
  1. 120x20;
  2. 120x600;
  3. 160x600;
  4. 180x150;
  5. 200x200;
  6. 234x60;
  7. 300x50;
  8. 300x250;
  9. 300x600;
  10. 320x50;
  11. 336x280;
  12. 468x60;
  13. 728x90.
  • Auto-play, auto-expandable are not allowed.
  • Take Over creative (DHTML) are not allowed.
  • Colonizing ads that spawn additional windows or messages beyond the original advertising message are not allowed.
  • Ads must open in a new tab or a new window.
  • Ads that contain adware/spyware, ActiveX, exit pops or viruses are not allowed.
  • Ads should not shake or have flicker rates between 5 – 30 transitions per second.
  • Pop up, survey, polls are not allowed.
  • All other standards, as issued by the IAB regarding ad guidelines, need to be adhered to (including looping and total animation time restrictions, etc.).
Prohibited Content
 
  • Nudity or sexually explicit advertisers or ads featuring sultry, suggestive or offensive material
  • Deceptive or misleading ads; by definition this would be ads that do not clearly indicate the advertised entity or mislead customers.
  • Ads that resemble system dialogue boxes, error messages, etc.
  • Ads cannot appear as if they are actually content or links on a publisher’s site.

Admeta

Ad format and size requirements:
 
  • Accepted file types: Image, Flash, DHTML, Standard Rich Media.
  • Supported ad dimensions:
  1. 120x60;
  2. 120x600;
  3. 160x600;
  4. 180x150;
  5. 250x360;
  6. 300x250;
  7. 300x600;
  8. 468x60;
  9. 728x90;
  10. 750x200;
  11. 970x90.

Note: Third party pixels are not allowed.

Adright Pro

Available only for Italy.

Ad format and size requirements:

  • Audio must be user-initiated. Off by default;
  • Auto-expand and auto-play not allowed;
  • Max. file size: 60kb;
  • Supported ad dimensions:
  1. 120x600;
  2. 160x600;
  3. 180x150;
  4. 234x60;
  5. 250x250;
  6. 300x250 or non-expandable video banner;
  7. 320x50 mobile;
  8. 336x28;
  9. 468x60;
  10. 728x90.

AdScale

Available only for Germany.
 
Ad format and size requirements:
 
  • Accepted file types: JPEG, GIF, SWF, DHTML and Standard Rich Media;
  • Supported ad dimensions:
  1. 120x600;
  2. 160x600;
  3. 300x250;
  4. 468x60;
  5. 728x90;
  6. 930x180.

AdShark

Accepted formats:
  • 300x250;
  • 160x600;
  • 728x90;
  • 930x180.

Adspine

Ad format and size requirements:

  • Accepted file types: JPEG, GIF, SWF, DHTML and Standard Rich Media;
  • Max. File size for flash ads: 50k;
  • Max. Animation length: 30 sec;
  • Framerate: 25-30 fps;
  • Although all IAB formats are supported, the priority is given to the following ad dimensions:
  1. 160x600;
  2. 300x250;
  3. 728x90;
  4. 930x180.

Adtech

Initially available for UK, Germany and Italy.

Ad format and size requirements:
 
  • Accepted file types: JPEG, GIF, SWF, DHTML and Standard Rich Media;
  • Supported ad dimensions:
  1. 120x60;
  2. 120x600;
  3. 160x600;
  4. 180x150;
  5. 250x360;
  6. 300x250;
  7. 300x600;
  8. 468x60;
  9. 728x90;
  10. 970x90.

Adquota (mobile)

Accepted formats:
  • 320x50;
  • 320x80.

AppNexus Inventory Sources

AppNexus creative standards apply for the following inventory sources:
  • Emediate;
  • Zodiac Active;
  • WebAds;
  • Hi-Media;
  • CPX Interactive;
  • Marimedia;
  • Harrenmedia;
  • Reach Junction;
  • Creafi;
  • OpenX;
  • bRealTime;
  • YieldAds;
  • Redux Media;
  • Ad.com Interactive Media;
  • MediaShakers;
  • Adknowledge;
  • Advance Media;
  • Matomy Media;
  • Bannerconnect;
  • DSNR Media Group;
  • Zenovia Digital Exchange;
  • Audience Amplify;
  • CPM Only;
  • Ybrant Digital;
  • Meta Network;
  • Altitude Digital Partners;
  • AudienceScience;
  • Beanstock Media;
  • Clove Network;
  • Collective Exchange;
  • Cox Digital Solutions;
  • Q1Media;
  • Switch Concepts;
  • Technorati Media;
  • Stailamedia;
  • A&N Media.
Requirements
 
Ad Dimensions:
 
Standard:
  1. 120x600;
  2. 160x600;
  3. 300x250;
  4. 468x60;
  5. 728x90;
Additional:
  1. 120x60;
  2. 120x90;
  3. 120x240;
  4. 180x150;
  5. 234x60;
  6. 380x200;
  7. 930x180.
Approved Ad Formats and specifications:
  • Flash files (the suggested version Flash 8 or lower);
  • GIF, JPEG image files;
  • 3rd Party Ad Tags from Approved Ad Servers only (HTML or raw JavaScript);
  • DHTML;
  • Expanding Rich Media banners;
  • Auto-expansion, page takeovers, etc. are not permitted (If a creative uses a roll-over to initiate audio without any delay, this will be marked as auto-initiated);
  • Audio and/or video loops must be limited to 30 seconds;
  • Pop Ads are permitted where publishers allow them;
  • A landing page must open in a new window or tab rather than navigate away from the publisher's page;
  • The creative's brand or offer must match the creative's landing page brand or offer;
  • Creatives can rotate images but are not permitted to rotate brands;
  • The creative's brand must be on the AppNexus brand list. We will add brands during the auditing process if necessary.

Prohibited Content

  • Promoting gambling (Paid, free, or gateway to paid gambling; with exceptions for Scratch Card sites, brick and mortar casinos or resorts, and state and national lotteries).
  • Have landing pages that do not meet the inventory content guidelines.
  • Depicting or delivering libelous, violent, tasteless, hate, defamatory, or illegal content.
  • Portraying partial or complete nudity, pornography, and/or adult themes and obscene content.
  • Simulating clicks, containing malicious code, viruses, or executable files of any kind.
  • Delivering surveys via floating layers.
  • Offers that lead to sites whose services in some manner include charging for government forms that are free or available for a lesser charge from the government site.

Behrentz media

Available only for Denmark.

Ad format and size requirements:
 
  • Accepted file types: JPEG, GIF, SWF, DHTML and Standard Rich Media.;
  • Max. size for image ads: 35kb;
  • Max. size for flash ads: 50kb;
  • Max. animation length: 30sec;
  • Supported ad dimensions:
  1. 160x600;
  2. 300x250;
  3. 320x50 (mobile);
  4. 728x90;
  5. 930x180.

Berlingske

Available only for Denmark.
 
Ad format and size requirements
 
  • Accepted file types: JPEG, GIF, SWF, DHTML.
  • All Flash ads should support clickTAG variable. 
  • Max. framerate of flash ads: 18 fps.
  • Animation length: 45sec. - 5 loops each of 9sec.
  • No auto-video, auto-audio or auto-expand.
  • Supported ad dimensions:
  1. 300x250;
  2. 930x180.

BT

Available only for Denmark.
 
Ad format and size requirements
 
  • Accepted file types: JPEG, GIF, SWF, DHTML.
  • All Flash ads should support clickTAG variable. 
  • Max. framerate of flash ads: 18 fps.
  • Animation length: 45sec. - 5 loops each of 9sec.
  • No auto-video, auto-audio or auto-expand.
  • Supported ad dimensions:
  1. 300x250;
  2. 930x180.

ConceptCPH

Accepted formats:

  • 300x250;
  • 160x600;
  • 728x90;
  • 930x180.

Criteo

Ad format and size requirements
 
  • Accepted file types: Image, Flash, DHTML, Standard Rich Media.
  • Supported ad dimensions: 
  1. 120x600;
  2. 160x600;
  3. 180x150;
  4. 234x60;
  5. 300x250;
  6. 300x600;
  7. 468x60;
  8. 728x90.

Facebook Ad Exchange

Ad format and size requirements:
 
  • Supported file type: Image.
  • Supported Ad dimensions: 100x72,100x80, 254x133, and 600x315.
  • Approval required.

Note: old formats (100x77 and 100x80) will be depreciated by September, 2014. Read more about the redesign.

"Title" and "Description" fields automatically become available in Banner Edit page when the image size is 100x72 or 100x80. Please note that these fields are not editable once the request for an approval is sent. 
 
Technical specifications for Facebook creatives
 
  • Image size: 100x72px or 100x80px.
  • Image and text must go to one landing page.
  • Title can be max. 25 characters long including spaces, with no word having more than 20 characters.
  • Body text can be max. 90 characters long including spaces, with no word having more than 20 characters.
  • Title and/or body cannot consist entirely of capital letters.
  • Title and body text cannot start with punctuation signs.
  • Title and body text cannot contain duplicate consecutive punctuation characters with the exception of 3 ellipses...
  • Title and body text cannot contain double spaces.
  • Title and body text cannot contain more than 2 consecutive 1 character words.
  • Title and body text cannot contain the following characters:
  1. \ ^ ~ _ = { } [ ] | < >
  2. International Phonetic Alphabet (IPA) Symbols, e.g., θ, ð, ʃ, ʒ, etc.
  3. Superscript and subscript characters with the exception of TM and SM.

Gaysir.no

Ad format and size requirements

  • Accepted file types: JPEG, GIF, SWF, and DHTML.
  • Max. file size: 60kb.
  • Audio and video must be user-initiated.
  • Supported ad dimensions:
  1. 180x500;
  2. 980x150.

Google AdX

Ad format and size requirements

  • Accepted file types: JPEG, .JPG, .PNG, .GIF, .SWF (Flash).
  • File size: no larger than 50K.
  • Animation length: no longer than 30 seconds.
  • Animated GIF ads must have a frame rate no faster than 5 fps.
  • Flash ads must have a frame rate no faster than 20 fps.
  • Creative cannot be from or make a call to an unapproved adserver.
  • Cannot contain auto-video, auto-audio, or be expandable.
  • The following ad dimensions are accepted for animated and non-animated ads:
  1. 120 x 240;
  2. 120 x 600 Skyscraper;
  3. 125 x 125;
  4. 160 x 600 Wide skyscraper;
  5. 180 x 150;
  6. 200 x 200 Small square;
  7. 234 x 60;
  8. 250 x 250 Square;
  9. 300 x 50 Mobile leaderboard;
  10. 300 x 250 Inline rectangle;
  11. 300 x 600;
  12. 320 x 50;
  13. 336 x 280 Large rectangle;
  14. 468 x 60 Banner;
  15. 728 x 90 Leaderboard.

Note:  "300 x 50 Mobile leaderboard" size is not allowed for Flash ads.

Info: For more technical details please follow this link, also "Technical specifications and creatives" section here. 

Note: Please, keep in mind that serving RTB Ads on GoogleAdX when using a third party click tracker or user redirect possibilities requires a specific setup process in the Adform’s system. For more information please refer to Adform Help & Support center.

Content Requirements
 
  • Only conventional graphical layout is allowed: ads must occupy the entire space of the image size you have chosen. Ads cannot appear sideways or upside down. Ads cannot be segmented, contain multiple copies of itself within the ad, or otherwise appear to be more than one ad.
  • Ad images must be clear, recognizable, and relevant. Text appearing in the ad images must be legible. No low quality or blurry images.
  • Strobing, flashing backgrounds, or otherwise distracting ads are not allowed.
  • Ads cannot mimic news articles and features. They may also not contain screenshots of Google AdWords text ads or otherwise simulate an AdWords text ad in any way.
  • Image content and associated website content must be family safe. Any image ads that contain Non-Family Safe or Adult material in the ad or website will not be accepted.
  • „Trick to click“ ads not allowed: ads cannot pretend to be a system or site warning. Ads cannot mimic or resemble Windows, Mac, or Unix dialogue boxes, error message, etc. Ads can have mock animated icons or features such as button images as long as the purpose of these features can be achieved on a landing page.
  • Ads can have mock animated features or icons as long as the functionality works or the purpose of these features can be achieved on a landing page.
  • The sole purpose of the ad cannot be to contest or game, or winning of prizes. However, ads can promote sweepstakes and contests on their sites (specific to animated ads).
  • "Mousing effects" do not have to be user initiated. Ads can simulate mouse or computer actions like mimicking the movement of a mouse icon within the parameters of the ad, as long as the mousing effects stop after 5 seconds (specific to animated ads).
  • Must adhere to content restrictions (no politics, dating, religion, video games (casual & online), ringtones & downloadables, get-rich-quick, weight loss, cosmetic procedures & body modification, drugs & supplements, sexual & reproductive health, consumer loans, free gifts, quizzes & surveys, misleading claims, references to sex & sexuality etc.).

Info: Ad must conform to the AdX Content Policy. Full details available at AdX Policy Center.

Additional Flash Requirements
 
  • Tracking event constraints: AdWords does not allow the specific tracking of user interactions that do not involve clicks.

Tracking parameters that are not allowed include:

  • View-through tracking;
  • Key-modifier tracking;
  • Mouse location tracking.
  • Other behaviors: The AdWords system reviews the code of all Flash ads as they are uploaded.

The following coded behaviors have restrictions on their use:

  • Extra calls: Your ad code cannot make external server calls for additional JavaScript or other functionality. All functionality must be localized to the code itself;
  • Tracking bypass: You cannot change the behavior of your ad to avoid or eliminate the AdWords redirect URL;
  • Destination changes: The ad should direct users to a web page with the appropriate destination URL. It should not open the destination URL within the ad iFrame itself;
  • Cursor behavior: Your ad may affect or change a user's mouse cursor (arrow) within the parameters of the ad, but the user should be able to stop this interaction if it is non-user initiated or it should auto-stop after 5 seconds;
  • Random numbers: Your ad may not include code that generates or uses random numbers.
  • Other disruptive behaviors: Ads may not be designed or coded to circumvent the basic and usual AdWords flow. This includes (but is not limited to) the ad being displayed normally to users, Google registering the impression, and a click directing the user to the destination URL indicated by the advertiser in their AdWords account.

Info: For more details on the Flash, including detailed technical specifications, please refer to the official Flash help center. 

In-stream video ad (VAST-compliant) requirements
 
Third-party In-Stream Video Ads are accepted on the DoubleClick Ad Exchange according to the following policies.
 
Technical Specifications
 
In-stream video ad:
  • Accepted video file types: MP4, FLV, and WebM video file types must all be included (other formats may be included but will not be used);
  • Audio file types MP3 or AAC preferred;
  • Maximum file size: 10MB;
  • Maximum video length is 20sec; however, the recommended length is <15 secs (to be eligible for the most publisher inventory);
  • Maximum frame rate: 30fps;

The following unit sizes are accepted:

  1. 480x360 (4:3);
  2. 640x380 (16:9);
  3. 1920x800 (5:2).
Companion ad only available through AdWords (not AdX) currently.
 

Note: Ad Exchange does not support in-stream video ads in mobile applications or on sites accessed through mobile browsers.

Creatives requirements
  • Creatives may not expand past ad unit boundaries.
  • All creatives must be free of applications including, but not limited to, ActiveX, viruses, exit pops, spyware, and malware.
  • Creative coding may not use cross-domain scripting or set cookies in unapproved domains.
  • All the creatives must open in new windows. The target window for the clickthrough URL must be set to "_blank" so the clickthrough will open in a new window. Do not leave the target statement undeclared.

Gule Sider

Available only for Norway.

Ad format and size requirements

  • Accepted file types: JPEG, GIF, SWF, HTML.
  • Max. framerate: 18 fps.
  • Max. animation rate: 20 sec.
  • Video and audio must be user-initiated.
  • Supported ad dimensions:
  1. 300x250 (max. 50kb);
  2. 768x150 (max. 60kb);
  3. 980x150 (max. 60kb).

iBillboard

Available only for Czech Republic.

Ad format and size requirements
 
  • Accepted file types: JPEG, GIF, SWF, DHTML and Standard Rich Media.
  • Supported ad dimensions:
  1. 120x600;
  2. 160x600;
  3. 300x250;
  4. 250x250;
  5. 750x100;
  6. 750x200.

Improve Digital

Technical Requirements

The following dimensions are accepted:
  1. 120x600;
  2. 160x600;
  3. 300x250;
  4. 728x90;
  5. 750x200;
  6. 468x60.
Prohibited elements:
  • Audio (automatic or user initiated via click/roll over);
  • Video.

Unacceptable formats:

  • Expandable ads;
  • Full page layer (float);
  • Layer popout;
  • Triple banner.
Prohibited Content
 
The following content will be blocked:
  • Blinking Ads (heavily blinking ads);
  • Text based ad's (like google text ads);
  • Various pop-up ads, incl. pop-up surveys;
  • Unverified hygiene products (e.g.Teeth Whitening/Improve Teeth).

Yieldlab

Ad Dimensions
 
  1. 160x600;
  2. 300x250;
  3. 728x90;
  4. Build/text-ads (a special German format for some publishers/agencies).
Prohibited Content
 
  • Pornography;
  • Racist;
  • Religious;
  • Political;
  • Tabacco;
  • Gabling;
  • Alcohol.

Jubii

  • Accepted formats:
  1. 300x250;
  2. 160x600;
  3. 728x90;
  4. 930x180.
  • Animation length: no longer than 30 sec.
  • Max. 3 loops.

Konverto.be

Ad format and size requirements

  • Title max. 25 characters long including spaces.
  • Body max. 90 characters long including spaces.
  • Clear call to action areas.
  • Accepted image file types: JPEG, GIF.
  • Supported image file dimensions: 100x72.

Microsoft Ad Exchange

The ad must adhere to the following Microsoft Ad Exchange-specific requirements.
 
Size and format requirements
 
  • Animation/looping is limited to the first 30 seconds (15 sec for US campaigns).
  • Cannot contain auto-video, auto-audio, or be expandable.
  • Pop ups or any ad that spawns them are now allowed.
  • Creative causing degradation of the site performance (including excessive file weights) is not allowed.
  • Cannot have fake close behavior (when you attempt to leave a page and another dialogue box appears) or fake operating system interface.
  • Ad opens into a new browser tab or window.
  • Creative must feature a one pixel border (grey [#666666] or black recommended, though any colour that clearly distinguishes the ad from the content may be used).
  • Standard Exchange Ad dimensions include:
  1. Button 120x60;
  2. Button 120x90;
  3. Banner 120x240;
  4. Skyscraper 120x600;
  5. Skyscraper 160x600;
  6. Rectangle 180x150;
  7. Banner 234x60;
  8. Rectangle 300x250;
  9. Rectangle 380x200;
  10. Banner 468x60;
  11. Banner 728x90.

Info: for detailed format requirements please visit advertising.microsoft.com/europe/home.

Immediate Removal Criteria
 
  • Risqué or racy content.
  • Inappropriate/illegal content, (ex. language, violence, potential brand competitor, alcohol).
  • Any gambling ads – „instructional‟ included.
  • Misappropriation of MSN or syndicated partners‟ logos or brand.
  • Competitive Exclusion (which includes Publisher Specified Requirements or covers other Publisher filtering).
  • Any creative with multiple CAP violations.
  • Non-compliance with AdChoices program.
  • Promoting or containing malware, viruses, worms, corrupted files or other material that jeopardizes user security and privacy.
  • Prohibited Content
  • No tobacco/weapons,
  • No nudity, nipples, area between navel and hip for non-bathing suit creatives
  • No dating/singles creative that contain beds, no seductive poses, or meeting "specific individuals" (atmosphere should be casual)
  • No sexually suggestive content
  • No defamatory or hate speech
  • No illegal activity
  • No profanity (“suck” or “I need a diet for my big butt”)
  • No suffering, violence, exploitation (includes international dating, overseas wife, etc.)
  • No Spyware or auto-downloads
  • No extra-specific targeting- Yes “find jobs in Chicago;” No “West Coast singles 21-30 who want to work in Thailand”
  • No spy cameras/systems (home surveillance and security systems are allowed)
  • No Windows dialogue boxes or fake error messages No photos of major political figures that could represent an endorsement
  • No internet pharmacies for now. No unverified pharmacies - check Verified Internet Pharmacy Practice at nabp.net
  • Gambling is only allowed state lotteries when ad appears in that state, and hotel/resort brick and mortar casinos.
  • Children's content is prohibited from prompting personally identifiable information (P.I.I.)
  • Political creatives cannot use “hot-button issues”
  • Web-based colleges must be accredited
  • Audio must be user-initiated (except when MSN approves it on a case-by-case basis.
  • No privacy policy on landing page that requests Personally Identifiable Information.
  • Exact offer in the creative is not actionable on the landing page (example: if 15% off is offered in the creative, 15% exactly must be advertised on the landing page.
  • Non-US landing pages are okay, but any prices shown in creatives must be in the advertiser country's currency.
  • Windows Live currently only accepts creatives in English and Windows Live Latino only accepts creatives in English and Spanish.

Info: Ad must conform to the MSN & Windows Live Creative Acceptance Policy. Please see the Creative Acceptance Policy Guide for further information.

Pil Media

Ad format and size requirements

  • Accepted file types: JPEG, GIF, SWF, DHTML, Standard Rich Media.
  • Max. file size: 60kb.
  • Video and audio must be user-initiated.
  • Supported ad dimensions:
  1. 160x600; 
  2. 180x500;
  3. 468x400;
  4. 580x400;
  5. 980x150;
  6. 980x300.

Prohibited content:

  • Pornography;
  • Racism;
  • Tobacco;
  • Gambling;
  • Alcohol.

Pubmatic

Ad format and size requirements
 
  • Accepted file types: Image, Flash, DHTML, Standard Rich Media.
  • Supported ad dimensions: 
  1. 120x600;
  2. 160x600;
  3. 180x150;
  4. 216x36;
  5. 234x60;
  6. 250x250;
  7. 300x50;
  8. 300x100;
  9. 300x250;
  10. 300x600;
  11. 320x50;
  12. 336x280;
  13. 468x60;
  14. 480x50;
  15. 728x90.

Rubicon

Ad format and size requirements
 
  • Accepted file types: Image, Flash, DHTML, Standard Rich Media.
  • Supported ad dimensions:
  1. 88x31;
  2. 120x60;
  3. 120x90;
  4. 120x160;
  5. 120x240;
  6. 120x600;
  7. 125x125;
  8. 140x350;
  9. 160x90;
  10. 160x600;
  11. 180x90;
  12. 180x150;
  13. 180x500;
  14. 200x90;
  15. 200x200;
  16. 234x60;
  17. 240x400;
  18. 250x250;
  19. 250x360;
  20. 300x50;
  21. 300x100;
  22. 300x250;
  23. 300x600;
  24. 300x850;
  25. 320 x 50;
  26. 336x280;
  27. 468x15;
  28. 468x60;
  29. 468x400;
  30. 468x728;
  31. 580x400;
  32. 728x15;
  33. 728x90;
  34. 750x100;
  35. 750x200;
  36. 750x300;
  37. 930x180;
  38. 980x120;
  39. 980x150.

Specific Media

Ad format and size requirements
 
  • File size no larger than 35k for image ads.
  • For flash ads: no larger than 50k.
  • Animation lenght: 30 sec max.
  • Framerate: 25-30 fps
  • Supported ad dimensions:
  1. 728x90;
  2. 300x250;
  3. 120x600;
  4. 160x600;
  5. 468x60;
  6. 930x180.

Talentum

Available only for Finland.

Ad format and size requirements

  • Accepted file types: JPEG, GIF, SWF, DHTML and Standard Rich Media.
  • Max file size for image ads: 40k.
  • Max file size for flash ads: 70k.
  • Max animation length: 35sec.
  • Framerate: 25-30 fps.
  • Supported ad dimensions:
  1. 140x350;
  2. 300x250;
  3. 728x90.

WhiteRabbit

Available only for Finland.

Ad format and size requirements
 
  • Accepted file types: JPEG, GIF, SWF, DHTML and Standard Rich Media.
  • Max file size for image ads: 35k.
  • Max file size for flash ads: 50k.
  • Max animation length: 30sec.
  • Framerate: 25-30 fps.
  • Sound on click only.
  • Supported ad dimensions:
  1. 160x600;
  2. 300x250;
  3. 728x90;
  4. 980x120;
  5. 980x400.

4 Media Network

In-stream video ad format and size requirements

  • Accepted video file types: MP4 and FLV.
  • Accepted audio file types: MP3 (preferably), AAC.
  • Max file size: 10MB.
  • Max video length: 30sec. (Note: special solution of longform format may be discussed and provided).
  • Framerate: 25-30 fps.
  • Supported ad dimensions:
  1. 480x360 (4:3);
  2. 640x380(16:9);
  3. Or any 4:3 and 16:9.

Introduction

Adform has released a beta version of HTML5 Toolkit: http://html5toolkit.adform.com/
Users of HTML5 Toolkit are able to create or upload projects:

By clicking Create, a user is able to create a new HTML5 banner from the list of default Adform templates or upload an already made HTML5 banner (ZIP that only contains CSS, JavaScript, images, etc.)
By clicking Upload a user can upload an already existing project. Note that only ZIP files generated in HTML5 Toolkit can be uploaded.

More information on each feature can be found on the following sections:

Note: send us feedback about Adform HTML5 Toolkit by simply clicking the  icon in the top right corner of the Toolkit page. Thanks!

Create Banner

By clicking Create you are represented with the following block:

There are two options available:

a) create Standard, Floating, Expanding or Single Expanding (1st row options) – this means you will have to upload ZIP with .html, .css, .js or image assets.  

Info: further steps of this option are presented within the Banner Settings section in the text below.

b) create banner from Adform predefined templates (e.g. Standard 300x250, IAB Billboard, Responsive Leaderboard, etc.) After choosing one of the templates, a workspace with a banner in Adform's design is opened:

Info: for futher steps proceed to other posts, i.e. banner edit, live preview, etc.

Banner Settings

If you have selected to create Standard, Expanding or Floating banner:

Adform HTML5 Toolkit will ask you to upload a ZIP file with banner assets:, .html, .js, .css and image files:

Once you have uploaded the file, click the banner settings icon in top menu:

Then click on the name of a project:

After clicking the name of a project, a banner asset dialog is opened. Enter mandatory info, such as banner height, width, add clickTAG, events (if there are any), and press the save button:

Now you are able to edit, export the banner or generate the live preview:

In order to edit a banner, select the HTML/CSS/JavaScript resource and click on it:

Edit the banner using the code editor which appears at the bottom of the screen:
 
 
You are also able to remove or add any file from resource list:
 
 

Responsive Banners

Adform HTML5 Toolkit has a feature for testing responsive banners.
If you have created or uploaded a responsive banner built according to the Adform specs, click  the icon in the left top corner:

By clicking the icon are able to set viewport dimensions and test the responsiveness.

Note: more details about Adform Responsive banners API coming soon.

Info: read the Adform - Responsive Banners manual for more information.

Live Preview

Using the HTML5 Toolkit you are able to share banner preview. To do so, click the preview icon located in the top menu:

Once you are finished creating a banner, click the download banner icon located in top menu:

After clicking the icon, the Toolkit generates a ZIP file which is compatible with the Adform system – it means you can upload it to Adform as a Toolkit ad.
Also, you are able to open this ZIP by using the Upload function in the HTML5 Toolkit.