Bidtellect's Advertising Specs

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

Required Assets

Bidtellect Native Ad Units

Access to the award-winning Creative Services Team, [b]+studio, expert storytellers that have a deep understanding of best-performing images and copy and can help create your custom content assets.

R

Native Ad Units

Recommendation Widgets

In-Ad Placements

In-Feed Placements

Imagery

Required: 1200 x 900 / 900 x 900 / 1200 x 628 non-branded Max image size: 2MB. (.jpeg, .gif, .png)

c

Headline

< 60 Characters

b

Description

< 150 Characters

|

Sponsored by

< 30 Characters

;

Content Destination

Article/Landing Page

Cinemagraph Native Ad Units

R

Native Ad Unit

Cinemagraph

Imagery

Animated .gif file; 2 MB (Maximum 5 seconds long (looped)

c

Headline

< 30 Characters

b

Description

< 150 Characters

|

Sponsored by

< 30 Characters

;

Content Destination

Article/Landing Page

Carousel Native Ad Units

R

Native Ad Unit

Carousel

Imagery

Recommended: 1200 x 1200
Minimum: 500 x 500
<= 2MB

Logo (Optional):
JPEG or PNG – transparent recommended
Minimum Size: 300 x 300

c

Headline

30 Characters or less
Can have different headlines per image

b

Description

150 Characters or less
Can have different long text per image

|

Sponsored by

25 Characters or less

;

Content Destination

Each Pane can have a unique click URL

3rd Party Trackers:

1×1’s and JS trackers accepted

NOTE:

  1. View tags can only be per Carousel Unit. There cannot be unique view tags per pane.
  2. Need to make sure to replace all “timestamp” macros with “{unixtimestamp}”. This will not be auto-replaced in the DSP like it normally is.

 

Scroller Native Ad Units

R

Native Ad Unit

Scroller

Imagery

A minimum of 2 images is required. Max of 5 images.
Recommended: 1200 x 800, Minimum: 500 x 500 – Maximum: 1200 x 1200
File size: <= 2MB

Logo (optional):
JPEG or PNG – transparent recommended
Minimum Size: 300 x 300

c

Headline

30 Characters or less
Can have different headlines per image

b

Description

150 Characters or less
Can have different long text per image

|

Sponsored by

25 Characters or less

;

Content Destination

Each Image can have a unique click URL

3rd Party Trackers:

1×1’s and JS trackers accepted

NOTE:

  1. View tags can only be per Carousel Unit. There cannot be unique view tags per pane.
  2. Need to make sure to replace all “timestamp” macros with “{unixtimestamp}”. This will not be auto-replaced in the DSP like it normally is.

 

Reveal Native Ad Units

R

Native Ad Unit

Reveal

Imagery

1200 x 1200
File Size: < 2 MB

Logo (optional):
Transparent JPEG or PNG
Minimum Size: 300 x 300
File Size: < 2 MB

 

c

Headline

30 Characters

b

Description

150 Characters or less

|

Sponsored by

25 Characters

;

Content Destination

Each Reveal Unit can have 1 click URL

_

Text Overlay

500 character maximum
Longer text will force user to scroll
Plain text (will display as white on black)

Trigger Options

The Adv should choose the “reveal” action that they would like to use.

  1. Corner Peelback (default)
  2. Custom Text (such as “More Info” or “Terms and Conditions”).
  3. Info Icon.

 

3rd Party Trackers:

1×1’s and JS trackers accepted

NOTE:  Need to make sure to replace all “timestamp” macros with “{unixtimestamp}”. This will not be auto-replaced in the DSP like it normally is.

Window Native Ad Units

R

Native Ad Unit

Window

Imagery

Recommended: 1000 x 1500
Minimum: 500 x 800
<= 2MB

Logo (optional):
JPEG or PNG – transparent recommended
Minimum Size: 300 x 300

 

 

c

Headline

30 Characters or less

b

Description

150 Characters or less

|

Sponsored by

25 Characters or less

;

Content Destination

1 click URL per window unit

3rd Party Trackers:

1×1’s and JS trackers accepted

NOTE:  1. Need to make sure to replace all “timestamp” macros with “{unixtimestamp}”. This will not be auto-replaced in the DSP like it normally is.

 

Pharma/ISI Native Ad Units (BETA)

If interested please discuss with your Bidtellect Sales Representative

R

Native Ad Unit

Pharma

Imagery

Recommended: 1200 x 1200
Minimum 300 x 300
<= 1MB

Logo (optional):
JPEG or PNG – transparent recommended
Minimum Size: 300 x 300

c

Headline

30 Characters or less

b

Description

150 Characters or less

|

Sponsored by

25 Characters or less

;

Content Destination

Each ISI Unit can have 1 click URL

ISI Field:

No Character limit

Format: HTML without CSS or JS

Option 1: Semi-transparent ISI: the ISI pane has a semi-transparent background and is overlaid over the bottom ⅓ of the image

Option 2: White-background ISI: image is cropped to ⅔ of original; the ISI pane is stacked below the image; ISI content displayed on a white nontransparent background.

 

3rd Party Trackers:

1×1’s and JS trackers accepted

NOTE:  1. Need to make sure to replace all “timestamp” macros with “{unixtimestamp}”. This will not be auto-replaced in the DSP like it normally is.

Branded Video Ad Units

R

Native Ad Unit

Native: Click to Play & Native Autoplay

Imagery

One 1200×900,non branded*Max file size:2MB

 

c

Headline

< 30 Characters

 

 

b

Description

< 140 Characters

 

 

|

Sponsored by

< 25 Characters

;

Content Destination

Article/Landing Page

I

Audio

Audio is supported. AAC audio is recommended.

p

Video Format

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

 

T

Video File Size

30MB for every 30 seconds

]

Video Aspect Ratio

(16:9) 1920×1080
1280×720 or
640×360

Outstream Video Ad Units

R

Native Ad Unit

Outstream & Vertical Video

p

Video Format

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

 

T

Video File Size

30MB for every 30 seconds

]

Video Aspect Ratio

Outstream:
(16:9) 1920×1080
1280×720 or
640×360

Vertical Video:
(9:16) Max: 1080 x 1920

}

Duration

Unlimited

I

Audio

Audio is supported. AAC audio is recommended.

VAST / VPAID

VAST

Max supported file size is 20 MB

VAST

Video format must be MP4

VPAID

We only accept Javascript VPAID tags

DCO: Dynamic Creative Optimization (BETA)

If interested please discuss with your Bidtellect Sales Representative

R

Native Ad Units

Recommendation Widgets

In-Ad Placements

In-Feed Placements

Imagery

JPEG or PNG files; Max file size 150kb; Ideal sizes are 1000×750 and 1200×1200 pixels, Images should be free of text.

(Optional but NOT recommended) Logo: JPEG / transparent PNG recommended
1:1 Ratio; Min size: 50 pixels high
Rec: 2 versions (light and dark)

c

Headline

<30 Characters

b

Description

<140 Characters

|

Sponsored by

<30 Characters

;

Content Destination

Article/Landing Page

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.

We accept Facebook images on our spec, so using your Facebook creative assets on Bidtellect’s platform requires no additional work on the advertiser’s part. Our platform does all the work.

If you’d like new creative assets, leverage our internal creative services team, [b]+studio, to optimize existing creatives from social, search or display and create custom content assets for Native.

AD TAG INSTRUCTIONS FOR IMPRESSION AND CLICK TRACKING

  • Bidtellect requires secure pixels (https://)
  • Bidtellect only accepts 1×1 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
  • IAS

SUPPORTED MACROS

  • Asset ID
  • Brand ID
  • Campaign ID
  • Creative ID
  • Customer Brand ID
  • Impression Data
  • IO ID
  • ParentPublisher ID
  • Placement ID
  • Product ID
  • Publisher ID
  • Publisher Name
  • Site ID
  • Timestamp

1×1 EXAMPLE
(Preferred)

https://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.
  • Bidtellect can do up to 5 per campaign.

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