General information
Information on general specifications and delivery of ad material.
Specifications
Technical specification | Specifications |
---|---|
Protocol | All components of the ad, especially tracking pixels and external ad-server systems (redirects), must be invoked using the HTTPS protocol. Using HTTP results in tracking differences. |
Load | On the side of the user, the presentation of the ad-media may not generate more than a 30% CPU load increase. |
File size | The maximum file size of an ad takes into account all files related to the ad, including all common libraries (e.g.: jQuery, Adobe Edge). Calculation of the total size takes place following compression of all files through GZIP. |
Requests | The maximum numbers of requests are 15 for the Initial Load and 85 for the Sub Load. |
Audio/Video | This content may be launched only following interaction of the user with the ad. The user must be able to control the playback of this media at any given time using control elements in the ad. |
Expansion/interaction | When using interactive and/or expanding surfaces in your ad, these may be launched only following interaction of the user with the ad. We will automatically include an easily visible Close button in your ad. |
GDPR Guidelines | In general we follow the technical specifications for the GDPR Transparency & Consent Framework. Examples for a general implementation (Javascript) : https://github.com/InteractiveAdvertisingBureau/Consent-String-SDK-JS |
Functionality | Please ensure that the creative redirects don't cause any javascript errors. For example 404 or synthax errors. |
Heavy Ad Interventions in Google Chrome | With Chrome 86, Google starts blocking ads that are resource-heavy and use an egregious amount of CPU or network bandwidth. In order to avoid such a blockage of the creative we recommend to consider the restrictions/guidelines from Google: https://developers.google.com/web/updates/2020/05/heavy-ad-interventions |
Delivery
Technical specification | Specifications |
---|---|
Delivery timeframe | 3 days prior to start of the campaign |
Protocol | HTTPS always required |
Audio and video content | allowed, launch by user action only (MouseOver) |
Expansion/interaction | allowed, launch by user action only (MouseOver) |
CPU load | max. 30% increase in load |
Deliver all ads to the following email addresses:
Agency group | Email address |
---|---|
Add2 | ops-add2@stroeerfrankfurt@stroeer.de |
Independent agencies | ops-agency@stroeer.de |
Agency2 | ops-agency2@stroeer.de |
Crossmedia | |
Dentsu | ops-dentsu@stroeer.de |
Direct clients | ops-direktkunden@stroeer.de |
Group M | ops-groupm@stroeer.de |
Havas | ops-havas@stroeer.de |
MGMP | ops-mgmp@stroeerfrankfurt@stroeer.de |
Omnicon | ops-omnicom@stroeer.de |
Performance Media | ops-performancemedia@stroeer.de |
Pilot | ops-pilot@stroeer.de |
Publicis | ops-publicis@stroeerfrankfurt@stroeer.de |
PPV | ops-ppv@stroeer.de |
AcceptableAds
Note |
---|
Always include the following information in your email (including for follow-up questions and/or subsequent changes to ads):
|
AcceptableAds is a programme of some AdBlocker providers that permits ads subject to specific quality guidelines and in spite of an AdBlocker being active.
The following information only applies if you have explicitly ordered a product that participates in the AcceptableAds programme.
Follow this link to learn more about the AcceptableAds programme.
Technical specification | Specifications |
---|---|
Ad formats | Only IAB Universal Ad Package + HalfpageAd: Leaderboard, Skyscraper, Widesky, Medium Rectangle, Halfpage ad possible |
animations/videos | not allowed, ads must be completely static (no moving images) |
sound | not allowed |
loading indicator | not allowed |
Media guidelines
Information on formatting guidelines of file sizes, HTML5, instream video.
File size
Technical specification | Purpose |
---|---|
max KB "Initial Load" | see format specifications |
max KB "Subload" | 2 x KB of "Initial Load" |
max. KB "User Initiated Load" | unlimited |
Guidelines on the loading procedure
Info |
---|
It is customary in the industry that all ads can use 3 points in time to load their files: "Initial Load", "Subload", "User Initiated Load". At each of these points, the ad can load a limited amount of data. These limits depend on the format to be served, larger-scale formats have higher limits. |
Loading time | Information |
---|---|
Initial Load | Can be executed immediately upon loading the ad. Until the hosting website sends the "DOMContentLoaded", all loading processes of an ad are considered part of the "Initial Load". |
Subload | May be started one second (1000 ms) after the Browser Event "DOMContentLoaded" of the serving website (previously Polite Download). Usually includes the main portion of the ad (complex animations and images, interactive elements).The maximum file amount at this time is double the initial load (Initial Load x 2) and there is no limit on file requests. |
User Initiated Load | This is defined as the time when the user interacts with the ad (touch, click, mouse-over). On mobile devices, note that the ISP typically provides a limited data connection. This connection should be burdened to the lowest possible degree. The users whose connections are being burdened are your potential customers. |
HTML5
General
Technical specification | Specifications |
---|---|
Format | Delivery as index.html with complete HTML syntax (Doctype definitions, <head>, <body>, etc.). |
Scripts | Additional content (scripts, CSS, etc.) can be delivered in separate files. Optimise the number of additional files as far as possible and minimise each file. Each additional file loaded has an adverse effect on the performance indicators of your ad (decreased visibility, fewer clicks). |
External resources | When linking external resources, make sure that their servers permit cross-domain access. Additional information on cross-origin resource sharing (CORS) can be found here. |
ID-Definition | In order to avoid conflicts with other banners and the serving website, always use a name-prefix when defining CSS classes and element IDs. |
Display orientation | The orientation of the displaying device should be considered, and the ad should be optimised for "landscape" and "portrait" orientation. |
Tracking | The tracking/counting of user actions (except for clicks) through separate server must be conducted by the ad producer. If the IAS Tracking is used, the programming of the html document must pay attention to the implementation of IAS. The technical specifications of the IAS must be adhered to and we cannot assume any liability for their correctness. |
Motion sensors | Data from the motion and orientation of a mobile device may be read and used for the interaction of the ad but may not be used in a blocking capacity. Functions such as closing or minimising of ads should not be exclusively dependent on the motion of the device but must rather always be controllable through additional buttons / gestures. |
JavaScript
Technical specification | Notes |
---|---|
Preparation | Prior to loading JS libraries and frameworks (jQuery, ZeptoJS, etc.), you must check whether an instance of the framework has already been loaded and is active on the website. |
Framework | Use small, compact JS frameworks. Larger libraries such as jQuery are generally unnecessary and increase the data load of the ad. |
Code size | Minify your final JS code as far as possible. Use Minifier or similar tools so that your ad can be transmitted to the viewer as fast as possible. |
Variables | Generally, avoid using globally defined variables and functions and store these in a separate "namespace". |
document.write() | Using document.write() is not permitted. Ads using this method will be automatically blocked. |
Mobile formats | For mobile ad formats intended for display in an app we support the standardised API MRAID (Mobile Rich Media Ad Interface Definitions) of the Interactive Advertising Bureau (IAB). For access to mobile device functions, e.g.: Creating a calendar entry, the device must be MRAID compatible. |
Click measurement
You can measure clicks on your ad through the Ströer AdServer. To achieve this, a dynamic assignment of the link URLs must be enabled in the HTML5 ad.
You will find instructions for inserting the dynamic assignment, including code examples, in the public GIT repository of the Online Marketing Group (OVK) in the Federal Association for the Digital Economy (BVDW).
The instructions are supported by all German marketers. After the one-time integration, the click measurement works on all German websites with no further adjustments required.
When developing / testing your ad, you can simply pass the URL-encoded links (encodeURIComponent() ) to the call of your .html file.
ihrWerbemittel.html?clicktag1=http%3A%2F%2Fwww.ihreUrl.de&clicktag2=http%3A%2F%2Fwww.ihreAndereUrl.de |
---|
Animations
Technical specification | Specifications |
---|---|
Creation | Animations should be designed as resource-efficiently as possible. Avoid the overuse of transparency effects (opacity), or triggering "repaints" of a browser. See additional information on paint/repaint here. |
GIFs | Rather than simply hiding them, completely remove unused GIFs (e.g. loading animation) from the HTML tree. Hidden animations continue to burden the browser. |
Animations | Use the animation capacities of CSS3 (animation, keyframe, translate, etc.). Do not, under any circumstances, use animations through JavaScript' s setInterval() or setTimeout(). |
Images
Technical specification | Specifications |
---|---|
Formats | GIF, PNG, SVG, JPEG |
Pixel density | To display optimally on all devices, all images should be adjusted for HDPI. See additional information on screen sizes and pixel density here. |
Compression | The compression procedures/formats progressive JPEG / progressive PNG and SVG are perfect for maintaining a low data load of the ad in spite of HDPI. |
Amount | Use the triggering of server requests for small images very sparingly. If you want to use numerous small image files (icons, logos), these should either be loaded as CSS sprites or stored directly in the HTML as DataURI. |
Integration | In order to serve individual versions of images to the respectively correct device and/or at the respectively appropriate pixel density, we recommend using CSS3 image-set() or <img>'s srcset element (check browser support). |
Videos
Note |
---|
Mandatory information Ads with video/audio content must, at any given time, include 3 well-visible and immediately clickable buttons (stylised or as text):
|
Technical specification | Specifications |
---|---|
Format | MP4, optional: WebM, and Ogg (see Browser Support https://www.w3schools.com/html/html5_video.asp) |
Frame rate | 25 FPS |
Max. file size of a video | 5 MB |
Integration | Use the video API of the browser to integrate videos. |
Loading options | Videos may be loaded only following a user action or in the "sub-load" of the ad. As a rule, starting the video is permitted only following a user action (click on "play" button, swipe to expand). |
Max. length of spot | max. 30 s |
Repeated playback | Video may be played a maximum of 2x. Following that, the video must stop automatically. |
Instream video
Info | ||
---|---|---|
| ||
Find information on the delivery of instream ads (pre-/mid-/post-roll) here. A lead time of at least 5 business days prior to the delivery date of the ad applies. The email for the ad delivery should include the following information: Customer name, campaign name, campaign schedule, advertising medium, assignment of ads for individual placements and point of contact for questions.
Please note that if the delivery of ad content is delayed or does not meet the technical specifications, in order to achieve the contractually agreed goals Ströer Digital Media reserves the right to delay the campaign by the number of days that the delivery was late. |
General
Technical specification | Specifications |
---|---|
Delivery | As a video file or as 3rd party redirect via the VAST3.0 wrapper mechanics. When you provide a Redirect delivery, make sure that only a maximum of three redirects to subsequent AdServers are carried out. |
Max. length of spot | 30 s for a PreRoll, MidRoll and/or PostRoll ad |
Playback | The video material should start immediately in the first frame, empty frames at the beginning or end of the commercial are to be avoided. |
PreRoll, MidRoll & PostRoll | The following KPIs are counted by default via the ad server:
|
Physical delivery
Technical specification | Specifications |
---|---|
Format | Mandatory: MP4, optional: MOV, WebM, MPEG |
Conversion | H.264 |
Frame rate | 25 FPS |
Colour intensity | 32 bit |
Resolution | 1280x720 |
Aspect ratio | 16:9 |
Max. file size | 100 MB |
Max. length of spot | 30 seconds |
Audio / sound | Please observe loudness norm EBU R 128. The sound must be integrated in the video. |
Playback | The basic material should start immediately in the first frame; black images at the beginning or end of the commercial are not permitted. |
Components of the file delivery | Video, tracking pixel (no JS pixel) and click counters (Click Through Tracking Pixel) |
Note | Please send a download link for files > 10 MB. When booking TubeOne, only 3rd-party trackings from certified partners (https://developers.google.com/third-party-ads/adwords-vendors?rd=1) may be used. |
3rd-party delivery (VAST 3.0) as well as programmatic / real-time bidding on Ströer SSP:
Technical specification | Specifications |
---|---|
Format | MP4 is mandatory, additionally optional: MOV, WebM, MPEG (RTB bid responses must correspond to the MIME types displayed in the respective bid request) |
VPAID | Only VPAID JS upon request (please note that the range is limited when only a single VPAID format is delivered). IMPORTANT: The ad video may not be superimposed on the controls within the video player. Ad videos (e.g. PreRolls) must always include clickable buttons with Stop, Pause/Play, Audio on/off. |
Protocol | Deliver trackings and media files secured and non-secured. |
Resolution | Minimum 1024x756 (or comparable high-resolution format) and 640x360 |
Bit rate | < 800 kbps (Mobile / InApp) and < 1600 kbps (Desktop) |
Max. length of spot | 30 seconds |
Max. file size | 5 MB |
Audio / sound | Please observe loudness norm EBU R 128. The sound must be integrated in the video. |
Wrapper level | max. 3 |
3rd-party | On the basis of VAST 3.0 tag (Digital Video Ad Serving Template) via Doubleclick, Adform, Mediamind, Flashtalking, Adition etc. VAST guidelines according to IAB: www.iab.net |
Include Page | ||||
---|---|---|---|---|
|