 |
SPECIFICATION (technical standard)ad products served by Lotos Technology Sp. z o.o.
Effective since 1 July 2008 (update 08.04.2009: I-2b, I-3, I-4, II-4-1, II-4-2)
Table of content:
I. General rules.
II. Special requirements for every form
- Banners
Graphic forms (banner 468x60, billboard 750x100, doublebillboard 750x200, skyscraper 120x600, box 300x250, button, bar, etc.), standard ads (not covering the page content, not shoving the service), maximal form size and weight define in boundary conditions , formats:
GIF/JPG, SWF - so in flash version up to 9 (however please remember about other specifications: if ad is supposed to be putted on Interia - flash version must be max. 7)
Ad must have implemented variable „clickTag” according to general rules:
on (release)
{
getURL(_root.clickTag, "_blank");
}
ATTENTION !!!
Forms destinated for other portals, should not be replicated if the only difference is content (name) of the variable! Additional form should only be created when the form is going to be emitted directly from portal – please refer to: general rules - point 2.
- Expands
Expand – interactive form of banner, which expands on mouseover, allowing to show additional content. Standard and maximal sizes compatible with boundary conditions of exact expand based on: GIF/JPG, SWF - flash up to ver. 7.
Ad should expand only on mouseover (also possible to autoexpand after site preload, but no longer than three seconds – after this period ad must automatically rollback to standard size). Creation must consist one file, and the implemented variables must enable to show/hide DHTML layer – depending which action takes place.
- For expanding: getURL(_root.doexpand, "_self"):
on (rollOver)
{
getURL(_root.doexpand, "_self");
}
- For rolling back to standard size: getURL(_root.dolittle, "_self"):
on (rollOut)
{
getURL(_root.dolittle, "_self");
}
- Form must have implemented „clickTag” variable:
on (release)
{
getURL(_root.clickTag, "_blank");
}
ATTENTION !!!
In case of expand skyscrapper – it is important to know where the form should expand (left or right), and according to this info prepare proper ad.
If form must be served directly from portals – it should be prepared according to portals specification.
- Scrollers
Scrolling ads are always visible in the same place of the user’s browser, independently of scrolling the page. „X” close button over the upper right corner of the ad. The ad may be “sent back” to the ad slot on the top of the page by clicking the “X” close button.
- Layers Form (BrandMark, TopLayer)
- BrandMark
Brandmark is a graphic advertisement served in an invisible layer on the top of the content of a web page. This kind of advertisement is similar to pop-up, but it is not limited by the standard pop-up window and may take any shape. Brandmarks may be moved within the browser window. They must include a non-clickable area with clearly labeled buttons: close (“X”), minimize and maximize. Maximal sizes and formats are to be found in table of boundary conditions or eventually in specification of landing portal, flash version up to 7.
- Form should contain closing cross, „X” – a button at a size of rectangle not small than 30x30px with implemented code:
on (release)
{
getURL(_root.adclose,"_self");
}
- Form should contain shrinking button, allowing to shrink to standard size:
on (release)
{
getURL(_root.dolittle,"_self");
}
- Form should contain button responsible for returning to standard size of ad with addition allowing to increase visible area to previous size:
on (release)
{
getURL(_root.doexpand,"_self");
}
- Form must have implemented „clickTag” variable:
on (release)
{
getURL(_root.clickTag, "_blank");
}
In this situation the ad launched from serving code cannot block the similar area up to the contour of bar. The visible size in minimalisation state can be controlled by variable parameters in serving code. The transparent area cannot be clickable and/or making content of the portal unclickable.
ATTENTION !!!
Button area cannot be placed at the bar area - form cannot link nowhere while dragging the bar. Important thing is to equip the form with graphic background (this kind of ads cannot be set up by a code).
- TopLayer
Toplayer - Graphic advertisement with animation and audio allowed. It „floats” above the web page. There are no restrictions concerning its position and size. Maximum weight: up to 40 kB. Duration of animation: maximum 15 seconds then auto close. Format: flash up to version 7. Sizes and exact display area are individually selected – depending on rules of landing portal. Everty ad must have “X” close button in the top right corner. Exact size and position are individually determined on a case-by-case basis.
- Form should contain closing cross, „X” – a button at a size of rectangle not small than 30x30px with implemented code:
on (release)
{
getURL(_root.adclose,"_self");
}
- Last empty frame of aminationmust contain:
stop();
{
getURL(_root.adclose,"_self");
}
- Form also should have implemented „clickTag” variable:
on (release)
{
getURL(_root.clickTag, "_blank");
}
ATTENTION !!!
Toplayer form cannot have clickable transparent area that disables to click links on portal. The form emitted on Onet.pl must be compatible with portal’s specification.
- Scroll Footer
Scroll footer - graphic advertisement with animation, recommended for Microsoft Internet Explorer web browser. Max. size – up to 10 kb. The scrolling effect code is placed in a form. Ad should also have implemented „clickTag” variable, allowing to monitor number of clicks:
on (release)
{
getURL(_root.clickTag, "_blank");
}
GIF/JPG form should be static – scrolling effect is enabled thanks to serving code.
ATTENTION !!!
Form for Onet.pl should be prepared according to portal’s specification.
- Pop-up i pop-under
Dynamic graphic advertisement displayed in a separate browser window when a user visits a web page. Maximum size: 336x280 pixels, weight: up to 30 kB, formats: GIF/JPG, SWF, flash version up to 9.
Pop-up is displayed over the browser window. Pop-under appears behind the browser window visited by a user, so the advertisement can be seen when a desired window is closed. Form must have “clickTag” variable:
on (release)
{
getURL(_root.clickTag, "_blank");
}
ATTENTION !!!
Ad designed for Onet.pl must be prepared according to portal’s specification.
- In-Stream
In-stream – advertising movie presented in media player’s window. It is published in Windows Media Player’s windows and it is presented before multimedia content (TV news, sport events, movies, video clips, etc.). This ad is unclickable. Important thing is to prepare proper forms for this ad:
- Onet.pl - In-Stream must be prepared basing on special materials (movie prepared in proper format):
- Allowed formats: mpeg, avi, wmv, mov, qt.
- Minimal FPS of movie: 20.
- Movie ratio: 4: 3 (standard): 320x240 pixels
- Maximal period of time: 10/20 or 30 seconds (depending on ad size)
- Properties for Interia.pl:
- Max. period of time for TV spot is 30 seconds
- SPOT (AVI or MPEG/MPEG4 in version for Windows, VHS, BETA lay.) at best quality available (up to 15s). This file is converted by INTERIA.PL into 3 stream-video movies (WMV) at three different sizes – for client’s acceptation.
- o2 - In-stream video (SPOT before videos on Smog.pl and Wrzuta.pl)
- Size: 400x300px (ideal resolution).
- Time period: up to 15 seconds (recommended time: 7-8 seconds).
- Weight: up to 40 MB (video will be compressed).
- File format: .flv, .mpg, .mov, .avi or .wmv.
- Wallpaper (watermark)
Wallpaper (watermark) – static graphic ad, situated behind the portal’s text and graphics, minimal area (logo) is set to be 80 pixels vertically and horizontally. Maximal weight - 7kB. Ad should be delivered in form of static picture (gif, jpg, tif, tga, psd or bmp).
- Spotlight
If campaign contains Spotlight codes (additional action codes), it is required to deliver:
- Exact URLs of sites, which are supposed to be monitored (incl. identificators in system) – up to 32 characters. Thanks to this it is possible to gather data while reporting (stats). Other info required: the name of country where the ad is going to be published (if different than Poland).
- Each code requires info about technology used: JavaScript, PHP, JSP, ASP, JAVA, Cold Fusion. JavaScript is treat as default (when no info is added).
ATTENTION !!!
Materials for spotlight must be sent 5 days before campaign’s launch.
- Mailing
Mailing – e-mail message (in HTML) to be send to users who use free mail accounts. Standard weight of advertising e-mail: 25 kB. General rules:
- Required parameters for mailing:
- Sender’s name
- Re:mail address
- Subject
- Content of mail
- Footer (signature)
- E-mails for testing (where tests should be send)
- All contents (images, texts, HTML files) must be delivered in one compressed package
- Links should be equipped with target=”_blank” parameter
- Polish fonts should be coded in Windows-1250 or ISO-Latin-2 (ISO 8859-2) standard; HTML must contain declaration compatible with proper coding standard
- Graphic background in CSS is unacceptable
- Mailing’s width: up to 600 px – important for mailings with unscalled table
- JavaScripts/frames/dynamic HTMLs/ActiveX are not allowed
- CSS styles cannot be saved in other file – implementation is only allowed in main HTML file. “Position” declaration is forbidden.
- HTML code cannot contain <TITLE> and <META> sign. That is different than declared in language code <!DOCTYPE ...>
- HTML must be 100% fault-free. Mailings in HTML should be compatible with W3C for HTML 4.01 (http://www.w3.org/TR/html401/). XML, XHTML / MS Word formats are not allowed.
ATTENTION !!!
Mailings for WP must contain:
-
All images must be presented via "cid:" parameter. So instead:
there must be:
-
In all links must not contain "http://" and be finished be "KLIK" parameter, so instead of:
III. Differences between portals’ specifications
- Variables, weights and flash versions
If campaign should be monitored by Lotos – all ads must be compatible with general rules - point 2. and be prepared according to Lotos’ specification! However, if some forms are supposed to be emitted on portals where serving codes cannot be used – in this condition ads must be compatible with landing portals’ specificaton.
If ordinary exposures (also on portals - onet, wp, interia, etc.) – forms should be compatible to spec of Lotos, however also minding landing portal’s spec.
Example – here are four placements:
| Portal |
Section |
Ad form |
Limitations |
| Gazeta |
SG(HP) |
Billborad 750x100 |
cap1xUU |
| Onet |
Kobieta |
Billborad 750x100 |
cap1xUU |
| Interia |
Kobieta |
Billborad 750x100 |
cap1xUU |
| Wp |
ROS |
Billborad 750x100 |
cap1xUU |
In this case only one form is required - Billboard 750x100, compatible with Lotos’ specification – form must be equipped with „clickTag” variable) and be compatible with all four portals. So the ad must be created minding the following:
- CPU load level compatible with Onet.pl
- Flash version 7 max (required for Interia.pl)
- …and the rest of requirements
In this condition it is not required to replicate the same form and waste time by preparing the very same ads that differ only by one variable/property. If case when one of the placements would be home page of Interia.pl – according to generali rules - point 2 ad should be prepared especially for Interia.pl, but only in this special condition. Other cases should be checked analogically and if there are some forms that raise doubts – please fell free to ask.
In case of differences – main point is that some of the portals are built in way that disables to emit forms based on external codes. It is a result of portal’s policy. The attention must be payed to the fact that usually variables are implemented, but sometimes all actions are based on old, function-based methods.
Summary/Comparison:
| Action: |
Portal |
| Lotos |
Portals |
Onet |
WP |
Interia |
O2 |
Gadu-Gadu |
| Click variable |
clickTag |
clickTsag |
click |
click |
clickTag |
clickTag |
clickTag |
| Expanding function |
doexpand |
doexpand or doexpand() |
adrozwin |
rozwinFORMA() |
ElementsHS_gora_srodek('hidden') |
doexpand() |
|
| Shrinking function |
dolittle |
dolittle or dolittle() |
adzwin |
zwinFORMA() |
ElementsHS_corner('visible') |
dolittle() |
|
| BrandMark: shrinking |
dolittle |
dolittle or dolittle() |
adzwin |
|
TLGoMin() |
|
|
| BrandMark: expanding |
doexpand |
doexpand or doexpand() |
adrozwin |
|
TLGoMax() |
|
|
| BrandMark: closing |
adclose |
adclose or onFinishedPlaying() |
adzamknij |
ukryjReklame() |
top_layer_close() |
onFinishedPlaying() |
|
| TopLayera: closing |
adclose |
adclose or onFinishedPlaying() |
adzamknij |
ukryjReklame() |
top_layer_close() |
onFinishedPlaying() |
|
| TopLayer period |
30 |
30 |
30 |
30 |
30 |
30 |
|
| CPU load in % |
30% |
30% |
30% |
30% |
30% |
30% |
|
| FPS/FramesPerSecond |
25 fps |
25 fps |
25 fps |
25 fps |
|
25 fps |
18 fps |
| Flasha version |
banery 9 inne 7 a polter 5 |
8 |
9 |
8 |
7 |
7 |
8 |
Lotos Technology Sp. z o.o. ul. Altowa 6; 02-386 Warszawa; Dział traffic: traffic@lotech.pl
Warszawa XIII Wydział Gospodarczy KRS: 0000303859; NIP: 951-225-14-19; REGON: 141392338; Kapitał zakładowy: 50.000,00
Onet.pl
|
|