Standard Banner | Flash | HTML | JavaScript | Dynamic HTML
Java | Streaming Media | Text Links | Redirecting Tags |
Java | Streaming Media | Text Links | Redirecting Tags |
| General Specifications: |
| . The rich media banners cannot alter any element of the page being served . Any action by the rich media banner must be initiated by any action taken by the user related to the banner and not to the page being served. . All actions taken by a rich media banner must be initiated by the user. The banner must also include a clear way on how to stop the action. . The banners should not request the user the download of any plug-in type or media planer to see the banner. The banner must include a script which would determine if the user has the required plug-in installed to see the banner. . All the rich media banners must be accompanied by an alternate .gif file for those users whose browsers cannot show the rich media banner. . All banners must launch the destination URL in a new window. . The destination URL can only be launched if the user has previously clicked the banner. . The name of any sent file cannot have spaces or accents. . It is recommended for the rich media banners not to be served by a third party. |
| Standard Banner |
| Delivery Time: All the standard banners (gif, animated gif, jpeg) must be delivered at least one day in advance in order to identify, inform and solve any technical problem. | |||||||||||||||||||||
| Technical Specifications: | |||||||||||||||||||||
. The images can only be in .gif format . Alternative text: 50 characters maximum including spaces and punctuation . There are no restrictions in the number of loops of an animated image |
|||||||||||||||||||||
| Flash |
| Delivery Time: All Flash banners must be delivered at least 5 days in advance to identify, inform and solve any technical problem. A backup GIF or JPG image must be supplied. | ||||||||||||||||||||||||||||||
| Technical Specifications: | ||||||||||||||||||||||||||||||
. All Flash banners must include a clickTAG (script to count the clicks during a campaign) in the Flash code in order to track user clicks. The correct clickTAG to be placed on the Actions for the Button is: on (release) { getURL(_root.clickTag, "_blank"); } . All click URL must have a TARGET attribute with the "_BLANK" value. . All Flash banners must include the "sniffer" code to detect if the user has the required plug-in to see the Flash files and to serve the alternative .gif banner to those that do not have the Flash plug-in. . The maximum weight of the alternative .gif file is the same one as for the standard banners, depending on the size. . There are no looping restrictions for a Flash animation. . Flash version 6 is recommended . Frame rate: 18 fps is recommended |
||||||||||||||||||||||||||||||
| HTML |
| Delivery Time: All HTML banners require delivery of at least 3 days in advance in order to identify, inform and solve any technical problem. | |||||||||||||||||||||||||||||||
| Technical Specifications: | |||||||||||||||||||||||||||||||
. Maximum number of images calls: 5 . If the image is clickable the border must have a "0" value (border="0"). . The tables within tables are not allowed. (<TABLE><TABLE>.....</TABLE></TABLE>) . There will be only one level of tables for HTML banner. Mandatory attributes in the elements of a table:
. All the text attributes (font, size) must be specified "in-line". It is not allowed to use external style sheets. . The tags <HTML>, <HEAD>, <TITLE>, < META >, and <BODY> should not be included in the banner code. They can only be included in the pop-up or interstitial HTML file . All click-through URLs (via link, form, image, etc.) must include the TARGET attribute and the value "_ BLANK". . Specifications for the FORMS: - The <FORM> tag must be located just after the <TABLE> tag. - The FORM METHOD attribute must have the "GET" value. - All the INPUT elements must have the STYLE attribute assigned. - The URL TARGET attribute of the FORM ACTION must have "_BLANK". - The CGI files will not be located in the Terra servers. All CGI files must be processed in the customer's server. . Specifications for the POP-UPS and Interstitials: - Must be made up by an HTML file with the JavaScript code that launches the window, the pop-up HTML code and the .gif images. All files must be sent to Terra. - The window must offer the user the capacity to close it or minimize it. - The maximum frequency is 3 times per user. - The Interstitial HTML file must include a script code that automatically closes the window after 6 seconds (max.) of exposure - The Pop-Up HTML file must include a code for the window to move to a previous position specified by Terra . Specifications for the PPI Standard (120x90 pixels): - The PPI is made up by an HTML file and the .gif files of the header - Maximum number of destination URLs for a PPI: 4 - The destination URLs must be included in the HTML code with the TARGET attribute and the "_BLANK" value. |
|||||||||||||||||||||||||||||||
| JavaScript |
| Delivery Time: All the JavaScript banners must be delivered at least 5 days in advance to identify, inform and solve any technical problem. | |||||||||||||||||||||
| Technical Specifications: | |||||||||||||||||||||
. Number of images calls: 6. . The images that change due to any action by the user, a period of time or any other event must be pre-loaded to avoid delay for future calls. . Maximum number of pre-loaded images: 4. . The maximum weight of each of the loaded images cannot be over 2k. . The JavaScript banners cannot be served by a third party. . All code files and the images of the JavaScript banner must be sent to Terra. . The tags <HTML>, <HEAD>, <TITLE>, < META >, and <BODY> should not be included in the banner code. They should be included in the pop-up or interstitial HTML file. . The tags <SCRIPT></SCRIPT> should not be placed inside the <TABLE> </TABLE> tags. . The <SCRIPT> tags should have the following attribute-value pairs: LANGUAGE="JAVASCRIPT" and TYPE="TEXT/JAVASCRIPT". . The HTML tags (<!-- -->) should be used to hide the scripts from the browsers that do not read them. . Tags within tags <SCRIPT> are not allowed . . All scripts must function in the main browsers and versions: Internet Explorer 4.0 and superior and Netscape 4.0 and superior. . The scripts should alter o affect any element in the page where the banner is being served. . The script code should not be sent to a separate .js file. The HTML code and the script must be included in the same file. It is not possible to make calls to scripts located in another server (<SCRIPT SRC=...). . The JavaScript code must include the <NOSCRIPT> </NOSCRIPT> tags to serve an alternative .gif to those users whose browsers do not support the JavaScript. . The maximum weight of the .gif alternative file is the same than the standard banners, depending on the size. . When you click on the JavaScript banner it is not allowed to take any actions that would close the window where it is located. . All click-through URL must include the TARGET attribute and the "_BLANK value. |
|||||||||||||||||||||
| Dynamic HTML |
| Delivery Time: All DHTML banners must be delivered at least 5 days in advance to identify, inform and solve any technical problem. | |||||||||||||||||||||
| Technical Specifications: | |||||||||||||||||||||
. Maximum number of images calls: 6 . The images that change due to any action by the user, a period of time or any other event, must be pre-loaded to avoid delay in future calls. . Maximum number of pre-loaded images: 4 . The maximum weight of each of the loaded images cannot be over 2k. . The JavaScript banners cannot be served by a third party . All code files and the images of the JavaScript banner must be sent to Terra . The tags <HTML>, <HEAD>, <TITLE>, < META >, and <BODY> should not be included in the banner code. They should be included in the pop-up or interstitial HTML file . The tags <SCRIPT></SCRIPT> should not be placed inside the <TABLE> </TABLE> tags. . The <SCRIPT> tags should have the following attribute-value pairs: LANGUAGE="JAVASCRIPT" and TYPE="TEXT/JAVASCRIPT". . The HTML tags (<!-- -->) should be used to hide the scripts from the browsers that do not read them . Tags within tags <SCRIPT are not allowed . All scripts must function in the main browsers and versions: Internet Explorer 4.0 and superior and Netscape 4.0 and superior . The scripts should alter o affect any element in the page where the banner is being served . The script code should not be sent to a separate .js file. The HTML code and the script must be included in the same file. It is not possible to make calls to scripts located in another server (<SCRIPT SRC=...). . The JavaScript code must include the <NOSCRIPT> </NOSCRIPT> tags to serve an alternative .gif to those users whose browsers do not support the JavaScript . The maximum weight of the .gif alternative file is the same than the standard banners, depending on the size . When you click on the JavaScript banner it is not allowed to take any actions that would close the window where it is located . All click-through URL must include the TARGET attribute and the "_BLANK value. . Specifications for the layers or DHTML banners located by blocking the page content where they are served: - if the banner moves on the page where it is served, the maximum size is 80x80 pixels. - if the banner does not move, it must disappear after 6 seconds (maximum) exposure - the maximum number of pages where a layer can be segmented: 5 . If a banner expands, it should only be when the user clicks or when the mouse moves over the banner. Once the banner expands, it must be close: or when the mouse moves outside the banner, or when clicking over any button clearly advising that it "closes" the expanded part . Specifications for the expanded banners that display because the user moves the mouse over the banner: - Maximum size of the displayed banner: 468x90 or 120x90 pixels. - The expanded part of the banner must disappear when the user moves the mouse outside the banner. - Maximum number of pages where a DHTML expanded banner can be segmented: 5 . Specifications for the expanded banners that display because the user clicks over the banner: - Maximum size of the displayed banner: 468x90 or 120x120 pixels. - The expanded part of the banner must disappear when the user clicks over the expanded banner. - Maximum number of pages where a DHTML expanded banner can be segmented: 5 |
|||||||||||||||||||||
| Java |
| Delivery Time: All JAVA banners must be delivered at least 5 days in advance to identify, inform and solve any technical problem. | |||||||||||||||||||||
| Technical Specifications: | |||||||||||||||||||||
. Maximum number of .class files: 4. . Maximum number of images calls: 4. . Terra requests that the click URL to track users clicks should be passed as a parameter. The click URL must be specified by tag <PARAM>. . All click-through URL must include the TARGET attibute and the "_BLANK" value. . The dynamic changes in the banner must affect the banner only. No changes must affect the page elements where the banner is served. . If the banner includes audio, it must be initiated when a user clicks. The audio should not begin playing when the banner is served or when the user moves the mouse over the banner. The banner must have a button clearly indicating that the audio will stop playing. . The clips with audio should not have looping. . All JAVA banners must have a sniffer code to detect if the user is JAVA, if not, an alternative .gif banner must be served, with a maximum weight of 12 K (for the 468x60 ones). . If the banner expands (expanded banner), it must happen only when the user clicks or moves the mouse over the banner. Once the banner is expanded, it must close: or when the mouse moves outside the banner, or clicking over a button that clearly specifies that it "closes" the expanded part. . Specifications for the expanded banners, displayed when the user moves the mouse over the banner: - Maximum size of the displayed banner: 468x90 or 120x90 pixels. - The expanded part of the banner must disappear when the user moves the mouse outside the banner. . Specifications for the expanded banners, which display because the user clicks over the banner: - Maximum size of the displayed banner: 468x200 or 120x200 pixels. - The expanded part must disappear when the user clicks over the expanded banner. |
|||||||||||||||||||||
| Streaming Media |
| Delivery Time: All rich media banners require delivery of at least 5 days in advance to identify, inform and solve any technical problem. |
| Technical Specifications: |
| . The maximum weight of the alternative .gif file is the same one as for the standard banners, depending on the size . Maximum duration of video: 20 sec. . Size of "wipe" videos: 240x180 pixels . All Streaming Media banners must include the "sniffer" code to detect if the user has the required plug-in to see the Streaming Media files and to serve the alternative .gif banner to those that do not have it. . The maximum weight of the alternative .gif banner is 12 K. . If the banner includes video or audio, it must be initiated when the user clicks. The video or audio should not begin to play when the banner is served or when the user moves the mouse over the banner. The banner must have a button clearly specifying that the video or audio will stop playing. |
| Text Links |
| Delivery Time: All co-registration require delivery of all the creative elements (opt-in text, image, and email) of at least 2 days in advance in order to identify, inform and solve any technical problem. | |
| Recomendamos modules (homepage and other channels) | |
Texts: Maximum 50 characters of text, including spaces. All capital letters prohibited. Suggest a call to action vs. your company's name. |
|
| Ofertas module (homepage) | |
Texts: Maximum 100 characters of text, including spaces. Image Pixel Size: 50x50 pixel graphic, max weight 2K, gif or jpg only. |
|
| Co-registration (registration pages) | |
Texts: Maximum 250 characters of text, including spaces. Image Pixel Size: 81 (horizontally) x 33 (vertically). Email Drop to Opt-in Users: The client can choose whether to have the email sent by them or by Terra. If we are to send the email, the client should provide us with the Subject line, body of the email and URLs if hyperlinks are present (3 maximum). Emails are sent daily at midnight and the client will receive a weekly report that explains how many emails were sent and the CTR. Reporting & FTP: The opt-in information is delivered to the client via FTP and it is done weekly. However in special situations or exceptions we could arrange to have the FPT sent on a daily basis depending on the needs of the client (i.e. if the client prefers to do the email drop instead of us). - The client can choose in what order they would like to have the fields (first name, last name, sex, etc.) listed. - All Terra needs in order to send the opt-in information is a technical contact on the client's side so that we can find out the correct protocol to send the reports to them. There is a separate excel report also sent on a weekly basis via email to the person responsible for the campaign that gives the following information: Number of impressions, opt-in users, conversion rate and email CRT (this last one if we send the email drop). |
|
| Redirecting Tags |
| Delivery Time: As agreed in contract of redirecting to third-party. |
| Technical Specifications: |
| . All redirecting codes must include tags that can be read by the main browsers versions (Internet Explorer 4.0 and superior and Netscape 4.0 and superior) . All rich media banners must include the click-command (URG generated by Dart to count the number of clicks during a campaign) in the HTML code or JavaScript that serves a third party, in order to track user clicks. The click command will be generated and sent by Terra to be included in the code served by the third party. . In case any "cache busting" system must be used, the way to implement it must be specified. . All redirect tags for Pop Ups should already include the open java script so that the Pop Up self spawns when implemented into Terra's ad-server. |
