Recommendation Widgets


Standard 1200x900


non branded

*Max image size:2MB





Sponsored by:


Article/Landing Page

In-Ad Placements

In-Feed Placements

In-Stream Video

Video or YouTube

Auto-Play Preview/In-Feed Video

Format: 3GP, AVI, FLV, MOV, MP4 and WMV (MP4 / H.264 is recommended)

File Size: 30 MB for every 30 seconds

Aspect Ratio: (16:9) 1920x1080, 1280x720 or 640x360

Duration: Unlimited

Audio: Audio is supported. AAC audio is recommended.


Outstream Auto Play *

no copy or image needed

Format: 3GP, AVI, FLV, MOV, MP4 and WMV (MP4 / H.264 is recommended)

File Size: 30 MB for every 30 seconds

Aspect Ratio: (16:9) 1920x1080, 1280x720 or 640x360

Duration: Recommended 15-30 seconds

Audio: Audio is supported. AAC audio is recommended.


VAST/VPAID for video
Max supported file size is 20MB
Video format must by MP4
We only accept (Flash/Javascript) VPAID tag


  • Bidtellect requires secure pixels (https://)
  • Bidtellect only accepts 1x1 pixel trackers for billing purposes
  • Javascript tags are accepted by this may limit where campaigns may run since not all native supply sources support Javascript
  • Standard HTML tags (jump tag with ad server hosted image are not supported/allowed)
  • Standard click trackers are accepted

1x1 Example (Preferred);dc_trk_aid={ad_id};dc_trk_cid={creative_id};ord=[timestamp]

Click Tag Example (Preferred)[ad ID];[placement ID];[verifier]?[click-through URL]

JavaScript Example*

<SCRIPT language='JavaScript1.1' SRC=";sz=widthxheightord=[timestamp];dc_lat=N;dc_rdid=Czzzz;tag_for_child_directed_treatment=I;kw=[keyword];click=?">

*not all sites accept JS tags


Bidtellect supports nearly any video format for uploading. Examples are 3GP, AVI, FLV, MOV, MP4 and WMV. There are a few noteworthy formats that are not supported:

  • Quicktime (MOV) files that use the Apple Intermediate Codec (used in Final Cut Pro). 
  • DRM protected files from Microsoft (WMV) or the iTunes Store (M4V, MOV). 
  • WMV videos using the MSS2 video codec (for screencasting). 
  • Videos generated by GoToMeeting.
If you are in control of the format (e.g. when exporting the video from your editor), we advise you to always upload videos using: 
  • The MP4 container format 
  • The H.264 video codec 
  • The AAC audio codec

Dimensions & Bitrates for video
In terms of dimensions, bigger is better. Video in 720p is today's standard and a great option. We also see an increase in 1080p uploads. If your original video is full HD, we suggest you upload 1080p too. If your source footage is standard definition (NTSC, PAL), we suggest 360p as the dimension to use. Anything smaller than 360p is not recommended. 

Since H.264 and AAC are excellent codecs, the upload bitrates do not have to be extremely high. They should be sufficiently high to not introduce any data loss though. Remember that Bidtellect creates the final encodes to be streamed. If the input format already has compression artifacts, the final transcodes may look quite bad. 

Here is an overview that includes the preferred format, dimensions and audio/video bitrates to use. If you upload video in these formats, Bidtellect will be able to build high quality transcodes and deliver smooth playback across devices.

1920x1080 pixels
1280x720 pixels
640x360 pixels
Video Bitrate
15,000 kbps
10,000 kbps
5,000 kbps
Audio Bitrate
256 kbps
256 kbps
256 kbps

Note that our built-in transcoding will generate smaller versions of your uploaded video. If you upload video in 1080p, only viewers whose device and connection support 1080p playback will see that resolution. Other viewers (e.g. on older computers or phones) will see lower resolution transcodes (e.g. 360p or 180p).

Bidtellect Pixels:


  • The conversion pixel should be placed at the confirmation page or a thank you page post transaction. This would be after a user has made a purchase, registered for something, or any action you would like to measure for the campaign.

  • Additionally, the conversion pixel can also be placed on any page where you'd like to measure post-click activity, regardless of transaction or not. For example, if there is a secondary click that an advertiser wants to measure after landing on the homepage, the Bidtellect conversion pixel can be placed there.

  • At this point, advertisers can only utilize one conversion pixel per IO.


  • The retargeting pixel should be placed on any page on an advertiser's site where they'd like to collect a pool of users to remarket on the same or subsequent campaign.

  • For best practices and scale, we recommend that the advertiser place the RT pixel on their homepage or any page that generates the most volume in order to collect the largest user pool. The RT pixel can also be placed on multiple pages, including the advertiser's landing page.


  • The Engagement Code should be placed in the template header (common head HTML tag) so that we can track user behavior across multiple areas of your site.

  • If the template header is not possible,The Engagement Code can be placed in a common container footer that runs across your site's subdomains.