Vil du høre mere?
Menu
  1. Forside
  2. tv2.dk - adds
  3. Specs

Specs for tv2.dk

Specifications in general

 

The specifications described on this page are based on Danske Medier's standards, which can be found at the following address: https://danskemedier.dk/FINDSVAR/RAMMEAFTALER-VEJLEDNINGER-ORDNINGER/

They should be seen as guidelines, and TV 2 can therefore not guarantee that banners made within Danske Medier's guidelines will be able to run on tv2.dk. The guidelines should not be seen as absolute, and TV 2 may at any time reject material or require it to be changed to match TV 2's 'look and feel'. 

The below specifications describe the banner formats sold on TV 2's digital platforms, including direct sales and programmatic (RTB). 

Sizes and processor usage: Banners must not increase CPU usage by more than 5 percentage points. This is especially a problem with flash banners. It is continuously being assessed whether banners are too heavy in loading time. If they significantly delay the loading of the page, we reserve the right to stop running the campaign. 

As the Google Chrome browser will auto-block banners made in Flash from September 2015 due to resource consumption, TV 2 recommends using HTML5 for the production of animated advertising material. Read more about the blocking here. 

Banners made in Flash (.swf) will not run on TV 2's digital platforms as of September 2016. 

Third-party banner tags TV 2 supports most third-party tags used by media agencies and large direct clients. If in doubt, please contact banner@tv2.dk Material/banners must always be sent to: tv2trafficdigital@tv2.dk 

CSS The banner must not be positioned with inline CSS. TV 2 positions the banner. Z-index must not be placed on the banner. TV 2 will manage. 

JavaScripts and placement in the DOM structure The banner must not contain scripts that interact with other elements on the page, thus destroying TV 2 content. It is important that wmode is set to transparent. The banner must be inserted relatively in the DOM structure so that it settles in the DIV where we call the banner. This means that it must not be placed directly under <BODY>, for example. Expand must expand and collapse with mouse-over / mouse-out or click, and navigation on the page must be possible afterwards. 

TV 2 uses the Google Ad Manager Ad Serving system to manage banner ads. 

A landing page link/URL must be delivered to all banners. If HTML banners are delivered, either a clear clickTAG feature must be specified in the material, or an iframe parameter in which we can send a click-redirect. If you have any questions about this, please contact tv2trafficdigital@tv2.dk 
 
A maximum of 5 different creatives can be delivered per format. If you want a campaign with more creatives, please contact tv2trafficdigital@tv2.dk for further agreement. 

Digital campaigns must be booked at least 5 working days before the beginning of the campaign to ensure timely execution.  

Banners/third-party tags must be submitted well in advance, at least 2 working days before the beginning of the campaign. If the banner is not submitted on time, tv2.dk cannot guarantee that it will work at the beginning of the campaign. 

 

Subject to change without notice - including printing errors, price changes and items being out of stock.  

Animations and loops 

 

  • Ads may loop a maximum of 3 times. The maximum total animation time is 45 seconds - regardless of the number of loops. 
  • Animations before user interaction (in the form of clicks or mouse-overs) must be written in CSS3 Transitions, Transforms or Animation – or with GSAP libraries hosted on Cloudflare CDN called as: 

<script src=”https://cdnjs.cloudflare.com/ajax/libs/gsap/latest/TweenMax.min.js”> 

</script> 

  • Non-GSAP JavaScript animations are not allowed before user interaction in the form of clicks or mouse-overs. 
  • The framerate in animations in banners is limited to a maximum of 18 fs 
  • No processor-heavy animations before user interaction in the form of clicks or mouse-overs. 
  • Banners must not contain continuous, rapid "stroboscopic" animations of graphics, text, colours or background elements. 

Apps

 

TV 2 Nyheder

Platforms: iOS + Android 

Formats: 320×160, 320×320, 728x90

 

TV 2 Sport

Platforms: iOS + Android 

Formats: 320×160, 320×320, 728x90

 

Subject to change without notice - including printing errors, price changes and items being out of stock. 

 

TV 2 Vejr 

Platforms: iOS + Android 

Formats: 320×160, 320×320, 728x90

 

TV Tid

Platforms: iOS + Android 

Formats: 320×160, 320×320, 728x90 

Click tracking 

 

If you choose to code your banners yourself, you can follow these guidelines: 

Clicktags – HTML If HTML banners are submitted, either a clear clickTAG feature must be specified in the material or an iframe parameter in which we can send a click-redirect. If this is not specified, we cannot guarantee that we can count clicks on your campaign. If you have any questions, please contact banner@tv2.dk 

 

Example of inserting a click tag in an HTML banner: 

Insert the following script in the <head> tag of the banner: 

<script type='text/javascript'> 
var clickTag = 'indsæt Click-URL her'; 
</script> 

The script specifies an empty clickTag. 

Find the feature that is linked to the user's click event. 

Often you can find it by searching for "window.open". 

Now replace the URL in this click feature (window.open feature) with one that calls the clickTAG. Do as follows: 

window.open(“http://www.koldingstorcenter.dk”,”_blank“); 

Replace with: window.open(window.clickTag); 

Your banner will now call the URL that the media sends along when the banner loads – and Google DFP will be able to count clicks on the banner.  

More information is available here: https://support.google.com/dfp_sb/answer/7046799#clicktagguideline

 

Subject to change without notice - including printing errors, price changes and items being out of stock. 

Custom fonts

 

It is recommended that you avoid using custom fonts or only embed the characters used in the banner. 

Note: If a complete font library is called, the 100 kB limit for a banner will be quickly reached. 

 

Subject to change without notice - including printing errors, price changes and items being out of stock. 

Iframes  

 

HTML banners need to be tested to work in frames as they are often loaded into the media's ad server using one. 

Banners must not contain scripts that interact with other elements on the page and risk destroying or in any way altering the content of the page. 

 

Subject to change without notice - including printing errors, price changes and items being out of stock. 

Scrolling and mobile banners

 

Mobile banners must not block vertical scrolling as this often leads to misclicks and is a nuisance to users. 

Never use touchstart as an alias for clicks in mobile banners as touchstart will be activated when the user scrolls. 

 

Subject to change without notice - including printing errors, price changes and items being out of stock. 

Server calls

 

The number of server calls from a banner is kept to a maximum of 18 calls at initial load and a maximum of 15 additional calls at polite load in order not to slow down site performance unnecessarily. 

It is further recommended to place as much content as possible directly in the banner code and not in files that need to be downloaded first. 

To minimise server calls, all external graphics should be sprited as much as possible. 

 

Subject to change without notice - including printing errors, price changes and items being out of stock. 

SSL

 

Banners must be HTTPS-/SSL-compatible banners. 

Note: iOS 9 means that you cannot mix HTTP and HTTPS calls in ads. In addition, many ad servers now only load ads via HTTPS, so banners that call content via the HTTP protocol risk being blocked completely or only appearing partially. 

 

Subject to change without notice - including printing errors, price changes and items being out of stock. 

 

Video og audio 

 

Streaming video in banners may use autoplay to the extent that it complies with rules on weight and loading procedure - NOTE: Do not use autoplay on mobile phones/tablets.  

Do not start video playback with audio on autoplay. 

Streaming audio in banners must be user-activated on mouse-over and must have a one-second delay on start. Audio must stop on mouse-out. If clicks are used instead, there must be a distinct mute button. 

The medium is not responsible for hosting streaming unless explicitly agreed otherwise in advance. 

Streaming in banners may take up a maximum of 10 MB once the user has performed an active action. 

If the banner contains audio, there must be a clear stop/mute button. 

 

Subject to change without notice - including printing errors, price changes and items being out of stock. 

Weight 

 

Regardless of the format, the banner can download a maximum of 100 kB with the following exceptions: 

  • The limitation applies to the initial load. Data retrieved via polite load is not included in the 100 kB calculation. 
  • If a weight heavier than 100 KB is needed, use polite-load (Maximum 1 MB). This means that it can only be loaded at the browser event onload. 
  • Loading libraries from the below frequently used CDN services does not count towards the 100 kB limit. The following libraries are allowed: 
  • GSAP from Cloudflare 
  • The CDN libraries must be retrieved via HTTPS - even if the website or banner is only in HTTP. 
  • Data called after user interaction does not count towards the 100 kB limit. 

 

Subject to change without notice - including printing errors, price changes and items being out of stock.