close

Contact

Message sent. Thank you our team will get back to you shortly.
  • 111 New
    Montgomery
    Street San Francisco,
    CA, 94107, USA
  • Room 1303 Kai Tak Comm Bldg. 317-319 Des
    Voeux Road, Central
    Hong Kong
login SIGN UP

OMNI DSP Resources

Ad Specifications

We support all Open RTB ad formats on our platform to give you flexible and diverse options to create engaging experience for your audiences.

We accepts almost any ad format that is accepted by our exchange partners. Precise specifications vary from exchange to exchange. To ensure your ads are accepted on all inventory sources, please follow the IAB US Display Guidelines and Mobile Guidelines. The following specifications are particularly important for the widest acceptance of ads.

Display (Banner) Ads
Image dimensions (Desktop):

728x90*, 300x250*, 160x600* (standard sizes) 120x600, 300x600

Image dimensions (Mobile):

320x50*, 300x50* (smartphone banner, most common)

320x480*, 480x320 (smartphone interstitial) 300x250* (mobile interstitial, tablet in-app, mobile web)

728x90* (tablet only)
1024x768*, 768x1024 (tablet interstitial)

File size (kb):

Recommended size upto 100kb, max. bulk upload files up to 700Kb

File type:

JPG, GIF, PNG, HTML5

Animation length:

No more than 15 seconds and/or 3 loops

Border:

Creative must clearly separated from the site content, either by a clear border or a non-white background color.

*Recommended Ad Sizes


Other Supported Ad Sizes

120x20, 168x28, 180x150, 216x36, 234x60, 250x360, 300x50, 300x170, 300x340, 300x1050, 320x240, 320x320, 336x280, 386x300, 400x300, 468x60, 480x360, 480x800, 631x385, 640x480, 700x450, 750x200, 970x90, 970x250, 980x120, 980x150, 990x200

Video Ads
Video dimensions:

Minimum height of 144 px
Up to 2048x1080. Avoid uploading UHD (4K) video or higher resolution.

Aspect ratio:

16:9 or 4:3

Time:

Up to 60 seconds

Standard file upload size:

1MB

 

VAST/ VPAID

Third-party VAST 2.0 or 3.0 is also accepted. Only InLine Linear ads are accepted; Non-linear and wrappers are not accepted. VAST from a third party server must contain at least one MP4 media file: but it is strongly advised that the following be in the VAST:

  • MP4 high bitrate
  • MP4 low bitrate
  • FLV high bitrate
  • FLV low bitrate
  • (Optionally, but preferably) WebM high bitrate
  • (Optionally, but preferably) WebM low bitrate

"Low bitrate" is around 400-600kbps, "High bitrate" is around 1000-1200 kbps. Multiple bitrates are recommended for broadest acceptance, with at least one version with a bitrate less than 400kbps for mobile compatibility.

Ideally, the low bitrate versions are encoded at a lower resolution (i.e. 640x360 for 16:9 video, 640x480 for 4:3 video) if the high bitrate version is at a higher resolution. This is because the quality of a high resolution video at low bitrate will be poor, and some devices, especially mobile, may have difficulty playing very high resolution (i.e. 1080p) video. For more information, see: http://www.iab.net/displayguidelines under 'Universal Ad Package' for guidelines.

POP UNDER ADS

We also do accept POP under ads for HTTPs links. A type of window that appears behind the browser window of a Web site that a user has visited. In contrast to a pop-up ad, which appears over (on top of) the browser window, a pop-under is less obtrusive as it hides behind other windows. Pop-unders are used extensively in advertising on the Web, though advertising is not the only application for pop-under windows.

Tracking Macros

The following macros can be used in destination click URLs, JS/Iframe tags or impression tracker.

Macro
Explanation
[ADX_TRANSACTION_ID]

Passes the unique ID # of the ad for the impression.

[ADX_BUNDLE_ID]

Passes a numeric ID (for Apple) or bundle name (for Google) specific to the mobile app responsible for generating the impression. Example values: “383763″ (Apple) or “com.google.mygoogleapp” (Google) (mobile only)

[ADX_APP_URL]

Passes a string that outputs the origin or type of application responsible for the impression. Example value: “https://itunes.apple.com/us/app/angry-birds-classic/id343200656?mt=8” (Apple) or “https://play.google.com/store/apps/details?id=com.lonedwarfgames.tanks.android&hl=en” (Google) (mobile only)

[ADX_APP_NAME]

Passes name of app that the ad is being served on

(e.g.”Tank Recon 3D (Lite)”)

[ADX_APP_VER]

Passes version of app that the ad is being served on

[adx_publisher_id]

Passes the site ID of the publisher (e.g. 30_692ff3dff09f)

[adx_network_name]

Passes the name of the exchange for the impression/click.

[ADX_ADS_REFERRER]

When used in a destination click URL or impression tracker URL, it passes Referrer URL where ad is viewed.

(e.g.”http://www.bbc.com/news/business-44232539″)

[ADX_ADS_DOMAIN]

When used in a destination click URL or impression tracker URL, it passes only the domain name.

(e.g. “bbc.com”)

[adx_camp_code]

Passes the unique ID # of the campaign for the impression/click.

[adx_banner_code]

Passes the unique ID # of the Banner for the impression/click.

[adx_zone_size]

Passes the unique ID # of the ad size for the impression/click.

[ADS_WIDTH]

Width of the ad unit as a string ad. (e.g. “320”)

[ADS_HEIGHT]

Height of the ad unit as a string ad. (e.g. “50”)

[ADX_USER_IP]

Passes the IP address of the user

[ADX_CARRIER]

Passes the name of the mobile carrier for the impression/click.

[adx_geo_country]

Passes the country of visitor (ISO 3166-1 alpha-2 codes: AU, CA, US, CN

[adx_user_os]

Passes the Device operating system

[ADX_USER_UA]

Passes the Device user agent

[ADX_LAT]

Passes the Latitude

[ADX_LONG]

Passes the Longitude

[ADX_DEVICE_MAKE]

Passes the name of the Device make (e.g., “Apple”)

[ADX_DEVICE_MODEL]

Passes the name of the Device model (e.g., “iPhone”)

[ADX_DEVICE_ID]

Unhashed mobile advertising identifier (IFA) – specifically, Google Advertising ID or iOS IDFA, when available. (mobile only)

[ADX_DEVICE_IDFA]

Unhashed IDFA, when available. (mobile only)

[ADX_ADV_ADID]

Unhashed Google Advertising ID, when available. (mobile only)

[ADS_CLICK_URL]

Inserts click tracking link.

[adx_txn_id]

Passes a unique identifier representing the current click/impression, further used for tracking conversions.

[ADX_ADS_CACHE]

Passes a random number “Cache Buster”.

[ADX_ADS_MIMES]

Passes mime types.


*We suggest to use [ADX_ADS_DOMAIN] macro instead of [ADX_BUNDLE_ID] since [ADX_BUNDLE_ID] handles only in app and [ADX_ADS_DOMAIN] handles both site domain and app bundle within one campaign.

Conversion Tracking

What Is It?

Conversion pixels allow you to track the success of your campaign by reporting back an action that the user has completed on your website/app after arriving through an advertisement. Once conversion pixels are placed, you will be able to see how many conversions are generated from each site, placement, banner, etc. Conversion pixels can be used to track actions such as:

  • The user makes a purchase.
  • User signs up for your site.
  • User submits their e-mail address.
  • User arrives at your “goal page”.
  • Any other event or action on your website/app.

 

How It Works

A conversion pixel is a short line of code that you will place on your conversion page (“Thank You” page). We generate a unique transaction id value when your ad is clicked by a user. This transaction id value can be passed through to your campaign URL by using [adx_txn_id] macro, we need you to store and send back the information that we called ‘adx_txn_id’.

At a later point in time, when the user arrives at your thank you page and loads the conversion pixel our server uses the transaction id which was passed via your landing page URL and saved at your end and passed to the conversion pixel replacing the macro [adx_txn_id] to record conversion against the impression.

You will then know which placement on which domain generated the conversion, and which specific creative the user clicked on. This information will be available in your campaign statistics.

To do this:

Enter the landing page link that you use for the ad in the Click URL. Add the parameter for our adx_txn_id at the end of the URL.
[adx_txn_id] is a required id for us to track the conversion.
The Click URL setup should look like: http://landingpage.com?qs=[adx_txn_id]

You can define the name of the variables according to your tracking system. For example, define [adx_txn_id] as qs=, or subid= or v1=. This depends on your tracking system.

After clicking on one of your ads, users are redirected to your web property and will hopefully move through your funnel to complete the desired action. This action could include making a purchase, filling out a form, submitting email information, or some other event. In any of these cases, the successful action is referred to as a conversion. Conversion pixels are used to count the number of users that completed an action and attribute that conversion information back to the campaign.

Place the below pixel on your website’s conversion page, before the closing body tag.
<img src=”http://r.adsaxis.com/adx-dir-d/servlet/WebF_AdManager.AdActionManager?nid=4&adx_txn_id=[adx_txn_id]” border=”0″>

Once you have updated your website with the conversion pixel, users that arrive at this page by clicking your ad in the future will be counted as conversions.

Example of an actual Pixel (transaction id replaced with a unique id)
<img src=”http://r.adsaxis.com/adx-dir-d/servlet/WebF_AdManager.AdActionManager?nid=4&adx_txn_id=9bf2bd6b-5e38-4b2b-9f8b-5e51322f131a” border=”0″>