Bidtellect's Advertising Specs

Bidtellect makes native easy and effective, our copywriters and graphic designers are available to assist with the creative production.

Get Native

Required Assets

Bidtellect Native Ad Unit Spec Sheet
Recomendation Widgets Imagery: Standard 1200 x 900 / 900 x 900 non-branded Max image size: 2MB Headline: <60 Characters Description: <150 Characters Sponsored by: <30 Characters Article/Landing Page
In-Ad Placements
In-Feed Placements

We only require 1 tag per image set. Our platform and technology converts your basic creative assets into real time native ads, handling all resizing dynamically

Bidtellect Native Video Ad Unit Spec Sheet
Instream Video Imagery: Standard 1200 x 900 / 900 x 900 non-branded Max image size: 2MB Headline: <60 Characters Description: <150 Characters Sponsored by: <30 Characters Article/Landing Page Video or YouTube
Auto-Play Preview / In-Feed Video Format: 3GP, AVI, MOV, MP4 and WMV (MP4 / H.264 is recommended) File size: 30MB for every 30 seconds Aspect Ratio: (16:9) 1920x1080, 1280x720 or 640x360 Duration:
Unlimited
Audio: Audio is supported. AAC audio is recommended. Video
Outstream Auto-Play
VAST / VPAID
VAST
Max supported file size is 20 MB
VAST
Video format must be MP4

VPAID
We only accept Javascript VPAID tags

AD TAG INSTRUCTIONS FOR IMPRESSION AND CLICK TRACKING

  • Bidtellect requires secure pixels (https://)
  • Bidtellect only accepts 1x1 pixel trackers for billing purposes
  • Javascript tags are accepted but 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
  • Please allow 48 hours to properly test and implement tags.

THIRD PARTY PARTNERS

  • Atlas
  • Conversant
  • Doubleclick
  • Flashtalking
  • PointRoll
  • Sizmek

STUDIES

  • Millward Brown

DATA COLLECTION

  • Adobe DMP
  • Adometry
  • comScore
  • Datalogix
  • DoubleVerify
  • Integral AdScience
  • Krux
  • MOAT

BOT/FRAUD MONITORING

  • Forensiq
  • WhiteOps

SUPPORTED MACROS

  • Asset ID
  • Brand ID
  • Campaign ID
  • Creative ID
  • Customer Brand ID • Impression Data
  • IO ID
  • ParentPublisherID • PlacementID
  • ProductID
  • Publisher ID
  • Publisher Name
  • Site ID
  • Timestamp

1x1 EXAMPLE
(Preferred)

http://ad.doubleclick.net/ddm/trackimp/Nxxxx.site-keyname/Byyyyyyy.n;dc_trk_aid={ad_id};dc_trk_cid={creative_id};ord=[timestamp]

CLICK TAG EXAMPLE
(Preferred)

https://ad.doubleclick.net/ddm/clk/[ad ID];[placement ID];[verifier]?[click-through URL]

JAVESCRIPT EXAMPLE
(Preferred)

<SCRIPT language=’JavaScript1.1′ SRC=”https://ad.doubleclick.net/ddm/adj/Nxxxx.site-key name/Byyyyyyy;sz=widthxheightord=[timestamp];dc_lat=N;dc_rdid=Czzzz;tag_for_child_directed_treatment=I;kw=[keyword];click=?”>

 

CONVERSION PIXEL

  • 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.

RETARGETING PIXEL

  • 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.

BIDTELLECT ENGAGEMENT CODE

  • The Engagement Code should be placed in the template header (com- mon 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.

Scale Content in Real-Time with Native Programmatic

Bidtellect’s nDSP is built on the IAB’s OpenRTB 2.3 spec, which enables the necessary communication between DSPs and SSPs to scale the delivery of Native ads in RTB environments. This technology takes the deconstructed assets of a Native ad and assembles and deploys it in real-time.

Learn More