test.adform.com

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. However, please note that most Ad Exchanges only accept files up to 49 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.

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.

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
  }
}

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, _root.landingPageTarget);
}

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 Window → Components 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 as follows:

button.addEventListener(MouseEvent.CLICK, ADFclicked);

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

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.
 

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, _root.landingPageTarget);
         SOME_FUNCTION();
         }

Incorrect:

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

• When using ActionScript 3:

Correct:

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

Incorrect:

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

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

• When using ActionScript 2:

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

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"), AdfFlashVarsUtil.getParameter("landingPageTarget"));
}

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 the query string 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, _root.landingPageTarget);
}

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, _root.landingPageTarget);
}

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, _root.landingPageTarget);
}

ActionScript 3.0 code:

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

VPAID enables cross-platform support for rich in-stream video ads. A valid VPAID object can be used in conjunction with the VAST and is highly recommended, as VAST ads that include VPAID protocols can play in both VAST and VPAID-enabled video players.

With VPAID, both linear and non-linear ads are supported, which include standard, expanding, overlay or mixed ads.

Standard banners with Adform Core components can function as VPAID ads. For advanced VPAID solutions, please see instructions below.

Instructions

How to "Close" ad:

• add AdformCloseButton to the banner.
• drag AdformCore component to the stage and dispatch 'close' AdformSharedEvent from your ad.

import com.adform.events.AdformSharedEvent;
root.loaderInfo.sharedEvents.dispatchEvent(new AdformSharedEvent('close'));

How to add 'clickTag':

• drag AdformCore component to stage
• draw clickTag button on stage
• give instanceName 'clickTag' to the button
• import com.adform.events.AdformSharedEvent
• add MouseEvent.CLICK eventListener to clickTag
• remove MouseEvent.CLICK eventListener on clickTag click
• dispatch 'click' AdformSharedEvent

import com.adform.events.AdformSharedEvent;
clickTag.addEventListener(MouseEvent.CLICK, onClickTagClick);

function onClickTagClick(e : MouseEvent) : void {
  clickTag.removeEventListener(MouseEvent.CLICK, onClickTagClick);
  root.loaderInfo.sharedEvents.dispatchEvent(new AdformSharedEvent('click'));
}

How to set 'expand':

• drag AdformCore component to stage
• dispatch 'expand' AdformSharedEvent from your ad.

import com.adform.events.AdformSharedEvent;

root.loaderInfo.sharedEvents.dispatchEvent(new AdformSharedEvent('expand'));

How to set 'collapse'

• drag AdformCore component to stage
• dispatch 'collapse' AdformSharedEvent from your ad.

import com.adform.events.AdformSharedEvent;
root.loaderInfo.sharedEvents.dispatchEvent(new AdformSharedEvent('collapse'));

How to implement custom 'skipAd' button:

• drag AdformCore component to stage
• draw skipAd button on stage
• give instanceName 'skipAdBtn' to the button
• import com.adform.events.AdformSharedEvent
• add MouseEvent.CLICK eventListener to skipAdBtn
• remove MouseEvent.CLICK eventListener on skipAdBtn click
• dispatch 'skip' AdformSharedEvent

import com.adform.events.AdformSharedEvent;
skipAdButton.addEventListener(MouseEvent.CLICK, onSkipAdBtnClick);

function onSkipAdBtnClick(e : MouseEvent) : void {
    clickTag.removeEventListener(MouseEvent.CLICK, onSkipAdBtnClick);
    root.loaderInfo.sharedEvents.dispatchEvent(new AdformSharedEvent('skip'));
}

How to 'resize' ad:

• drag AdformCore component to stage
• import com.adform.events.AdformSharedEvent
• add 'resize' eventListener
• reposition ad elements according to data object from event

root.loaderInfo.sharedEvents.addEventListener('resize', onAdResize);

function onAdResize(e : AdformSharedEvent) : void {
  // var data : Object = e.data;
  // data.playerWidth -> player width in pixels
  // data.playerHeight -> player width in pixels
  // data.viewMode -> "normal"/"thumbnail"/"fullscreen"
  // TODO : reposition ad elements according to data
}

How to update ad according to player 'start'

• place your starting code in the firstFrame

or

• drag AdformCore component to stage
• import com.adform.events.AdformSharedEvent
• add 'start' eventListener
• update ad elements according to data object from event

The code is as follows:

import com.adform.events.AdformSharedEvent;
import com.adform.events.AdformSharedEvent;
root.loaderInfo.sharedEvents.addEventListener('start', onAdStart);

function onAdStart(e : AdformSharedEvent) : void {
  // var data : Object = e.data;
  // data.playerWidth -> player width in pixels
  // data.playerHeight -> player width in pixels
  // data.viewMode -> "normal"/"thumbnail"/"fullscreen"
  // TODO : update ad elements according to data
}

How to 'pause' ad:

• drag AdformCore component to stage
• import com.adform.events.AdformSharedEvent
• add 'pause' eventListener
• pause ad

The code is as follows:

import com.adform.events.AdformSharedEvent;
root.loaderInfo.sharedEvents.addEventListener('pause', onAdPause);

function onAdPause(e : AdformSharedEvent) : void {
  // TODO : pause ad
}

How to 'resume' ad:

• drag AdformCore component to stage
• import com.adform.events.AdformSharedEvent
• add 'resume' eventListener
• resume ad

import com.adform.events.AdformSharedEvent;
root.loaderInfo.sharedEvents.addEventListener('pause', onAdPause);

function onAdPause(e : AdformSharedEvent) : void {
  // TODO : pause ad
}

How to 'update' volume:

• drag AdformCore component to stage
• import com.adform.events.AdformSharedEvent
• add 'volume' eventListener
• update ad volume

The code is as follows:

import com.adform.events.AdformSharedEvent;
  root.loaderInfo.sharedEvents.addEventListener('volume', onAdVolumeChange);

  function onAdVolumeChange(e : AdformSharedEvent) : void {
    // var data : Object = e.data;
    // data.volume
    // TODO : change volume
  }

VAST setup:

Both Linear and Non-linear ads must have these AdParameters set:

linear → true/false

clickTAG → your clickTAG URL

the code is as follows:

<AdParameters>
  <linear>true</linear>
  <clickTAG><![CDATA[http://www.adform.com/site/]]></clickTAG>
</AdParameters>

Ad Unit flash vars in VAST

There is a possibility to ad flash vars to ad unit in MediaFile source:

plain:   VPAIDWrapper.swf?url=adUnit.swf?param1=value1&param2=value2
encoded: VPAIDWrapper.swf?url%3DadUnit.swf%3Fparam1%3Dvalue1%26param2%3Dvalue2

Note: all request params must be encoded.

Below are the most common requirements for an ad running on supported inventory sources.

Common Technical Requirements

• Animation length: no longer than 30 sec.
• Accepted file types: JPEG, .GIF, .SWF (Flash), DHTML.
• Cannot contain auto-video, auto-audio, or auto-expandable.
• Excessive file weight (initial load size bigger than 50K) not allowed (depending on ad dimensions).
• All Flash ads should support the clickTAG variable.
• Supports Standard Rich Media and AdPages.
• Take Over creative not allowed.
• Animated GIF ads must have a frame rate no faster than 5 fps.
• Flash ads must have a frame rate no faster than 18 fps.
• Ads that shake or have high frequency flicker rates (between 5 – 30 transitions per second) not allowed.
• Creative cannot be from or make a call to an unapproved adserver.
• Pop ups, surveys or any ad that spawns them not allowed.
• Colonizing ads that spawn additional windows or messages beyond the original advertising message are not allowed. Ads must open in new tab or new window only.
• The most common ad dimensions include:

1. 120x600,
2. 160x600,
3. 300x250,
4. 468x60,
5. 728x90.

Please consult format/size requirements for each individual network.
All other standards as issued by the IAB regarding ad guidelines should be adhered to.

Common Content Requirements

• Spyware, malware viruses, ActiveX etc. results in removal of the ad.
• Non-functional, deceptive or misleading elements or content not allowed.
• Ads cannot appear as if they are actually content or links on a publisher’s site. It must be distinguished from content.
• No privacy policy on landing page that requests PII results in ad prohibition.
• Exact offer in the creative must be 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.
• Content restrictions: Banners of RTB campaigns must not have any sensitive information from these categories: 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. Prohibited content also includes tobacco/weapons, nudity, defamatory/hate content, illegal activities, profanities, exploitation (includes international dating etc.), spyware, extra-specific targeting, fake operating system interface, gambling; 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. No potential brand competitors, no misappropriation of logos or brand.
• Compliance with AdChoices program, if applicable (for Microsoft AdExchange).
• Competitive Exclusion not allowed (which includes Publisher Specified Requirements or covers other Publisher filtering).
• Inappropriate content not allowed (pornography, racist, gambling etc.)

Additional Flash Requirements

For clickTag implementation, please refer to the clickTAG Variables section.

Google AdX

The ad must adhere to the following Google AdX-specific requirements:

Size and format 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:
• 120 x 240
• 120 x 600 Skyscraper
• 125 x 125
• 160 x 600 Wide skyscraper
• 180 x 150
• 200 x 200 Small square
• 234 x 60
• 250 x 250 Square
• 300 x 50 Mobile leaderboard
• 300 x 250 Inline rectangle
• 320 x 50
• 336 x 280 Large rectangle
• 468 x 60 Banner
• 728 x 90 Leaderboard

Note:  "300 x 50 Mobile leaderboard" size isn't allowed for Flash ads.

Info: more technical details are available at Adwords Ad Requirements.

Content Requirements

• Only conventional graphical layout allowed: ads must occupy the entire space of the image size you've 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 the 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 the landing page.
• The sole purpose of the ad cannot be to play a contest or game or to win 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 don't 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 Flash, including detailed technical specifications, please refer to the official Flash help center.

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 now allowed.
• Creative causing degradation of site performance (including excessive file weights) 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:
• Button 120x60
• Button 120x90
• Banner 120x240
• Skyscraper 120x600
• Skyscraper 160x600
• Rectangle 180x150
• Banner 234x60
• Rectangle 300x250
• Rectangle 380x200
• Banner 468x60
• 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.

Admeld

The ad must adhere to 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 not allowed.
• Take Over creative (DHTML) not allowed.
• Colonizing ads that spawn additional windows or messages beyond the original advertising message not allowed.
• Ads must open in new tab or new window only.
• Ads that contain adware/spyware, ActiveX, exit pops or viruses not allowed.
• Ads should not shake or have flicker rates between 5 – 30 transitions per second
• Pop up, survey, polls 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.

Appnexus Inventory Sources

Appnexus creative standards apply for the following inventory sources:

• WebAds (Italy)
• Emediate (Denmark)
• Zodiac Active (Italy)
• Hi-Media (Italy)
• ADshark (Denmark)
• CPX Interactive (Czech)
• Marimedia (Czech)
• Harrenmedia (Czech)
• ReachJunction (Czech)
• Creafi (Czech)
• Rubicon (all)

Requirements

Ad Dimensions:

Standard:

• 120x600
• 160x600
• 300x250
• 468x60
• 728x90

Additional:

• 120x60
• 120x90
• 120x240
• 180x150
• 234x60
• 380x200
• 930x180

Approved ad formats and specifications

• Approved Ad Formats:

1. Flash files (suggested version Flash 8 or lower)
2. GIF, JPEG image files
3. 3rd Party Ad Tags from Approved Ad Servers only (HTML or raw JavaScript)
4. DHTML

• Auto-expansion, page takeovers, etc. are not permitted (If a creative uses roll-over to initiate audio without any delay, this will be marked as auto-initiated).
• Expandables currently not permitted.
• Audio and/or video loops must be limited to 30 seconds.
• Pop Ads are permitted where publishers allow them.
• The 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.

Specific Media

Ad 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

Improve Digital

Technical Requirements

• The following dimensions are accepted:

1. 120x600;
2. 160x600;
3. 300x250;
4. 728x90;
5. 468x60

• Prohibited elements:

1. Audio (automatic or user initiated via click/roll over);
2. Video;

• Unacceptable formats:

1. Expandable ads;
2. Full page layer (float);
3. Layer popout;
4. 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

• 160x600;
• 300x250;
• 728x90;
• Build/text-ads (a special German format for some publishers/agencies).

Prohibited Content

• Pornography;
• Racist;
• Religious;
• Political;
• Tabacco;
• Gabling;
• Alcohol

• Animation length: no longer than 30 sec.
• Accepted file types: JPEG, .GIF, .SWF (Flash), DHTML.
• Cannot contain auto-video, auto-audio, or auto-expandable.
• Excessive file weight (initial load size bigger than 50K) not allowed (depending on ad dimensions).
• All Flash ads should support the clickTAG variable.
• Supports Standard Rich Media and AdPages.
• Take Over creative not allowed.
• Animated GIF ads must have a frame rate no faster than 5 fps.
• Flash ads must have a frame rate no faster than 18 fps.
• Ads that shake or have high frequency flicker rates (between 5 – 30 transitions per second) not allowed.
• Creative cannot be from or make a call to an unapproved adserver.
• Pop ups, surveys or any ad that spawns them not allowed.
• Colonizing ads that spawn additional windows or messages beyond the original advertising message are not allowed. Ads must open in new tab or new window only.
• The most common ad dimensions include:

1. 120x600,
2. 160x600,
3. 300x250,
4. 468x60,
5. 728x90.

Please consult format/size requirements for each individual network.
All other standards as issued by the IAB regarding ad guidelines should be adhered to.

• Spyware, malware viruses, ActiveX etc. results in removal of the ad.
• Non-functional, deceptive or misleading elements or content not allowed.
• Ads cannot appear as if they are actually content or links on a publisher’s site. It must be distinguished from content.
• No privacy policy on landing page that requests PII results in ad prohibition.
• Exact offer in the creative must be 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.
• Content restrictions: Banners of RTB campaigns must not have any sensitive information from these categories: 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. Prohibited content also includes tobacco/weapons, nudity, defamatory/hate content, illegal activities, profanities, exploitation (includes international dating etc.), spyware, extra-specific targeting, fake operating system interface, gambling; 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. No potential brand competitors, no misappropriation of logos or brand.
• Compliance with AdChoices program, if applicable (for Microsoft AdExchange).
• Competitive Exclusion not allowed (which includes Publisher Specified Requirements or covers other Publisher filtering).