Fullscreen Ad: Difference between revisions

From Technical Specifications
Jump to navigation Jump to search
No edit summary
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 2: Line 2:
|plattform=tablet
|plattform=tablet
|beschreibung=
|beschreibung=
|anlieferungStandard=10
|anlieferungStandard=15
|anlieferungSonder=
|anlieferungSonder=
|galerie=
|galerie=
Line 13: Line 13:
|typ=vertikal
|typ=vertikal
|bezeichnung1=Fullscreen Ad (Image)
|bezeichnung1=Fullscreen Ad (Image)
|teil1={{AnlieferungKombination|zeichen=|teil1={{Anlieferungselement|bezeichnung=Portraitmodus|abmessung={{Abmessung|w=1536|h=2048}}|format=jpg, png, gif*|gewicht={{Gewicht|w=2|typ=MB}}|anmerkung=If no HD formats are present, the delivery of standard formats is also permitted:<br />{{Abmessung|w=768|h=1024}}}}|teil2={{Anlieferungselement|bezeichnung=Landscapemodus|abmessung={{Abmessung|w=2048|h=1536}}|format=jpg, png, gif*|anmerkung=If no HD formats are present, the delivery of standard formats is also permitted:<br />{{Abmessung|w=1024|h=768}}}}}}
|teil1={{AnlieferungKombination|zeichen=|teil1={{Anlieferungselement|bezeichnung=Portraitmodus|abmessung={{Abmessung|w=1536|h=2048}}|format=jpg, png|gewicht={{GewichtStatisch|w=2|typ=MB}}|anmerkung=If no HD formats are present, the delivery of standard formats is also permitted:<br />{{Abmessung|w=768|h=1024}}}}|teil2={{Anlieferungselement|bezeichnung=Landscapemodus|abmessung={{Abmessung|w=2048|h=1536}}|format=jpg, png|anmerkung=If no HD formats are present, the delivery of standard formats is also permitted:<br />{{Abmessung|w=1024|h=768}}}}}}
|bezeichnung2=Fullscreen Ad (HTML5)
|bezeichnung2=Fullscreen Ad (HTML5)
|teil2={{AnlieferungKombination|zeichen=|teil1={{Anlieferungselement|bezeichnung=Fullscreen Ad (HTML5)|abmessung={{Abmessung|w=768|h=1024}}|format=HTML5|gewicht={{Gewicht|w=2|typ=MB}}|anmerkung=The ad has to react independently on an orientation change and to resize itself to the screen size of the new orientation {{Abmessung|w=1024|h=768}}.}}}}
|teil2={{AnlieferungKombination|zeichen=|teil1={{Anlieferungselement|bezeichnung=Fullscreen Ad (HTML5)|abmessung={{Abmessung|w=768|h=1024}}|format=HTML5|gewicht={{GewichtStatisch|w=2|typ=MB}}|anmerkung=The ad has to react independently on an orientation change and to resize itself to the screen size of the new orientation {{Abmessung|w=1024|h=768}}.}}}}
}}
}}
|besondereInformation=
|besondereInformation=
{{Baustein|titel=General|text=If the ad is bigger than the display, it is scaled down to ensure optimum presentation. If the display is bigger than the ad, the ad is centred on the display.<br />In the app offerings of the Quality App Package, the visibilities within an app may differ from the ad formats to be delivered. Depending on the booked app, the maximum ad area may be reduced by the status bar of the device.}}
{{Baustein|titel=General|text=If the ad is bigger than the display, it is scaled down to ensure optimum presentation. If the display is bigger than the ad, the ad is centred on the display.<br />In the app offerings of the Quality App Package, the visibilities within an app may differ from the ad formats to be delivered. Depending on the booked app, the maximum ad area may be reduced by the status bar of the device.}}
{{Baustein|titel=*GIF|text=No gif deliveries are possible for SZ Digital.}}
{{Baustein|titel=Orientation change and responsivity|text=Within the context of the aspect ratio, the ad must adapt responsively to the resolution of the user and react automatically to a change in orientation (vertical/horizontal view). It is generally not possible to block the orientation of the app from the ad itself.}}
{{Baustein|titel=Orientation change and responsivity|text=Within the context of the aspect ratio, the ad must adapt responsively to the resolution of the user and react automatically to a change in orientation (vertical/horizontal view). It is generally not possible to block the orientation of the app from the ad itself.}}
{{Baustein|titel=Video|text=Videos can only be integrated as streaming elements. Hosting within the app offerings is not possible.}}
{{Baustein|titel=Video|text=Videos can only be integrated as streaming elements. Hosting within the app offerings is not possible.}}
Line 26: Line 25:
{{Baustein|titel=Click buttons|text=If your ad contains multiple click buttons for external linking or internal user interaction, it is the responsibility of the creator to connect click processing to a corresponding element.}}
{{Baustein|titel=Click buttons|text=If your ad contains multiple click buttons for external linking or internal user interaction, it is the responsibility of the creator to connect click processing to a corresponding element.}}
{{Baustein|titel=Extension on smartphone apps|text=Campaigns are extended on the smartphone apps – and are served with broadband targeting.}}
{{Baustein|titel=Extension on smartphone apps|text=Campaigns are extended on the smartphone apps – and are served with broadband targeting.}}
{{Baustein|titel=HTML5 ads in SZ Digital|text=
|html5={{HTML5|erlaubt=ja|plattform=mobile|typ=JPG, PNG and HTML5-Zip-File|anmerkung='''In case of HTML5 delivery:'''<br />Due to differences in the technical specifications of the respective ads a uniform delivery of one file package is not possible. Please deliver separate ZIP files for each offer to: [mailto:banner@iqdigital.de banner@iqdigital.de]}}
<div class="warnung">All HTML ads for SZ Digital must be based on one of these templates: [https://sz-media.sueddeutsche.de/de/digital/downloads/sz_html_lad_programming_templates.zip Templates for SZ Digital] ([https://sz-media.sueddeutsche.de/service/downloads/180222_SZ_App_Spezifikationen_deutsch.pdf Technical Specifications SZ Digital] and [https://sz-media.sueddeutsche.de/service/mediadaten.html SZ mediadata overview]</div><div style="clear:both;"></div>
These specifications contain the following templates:
;Empty:template for liquid ads
;Resize:template for automatic scaling and centring for ads tailored to iPad size
;Video:demonstrates how videos have to be integrated so that they also function in the Android app.
====Please note the following in-house SZ Digital concepts:====
;File Preloader:The files to be loaded may not be loaded in the head section. Instead, there is a preloader that handles loading of the files. This preloader is already integrated in the templates.
;Callbacks:The life cycle of an ad is predefined by the three callbacks setupAd(), startAd() and stopAd(). The ad must implement these callbacks and behave accordingly.
:;setupAd():All files have been found by the preloader and the DOM has been fully loaded.
:;startAd():The user has swiped the ad page, and elements such as videos can now be started.
:;stopAd():The user has swiped out of the ad and the videos can now be stopped.
;Display sizes:As the ad is served on devices with widely varying display sizes, it should behave like a responsive/liquid webpage or, for example, treat the problematic devices separately via user agent (by displaying a fallback image or similar).
;Orientation change:The ad should be able to react to a change between portrait and landscape mode - via CSS media queries, for example.
;Video:Under iOS and Windows, videos can be integrated via the <video> tag. This does not work reliably with Android, which is why the native full-image player should be called via Javascript. Videos cannot be locally integrated on Android but must be streamed.
;SZVideo.openVideoPlayer(URL);:
}}
|html5={{HTML5|erlaubt=ja|plattform=mobile|anmerkung='''In case of HTML5 delivery:'''<br />Due to differences in the technical specifications of the respective ads a uniform delivery of one file package is not possible. Please deliver separate ZIP files for each offer to: [mailto:banner@iqdigital.de banner@iqdigital.de]}}
|3rdParty={{3rdParty|erlaubt=nein|plattform=tablet}}
|3rdParty={{3rdParty|erlaubt=nein|plattform=tablet}}
|agenturZaehlpixel={{AgenturZaehlpixel|erlaubt=nein|plattform=tablet}}
|agenturZaehlpixel={{AgenturZaehlpixel|erlaubt=nein|plattform=tablet}}

Latest revision as of 09:46, 31 January 2024

Schematic representation
Delivery
Wherever possible, please send the ads in ZIP file format via downloadlink to:

banner@iqdigital.de

Standard:15 working days before the insertion date


Technical data

Fullscreen Ad (Image)
Portraitmodus
Dimension:
1536 x 2048 px
File format:
jpg, png
Weight:
max. 2 MB
Annotation:
If no HD formats are present, the delivery of standard formats is also permitted:
768 x 1024 px
Landscapemodus
Dimension:
2048 x 1536 px
File format:
jpg, png
Annotation:
If no HD formats are present, the delivery of standard formats is also permitted:
1024 x 768 px
OR
Fullscreen Ad (HTML5)
Fullscreen Ad (HTML5)
Dimension:
768 x 1024 px
File format:
HTML5
Weight:
max. 2 MB
Annotation:
The ad has to react independently on an orientation change and to resize itself to the screen size of the new orientation 1024 x 768 px.


Formats of delivery:

as physical file

Delivery of JPG, PNG and HTML5-Zip-File is possible (see HTML5-Guideline).
In case of HTML5 delivery:
Due to differences in the technical specifications of the respective ads a uniform delivery of one file package is not possible. Please deliver separate ZIP files for each offer to: banner@iqdigital.de

as 3rd-Party-redirect

Delivery of 3rd-Party redirect is not possible.

Agency counting pixels

External counting pixel for impression tracking by the agency is not possible.

Special information for this ad format

General

If the ad is bigger than the display, it is scaled down to ensure optimum presentation. If the display is bigger than the ad, the ad is centred on the display.
In the app offerings of the Quality App Package, the visibilities within an app may differ from the ad formats to be delivered. Depending on the booked app, the maximum ad area may be reduced by the status bar of the device.

Orientation change and responsivity

Within the context of the aspect ratio, the ad must adapt responsively to the resolution of the user and react automatically to a change in orientation (vertical/horizontal view). It is generally not possible to block the orientation of the app from the ad itself.

Video

Videos can only be integrated as streaming elements. Hosting within the app offerings is not possible.

Swipe gestures

The HTML page may generally not contain any large-area or full-surface swipe actions (horizontal and vertical swiping). The only features of this type that are permitted are click actions and recognisable, closed, small swipe boxes that are integrated in the ad. The functionality must also already be guaranteed upon delivery.

Quality assurance

The ads are technically validated; any necessary changes must be made by the creator. Please tests the functionalities in advance on the relevant browsers. Final approval is only possible after a successful test in the app offering.

Click buttons

If your ad contains multiple click buttons for external linking or internal user interaction, it is the responsibility of the creator to connect click processing to a corresponding element.

Extension on smartphone apps

Campaigns are extended on the smartphone apps – and are served with broadband targeting.

Please always note the following:

eco ad® Label

If it is an eco ad® booking, the eco ad® label will be displayed on the ad as follows:

Size:
Width: 4% of the ad width
Height: calculated automatically (eco ad® label width x 1.74).

Position (distance from the bottom and right edges):
5 px from the bottom edge
5 px from the right edge

It is recommended not to place any logos, text, or other important elements in this area. For special advertising formats with backgrounds, the label is displayed exclusively on banners that are within the main page content. The background itself is not labeled.

SSL/HTTPS

All elements of a campaign and the creative must be HTTPS-compatible (see SSL conformity (HTTPS)).

Calculation of file size and loading phases

The max. size of the specified ad component and its allocation to the loading phase in question (initial load/subload) refers to the value after the files (HTML, CSS, script, libraries, graphics and other assets) have been gzip-compressed (see File sizes and loading phases).

Positioning

HTML, scripts and all components that form part of the ad presentation must remain in the ad iFrame tag of the marketer or the 3rd-party host and may not be positioned outside this tag. This means that no DOM insertion of ad components in the top window of the serving website is permitted.

Sound and animation

Ad creations must always be supplied with deactivated sound. Activation is only permitted based on deliberate interaction on the part of the user, and sound volume must comply with the loudness standard EBU R 128.
Animations should not exceed 30 seconds in total, looping is only permit within this time frame. It is important to make sure that these do not unnecessarily burden the processor of the computer.

In addition, since August 2020, the Google Chrome browser installs limits for ad resources (CPU load / loaded MBs) and will remove ads from the page that exceed these limits - "Heavy Ad Intervention".

An ad is considered heavy in terms of CPU load (defined by Chrome Browser),

  1. if the user has not previously interacted with it
  2. the ad scripting uses the main thread of the browser longer than 15 seconds in a 30-second window or in total longer than 60 seconds.


The technical specifications of iq digital for the provision of advertising material shows, that the current product range is well positioned with regard to the possible exceeding of the limit for the Chrome browser. Please adhere to the specifications already upon delivery of the material in order to avoid corrections. iq digital accepts no responsibility for advertisements unloaded by the browser.

Video content

If this ad is not a recognised instream or outstream ad, it is only possible to implement video content with processing as a 3rd-party redirect (if approved) in the host-initiated subload (max. 4 MB in the stationary Web and max 2 MB in the mobile Web); max. length 15 - 30 seconds, frame rate: 25 images per second (FPS). Due to the high bandwidth usage of video-content, videos on smartphones are served with broadband targeting. iq digital reserves its right to add broadband targeting on other platforms as well if it is necessary. Sound may only start upon user interaction.

Click tracking

The ad server of the marketer can only correctly measure the clicks on an ad if a click-sensitive surface to forward the user to the client target site is implemented in the creative code and the insertion of ad server macros for the counting of clicks is possible. An external click command URL (3rd-party click tracking incl. target URL for forwarding to the client landing page) is also to be delivered as follows depending on how the ads are provided:

In the case of delivery of physical IMAGE files Delivery of 1 click command per ad motif; allocation incl. ad server macro as full-area click forwarding by iq digital ad server templating.
In the case of delivery of a physical HTML5 zip file Delivery of 1 click command per ad motif or multi-click area – allocation incl. ad server macro in HTML5 creative code by creative agency - see OVK standard procedure for the transfer of click tag and forwarding - HTML5 Guideline
In the case of delivery of a 3rd-party redirect See Click tracking – Delivery of 3rd-party resources

Other tracking tools

The serving of additional scripts/services for tracking/measurement of parameters other than those required for reporting on campaign performance (e.g. impression counting, click counting and coordinated ad verification) is not permitted and must be communicated and approved in advance. Please refer in particular to the requirements for compliance with data protection regulations and the ban on the creation of profiles from the utilisation behaviour of users on the websites of iq digital (General Terms and Conditions of Business). iq digital reserves the right to reject this kind of tracking. With eco ads®, the use of scripts or services to collect metrics other than those required for reporting on campaign performance is not permitted under any circumstances.

Ad identification and labelling

The labeling for the differentiation from editorial contributions is carried out for ads on in-page placements by the agency. Ads in the mobile environment should additionally be labelled in the ad itself by means of a -w- in one corner using a high-contrast font colour with a font size of at least 9pt. If such labelling is absent, iq digital reserves the right to integrate this labelling in the ad.

Conditions

iq digital reserves the right to approve each ad motif on the basis of a case-by-case decision. Ads that do not comply with the specifications, result in excessive reactance (CPU load of average user devices) or impair use and general performance of the pages must be corrected by the agency delivering the ad or can be rejected. The technical specifications of iq digital are subject to change. For this reason, technical specifications apply to the respective advertising order in the version valid at the time the advertising order is concluded.

IAB TCF 2.0 (GDPR macro)

iq digital only admits technology service providers (vendors) for the delivery of advertisements and coordinated tracking that comply with the rules of IAB-TCFv2.0 (Transparency and Consent Franemwork) and have been approved for inclusion on our customers websites (see: Overview technology provider).

The provision of tracking (e.g. tracking pixels) for advertising media or 3rd party redirects must be inclusive GDPR macro (gdpr and gdpr_consent). The creator of the tracking /3rd-party URL makes sure that these parameters are replaced with its ID value (GVL-ID), added only once and passed to services that expect and can handle them correctly.

URL parameter Corresponding Macro Representation in URL*
gdpr GDPR &'gdpr=${GDPR}
gdpr_consent GDPR_CONSENT_XXXXX -
XXXXX represents the numerical Vendor ID (Global Vendor List)
&gdpr_consent=${GDPR_CONSENT_XXXXX}
Example: &gdpr_consent=${GDPR_CONSENT_123} for Vendor ID 123.

Source: IAB GDPR-Transparency-and-Consent-Framework.

* The actual provision of the parameters within the final URL may differ from the above example with respect to separators (& or ;).