Mobile Dynamic Halfpage Ad [Engl.]
Visualisation
Format concept
The Mobile Dynamic Halfpage Ad corresponds to the online desktop advertising medium "(Dynamic) Sitebar", which is displayed on mobile websites via an internal template.
The Mobile Dynamic Halfpage Ad is a large-scale advertising format that dynamically adapts to the respective smartphone screen width.
The advertising material is placed in the content in an eye-catching way and benefits from its visibility in the reading flow.
Live-Demo (to get a live demo for one of the other publishers below, append the parameter / ?sdmad=demo=mtmusd to the URL)
File format
- Physical (100% dynamic HTML file)
- Iframe Redirect
- Javascript Redirect
Dimensions & file size
- Size: 100% dynamic, the size of the advertising material must adapt in height and width, minimum size 120 x 600 pixels
- File weight: 150 KB initial + 300 KB reload
- File weight with video integration: 150 KB initial + 5 MB reload after user interaction
General information for advertising media with video/audio content
Videos
Mandatory information
Ads with video/audio content must, at any given time, include 3 well-visible and immediately clickable buttons (stylised or as text):
Stop
Pause/Play
Audio on/off
Technical specification | Specifications |
---|---|
Format | MP4, optional: WebM, and Ogg (siehe Browser Support https://www.w3schools.com/html/html5_video.asp) |
Frame rate | 25 FPS |
Max. file size of a video | Click-to-play: max. 5 MB Autoplay: max. 2,4 MB |
Integration | Use the video API of the browser to integrate videos. |
Loading options | Version Click-to-play Videos may only be started and played following a user action (clicking on a 'Play' button, swiping to expand the ad). The video file may only be downloaded when the user starts the video or when the 'subload of the ad' has been triggered. Automatic starting of the video without a clear action by the user is not permitted. Autoplay The video file may only be downloaded after the 'subload' of the advertisement has been triggered. The audio of the video must be set to 'Off' by default and may only be activated through user interaction. |
Max. length of spot | max. 30 s |
Repeated playback | Video may be played a maximum of 2x. Following that, the video must stop automatically. |
Delivery
- It is important to ensure that the advertising material does not want to break out of our container.
- 100% dynamic
Notes:
all trackings or redirects must be 100% SSL-compliant.
all ad tags/trackings to be used by us must contain the GDPR macros according to TCF v2.0 and all vendors used must be registered in the TCF v2.0 (Transparency and Consent Framework) of the IAB
Delivery deadlines: 3 days before start date, 5 days before start date in case of fixed placement. The delivery e-mail address can be found into the offer
Functionality
- The "stickyness" of the sitebar is ensured by Ströer, the tag itself must not contain this functionality
- The playout takes place via a safeframe, whereby the complete functionality is ensured by Ströer (sticky, positioning, scaling).
- It is important to ensure that the advertising material is https-capable and does not want to break out of our container.
- If it does try to break out, the following error will be thrown in the browser console:
- Blocked a frame with origin "null" from accessing a cross-origin frame
- This means that the script is trying to access the main page, which is prevented by the safeframe and therefore the ad is not displayed.
Visibility measurement
- If a visibility measurement is required, the visibility tracking must be delivered separately and should not be integrated into the redirect.
window.addEventListener('message', receiveMessage, false); function receiveMessage(event) { if (typeof event.data.msg === 'string' && event.data.msg.indexOf('StroeerScrollPostMessage') !== -1) { /* postMessage comes from Stroeer sitebar / following variables can be used: @param msg - @returns custom string which can be used to check postMessage source @param yPos - @returns the pixels the current document has been scrolled (pageYOffset) @param siteHeight - @returns the browser window's height (NOT including toolbars/scrollbars) */ } else { /* postMessage is not sent from the Stroeer sitebar */ } }
HTML5 Redirect
The delivery of an HTML5 advertising material must be done as an iFrame Redirect. When delivering, it must be noted that 3rd-party tracking pixels and click commands must already be integrated into the HTML by the creation process. The redirect must be 100% dynamic so that the advertising material can be played out as a multiscreen product.
General technical specifications and Tracking Guidelines
notes:
- all trackings or redirects must be 100% SSL-compliant.
all ad tags/trackings to be used by us must contain the GDPR macros according to TCF v2.0 and all vendors used must be registered in the TCF v2.0 (Transparency and Consent Framework) of the IAB
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.
This happens as an reaction to consumers are increasingly frustrated with ads that disrupt their experience, interrupt content and slow browsing.
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
The Ströer specifications have moved to stroeer.de.
Please find the most actual information and specifications regarding the Ströer Tracking Guidelines.
Click here: https://www.stroeer.de/en/planning-booking/specifications/online-ads/stroeer-tracking-guidelines/
Ströer Tracking Guidelines for advertisers and agencies on the use of trackings
1. Tracking in general
Up to five tracking pixels per creative have proven themselves as standard. This usually includes:
- two tracking pixels for impression tracking (media agency and technical service provider)
- a clickcommand
- a viewability measurement (e.g. meetrics)
- a market research pixel (e.g. GfK)
Ströer randomly checks the validity and amount of trackings. After prior consultation, a higher number of trackings can also be used.
All file sizes include all trackings.
2. personal data
Cookies and similar technologies which store and/or read out personal data on the user's device as well as further data processing must comply with the guidelines of the German Telemediengesetz, the EU General Data Protection Regulation (GDPR) and be listed on our vendor whitelist.
If there are any questions regarding the Ströer vendor list, please contact: vendorlist@stroeer.de
In particular (but not conclusively) the following types belong to it:
External tracking pixels, which analyze and record user behavior and, if desired, compare it with a downstream database on the customer side, must be explicitly released by Ströer before the start of a campaign. This includes any of the following pixel types:
- Ad Verification (reading the environment)
- Targeting quality (testing the effectiveness of the used targeting)
- User profiling (collecting profile data)
- Third party retargeting (re-targeting of users outside our network via external pixels)
3. tracking service providers (vendors)
All technical service providers (vendors) which will be used by agencies and advertisers must be registered in the TCF v2.0 (Transparency and Consent Framework) of the IAB and listed on our vendor whitelist.
If there are any questions regarding the Ströer vendor list, please contact: vendorlist@stroeer.de
4. Consent-Signaling for direct campaigns
For all cookies and similar technologies that are used in the context of the direct campaign on our portfolio, the necessary GDPR macros for the vendors used must be transmitted to us.
In order for us to be able to recognize/find these GDPR macros, we need to know at least 5 working days before start of a campaign how and where these GDPR macros will be implemented in the redirects, scripts, iframes and/or any other tracking.
All adtags/redirects/trackings to be used on our portfolio must contain these GDPR macros.
Note: Without this information we cannot ensure that direct campaigns can go live.
5. Counting differences
Counting differences in delivered ad impressions, caused by the selective filtering of an external tracking pixel (e.g. ad verification pixel), will not be acknowledged by Ströer or billed in Ströer's favor without prior consultation, unless they can be proven by a validated data basis.
6. Bundesdatenschutzgesetz BDSG
the Bundesdatenschutzgesetz BDSG must be observed in any case
https://www.gesetze-im-internet.de/bdsg_2018/
7. Further use of collected tracking data
The use of the collected tracking data is exclusively for the booked campaign and limited to the booked period in our network.
Any further use or sale of the data to third parties is prohibited.
© 2022-2023 - Ströer Media Solutions - https://www.stroeer.de