Tekniske specifikationer

Transcription

1
Tekniske specifikationer
for online annoncering
Marts 2009
Version 1
Yderligere spørgsmål? Kontakt venligst din account manager eller besøg advertising.msn.dk
2
Velkommen
Tak for din interesse i at annoncere med Microsoft Advertising. Her i dokumentet finder du vores
retningslinjer for produktion og indsendelse af materialer.
Når vi modtager en pakke bannerannoncer bliver den sendt fra vores salgsafdeling til godkendelse i
et centralt system, hvorfra vi styrer alle de bannerne, der kører på vores netværk. Vores specifikationer
bygger på internationale branchestandarder. For at din kampagne bliver accepteret i systemet og vi
dermed kan yde den mest effektive service, så er det nødvendigt, at de bannere vi modtager fra dig
er inden for de specifikationer, som er angivet i dette dokument. Begrænsningerne er med til at sikre,
at brugerne får en god oplevelse på vores netværk, men der er stadig store muligheder for kreativ
frihed i udformningen af materialet – så imponér brugerne med levende annoncer!
Med venlig hilsen,
Louise Kloster
Trade Marketing Manager, Microsoft Advertising
PS. Enkelte afsnit (af mere teknisk karakter) af dette dokument er på engelsk, men vi har gjort vores bedste for at
holde informationerne på dansk.
Indholdsfortegnelse
Bannerspecifikationer, samlet oversigt 3
Retningslinjer for indsendelse af annoncemateriale
Clicktag 4
Bannere
300x250 Banner 6
728x90 Banner 7
180x150 Banner 8
234x60 Banner 9
160x600 Banner 10
930x180 Banner 11
Text links 12
Wallpaper/Site Skin
Expandable Bannere
4
13
300x250 Banner, Expandable 17
Windoes Live Messenger Tab
Personal Expressions 27
Video 47
Take-over med Eyeblaster 53
Games 55
In Game Advertising 58
Messenger TV 61
Nyhedsbrev 63
25
3
Bannerspecifikationer, samlet oversigt
Specifikationer
CPM
Dimensioner
(BxH)
Flash
GIF/JPG
728x90
50K
40K
300x250
50K
40K
180x150
50K
40K
234x60
50K
30K
160x600
50K
40K
930x180
50K
40K
Animation
Maks. 15
sekunder
og
uendeligt
loop
Levering
3. part
Clicktag
staves*
Lyd
Streaming
Bruger
aktiveret
Tilladt
(Skal være
tredjepartsstyret
via f.eks.
Eyeblaster)
Tilladt
Lyd
Streaming
Levering
3. part
Ramme
Clicktag
staves*
Bruger
aktiveret
Tilladt
(Skal være
tredjepartsstyret
via f.eks.
Eyeblaster)
Tilladt
1 pixel om
banneret
(Grå eller
sort er
foretrukket)
clickTag
Ramme
1 pixel om
banneret
(Grå eller
clickTAG
sort er
foretrukket)
MSDR
Dimensioner
(BxH)
Flash
GIF/JPG
728x90
30K
30K
300x250
30K
30K
160x600
30K
30K
180x150
20K
20K
234x60
15K
15K
930x180
30K
30K
Animation
Maks. 15
sekunder
og
uendeligt
loop
CPM Facebook
Dimensioner
(BxH)
160x600
Flash
30K
GIF/JPG
Animation
30K
Maks. 15
sekunder
og
uendeligt
loop
Lyd
Streaming
Levering
3. part
Ramme
Clicktag
staves*
Bruger
aktiveret
Tilladt
(Skal være
tredjepartsstyret
via f.eks.
Eyeblaster )
Tilladt
1 pixel grå
ramme om
banneret
clickTAG
*For uddybelse af Clicktag-begrebet se side 4
Dimensioner
Bredde x højde, målt i pixels.
Flash
Annoncer der indeholder Flash skal indeholde en SWF-fil,
samt en JPG eller GIF backup fil. Her er angivet størrelsen
på filen.
GIF/JPG
Her er angivet, hvor meget GIF eller JPG backup filen
højst må fylde.
Lyd
Lyd skal altid aktiveres af brugeren og må aldrig starte
automatisk.
Animation
Animation er begrænset til de første 15 sekunder. Det er
ikke begrænsning på, hvor mange gange materiale må
loope inden for de 15 sekunder.
Streaming & levering fra 3. part
Der er særlige regler for streaming. Se venligst side 5.
clickTAG eller clickTag
På CPM-annoncer er stavemåden ”clickTAG”.
På CPC-annoncer er stavemåden ”clickTag”.
På CPM (Facebook)-annoncer er stavemåden ”clickTag”.
4
Retningslinjer for indsendelse af annoncemateriale
Sammen med det indsendte materiale skal du angive følgende oplysninger:
•
•
•
•
•
•
Navn på annoncøren
Microsoft ordrenummer eller IO nummer
Startdato for kampagnen
Slutdato for kampagnen
Clickthrough URL (hvor skal bannerne linke hen?)
Annoncens rotation i procent (ved indsendelse af flere annoncer til samme placering)
Send alt annoncemateriale til din Account Manager.
Annoncerne skal overholde kravene i Microsofts ”Politik for accept af kreative elementer”.
http://advertising.microsoft.com/creative-acceptance-policy
Deadlines
Microsoft Advertising skal bruge 3 hele arbejdsdage til at teste og forberede standardindesendelser af GIF ,JPG og
Flash-filer. Sørg venligst for at indsende materialet i god tid før annoncens startdato.
Microsoft Advertising skal bruge 5 hele arbejdsdage til at teste og klargøre rich media-løsninger, dvs. rich media
leveret af tredjepart som f.eks. Eyeblaster.
BEMÆRK:
Alle elementer der ikke overholder specifikationerne sendes tilbage til revison, hvilket kan forsinke kampagnestart.
Hvis du har brug for yderligere information om diverse spcifikationer henviser vi til
http://advertising.msn.dk
Har du spørgsmål til indsendelse af annoncemateriale, skal du kontakte din account manager.
Clicktag
For at Microsoft kan håndtere annoncer med Flash-indhold korrekt, skal alle SWF-filer kodes med enten en ”getUrl”
kode eller en ”fscommand” (fscommand anvendes ved flere URL´er i samme banner). Dette er nødvendigt for at
Microsoft kan tracke annoncen helt præcist - hvis kampagnens URL er hardcoded i SWF-filen, vil Microsoft IKKE kunne
registrere klikkene.
Ved CPM kampagner
GetUrl-indstillingen konfigureres således:
On (release) {
getUrl(_root.clickTAG,,”_blank”)
}
Fscommand-indstillingen konfigureres således:
on (release) {
fscommand(”URL1”)
}
Ved CPC kampagner
GetUrl-indstillingen konfigureres således
On (release) {
getUrl(clickTag, ”_blank”);
}
5
Retningslinjer for indsendelse af annoncemateriale (fortsat)
Navngivning
Alle filer bedes leveret i henhold til følgende standard formatering:
• Navngivning: ”Annoncør_Kampagnenavn_Sprog_Størrelse_Version”
• Eksempel: ”Microsoft_Vistabusiness_DK_300x250_v01.swf”
”v01” står for version 01.
Streaming
Annoncer der benytter streaming skal overholde følgende specifikationer:
•
•
•
Streaming indholdet må godt aktiveres automatisk. Dog anbefaler Microsoft at streaming aktiveres af brugeren, da det giver den bedste brugeroplevelse.
Lyd skal altid aktiveres ved klik af brugeren og må aldrig ske automatisk.
Annoncer med streaming indhold skal indeholde en tydelig funktion, som brugeren kan benytte til at slå det til og fra.
Streaming kan afvikles på Microsoft netværket på følgende måder:
• Flash-filer hosted af Microsoft, hvor filerne henviser til en tredjepartsudbyder af streaming
via f.eks. Eyeblaster, Atlas etc.
• Tredjepart håndterer alt vedr. hosting-delen.
Levering fra tredjepart
Alle annoncer, som hostes af tredjepart, skal overholde Microsofts generelle specifikationer mht. Kb –begrænsninger,
animation, lyd, m.v.
Herudover rapporterer Microsoft ikke statistiske oplysninger om klik, som vedrører annonce-koder fra tredjepart (f.eks.
Flash som leveres af tredjepart, Adform eller andre)
6
300x250 Banner
Eksempel
2 5 0 pi x e ls
3 0 0 pi x e ls
300x250 banner
Specifikationer
300x250 Banner
Udbyder
CPM
MSDR
Dimensioner
(BxH)
Flash
GIF/JPG
300x250
50K
40K
300x250
30K
30K
Animation
Maks. 15
sekunder
og
uendeligt
loop
Lyd
Streaming
Levering
3. part
Ramme
Bruger
aktiveret
Tilladt
(Skal være
tredjepartsstyret
via f.eks.
Eyeblaster)
Tilladt
1 pixel om
banneret
(Grå eller
sort er
foretrukket)
(ved klik)
Clicktag
staves*
clickTAG
clickTag
*For uddybelse af Clicktag-begrebet se side 4.
Om lyd, animation, Flash, mv.
•
•
•
•
•
•
•
•
Alle elementer der ikke overholder specifikationerne sendes tilbage til revision, hvilket kan forsinke kampagnestart.
Lyd skal altid aktiveres ved at brugeren klikker på banneret med musen.
Hvis der bruges lyd, skal banneret indeholde en tænd/sluk-knap til lyden.
Animation i banneret er begrænset til de første 15 sekunder. Banneret må ikke loope eller animere efter de første 15 sekunder.
Hvis du sender annoncemateriale i form af Flash-filer, skal du for hvert bannerformat sende én SWF-fil, samt én GIF eller én JPG-fil (til brugere, der ikke har Flash installeret).
For at Microsoft kan håndtere annoncer med Flash-indhold korrekt, skal alle SWF-filer kodes med enten en
”getURL” eller en ”fscommand” kode (se side 4 for yderligere information)
Klik-destinationens URL skal åbne i et nyt browservindue.
Det kreative element skal have en ramme på 1 pixel (grå [nr. 666666] eller sort anbefales, men enhver farve, der tydeligt adskiller annoncen fra indholdet på hjemmesiden, kan anvendes).
Hvor lang tid inden skal vi have bannerne?
Deadline for levering er 3 hele arbejdsdage inden den dato, hvor kampagnen starter.
7
728x90 Banner
Eksempel
9 0 pi x e ls
7 2 8 pi x e ls
728x90 banner
Specifikationer
728x90 Banner
Udbyder
Dimensioner
(BxH)
Flash
GIF/JPG
Animation
CPM
728x90
50K
40K
Maks. 15
sekunder
og
uendeligt
loop
MSDR
728x90
30K
30K
Lyd
Streaming
Levering
3. part
Ramme
Bruger
aktiveret
Tilladt
(Skal være
tredjepartsstyret
via f.eks.
Eyeblaster)
Tilladt
1 pixel om
banneret
(Grå eller
sort er
foretrukket)
(ved klik)
Clicktag
staves*
clickTAG
clickTag
•
•
•
•
•
•
•
•
Deadline for levering er 3 hele arbejdsdage inden den dato, hvor kampagnen starter (5 dage for specielle formater,
f.eks. Eyeblaster).
8
180x150 Banner
Eksempel
1 5 0 pi x e ls
1 8 0 pi x e ls
180x150 banner
Specifikationer
180x150 Banner
Udbyder
CPM
MSDR
Dimensioner
(BxH)
Flash
GIF/JPG
180x150
50K
40K
180x150
20K
20K
Animation
Maks. 15
sekunder
og
uendeligt
loop
Lyd
Streaming
Levering
3. part
Ramme
Bruger
aktiveret
Tilladt
(Skal være
tredjepartsstyret
via f.eks.
Eyeblaster)
Tilladt
1 pixel om
banneret
(Grå eller
sort er
foretrukket)
(ved klik)
Clicktag
staves*
clickTAG
clickTag
•
•
•
•
•
•
•
•
f.eks. Eyeblaster).
9
234x60 Banner
Eksempel
6 0 pi x e ls
2 3 4 pi x e ls
6 0 pi x e ls
2 3 4 pi x e ls
234x60 banner
messenger klient
Specifikationer
234x60 Banner
Udbyder
CPM
MSDR
Dimensioner
(BxH)
Flash
GIF/JPG
234x60
50K
30K
234x60
15K
15K
Animation
Maks. 15
sekunder
og
uendeligt
loop
Lyd
Streaming
Bruger
aktiveret
Tilladt
(Skal være
tredjepartsstyret
via f.eks.
Eyeblaster)
(ved klik)
Levering
3. part
Ramme
Tilladt
1 pixel om
banneret
(Grå eller
sort er
foretrukket)
Clicktag
staves*
clickTAG
clickTag
•
•
•
•
•
•
•
•
f.eks. Eyeblaster).
10
160x600 Banner
Eksempel
6 0 0 pi x e ls
1 6 0 pi x e ls
160x600 banner
Specifikationer
160x600 Banner
Udbyder
Dimensioner
(BxH)
Flash
GIF/JPG
Animation
CPM
160x600
50K
40K
Maks. 15
sekunder
og
uendeligt
loop
CPM
Facebook
160x600
30K
30K
Lyd
Streaming
Levering
3. part
Ramme
Bruger
aktiveret
Tilladt
(Skal være
tredjepartsstyret
via f.eks.
Eyeblaster)
Tilladt
1 pixel om
banneret
(Grå eller
sort er
foretrukket)
(ved klik)
Clicktag
staves*
clickTAG
clickTag
*For uddybelse af ClickTag-begrebet se side 4.
•
•
•
•
•
•
•
•
f.eks. Eyeblaster).
11
930x180 Banner
Eksempel
930x180 banner
Specifikationer
930x180 Banner
Udbyder
CPM
MSDR
Dimensioner
(BxH)
Flash
GIF/JPG
930x180
50K
40K
930x180
30K
30K
Animation
Maks. 15
sekunder
og
uendeligt
loop
Lyd
Streaming
Bruger
aktiveret
Tilladt
(Skal være
tredjepartsstyret
via f.eks.
Eyeblaster)
(ved klik)
Levering
3. part
Ramme
Tilladt
1 pixel om
banneret
(Grå eller
sort er
foretrukket)
Clicktag
staves*
clickTAG
clickTag
•
•
•
•
•
•
•
•
f.eks. Eyeblaster).
12
Tekstlinks
Brugeroplevelsen
1.
2.
3.
Når et samtalevindue åbnes, forbliver tekstlink-annoncen der, indtil vinduet lukkes. Selv hvis det minimeres, bliver
den samme annoncør ved med at være der. Annoncen forsvinder først, når samtalevinduet lukkes
(ved at der trykkes på krydset).
Der foretages en ny annoncegenkendelse for hvert samtalevindue, der oprettes.
Annoncen bliver der lige så længe, som samtalevinduet er åbent.
Tekstlink Specifikationer
• Max 65 tegn inkl. mellemrum
• Klikdestinationen skal åbnes i en ny browser.
• Teksten må ikke bestå af udelukkende store bogstaver.
Reporteret Data
Annonceanmodninger og gennemklik.
Eksempel
13
Wallpaper/Site Skin
Creative Acceptance Policy
All creative must meet the requirements of the MSA Creative Acceptance Policy
Specifikationer
Wallpaper/Site Skin
Ad Type /
Ad Size
Initial Size
Download
Max Initial
File Size (GIF/JPG) Download File Size
Audio
Specifications/ Limit
Animation/
Looping Limit
Rectangle
300x250
300W x 250H
40K
40K
Allowed on user click only;
Duration: 15 sec
Allowed; Duration: 15 sec
Banner
728x90
728W x 90H
40K
40K
Allowed on user click only;
Duration: 15 sec
Allowed; Duration: 15 sec
Alt
Text Limit
65 char
65 char
Note(s):
• The product will launch out of either a Banner 728x90 or a Rectangle 300x250 and requires a 100% SOV of all ad
placements on the page.
•Above ad specs are the standard guidelines, placements can also accommodate:
o Expanding Rich Media
o In-Page Rich Media
o Float to Rectangle (Market/Channel Decision)
Ad Specifications
Note: Markets may offer user control for narrow or wide home page. For markets that allow for that option we
require dynamic functionality to deliver the appropriate experience.
1. MSA Skin format - Basic option:
A static wallpaper solution combining a 728x90 or 300x250 with a static wallpaper.
SPECIFICATIONS:
• 728x90 element: See above
•Wallpaper element:
o Narrow Page Dimensions: 1600 x 1050 with left and right segment at 410 x 1050 each, centre section left white at 780 x 1050
o Wide Page Dimensions: 1600 x 1050 with left and right segment at 309x1050 each, centre section left white at 981 x 1050
o
File size: 100k
o File type: Jpg
• 300x250 element: See above
•Wallpaper element:
o Narrow Page Dimensions: 1600 x 1050 with left and right segment at 410 x 1050 each, centre section left white at 780 x 1050
o Wide Page Dimensions: 1600 x 1050 with left and right segment at 309x1050 each, centre section left white at 981 x 1050
o
File size: 100k
o File type: Jpg
14
Wallpaper/Site Skin
Eksempel
2. MSN Skin format - Animating Flash option:
A 15 second animating wallpaper solution combining a 728x90 and/or 300x250 expanding ad.
SPECIFICATIONS:
•Animating Skin Element:
o Flash Version: Flash 9 and below*
o File Weight: 150k max
o 15 second maximum animation
o Down-level experience based on vendor requirements.
o Skin can be clickable or non-clickable – Market/Channel decision
• 728x90 / 300x250 element: Please reference the Expanding Rich Media spec.
15
Wallpaper/Site Skin
Eksempel
3. MSN Skin format – Interactive option:
SPECIFICATIONS:
3.1. Synchronized Element
•
Synchronization allowed between the 300x250 / 728x90 and the skin element.
o Please contact the RMV for specs
3.2. Video Element
• Video element: to be supplied at minimum dimension of 720p format (1280 x 720) – this allows for enough size to the 3 x segment layout. Format would best suit MOV file. Video also exported for the MPU at 300 x 250
• Video creative using 3 x cropped areas of the video to make one large viewing area on the page – utilizes 300 x 250 MPU with video plus Wallpaper background
o File size: 2.2 MB
o File type: Rich Media / Flash / Video
Other Specifications
•
Additional Features Available through the standard ad space:
o Polling
o Viral
o Games
• Audio must be user click-initiated and never automatic.
• Audio insertion into Flash file may begin no earlier than the second frame.
• If audio is used, creative must include an On/Off switch for users.
• All DHTML creative submissions must have an accompanying default graphic that is
shown to users who do not have IE 4.0 or higher
• Animation is limited to first 15 seconds, looping is unlimited within 15 seconds. Use animation carefully - Keep animation smooth and fluid, using slow motion and gentle fades. Fast and abrupt motion is highly irritating. Avoid experiences that ’break through’ the page or abuse the content.
• For detailed Flash guidelines, visit advertising.microsoft.com.
• Creative must feature a 1 pixel border (gray [#666666] or black recommended, though any color that clearly distin
guishes the ad from the content may be used).
• Click destination URL must open a into new browser.
16
Wallpaper/Site Skin
Certified Rich Media Vendors (TBD, examples below)
• Atlas
• Eyeblaster
• Flashtalking
Data Reported
Ad requests and click-through. Microsoft cannot guarantee 3rd party served creative reporting within the Microsoft
reporting system.
Data
Collection
•
•
•
•
•
•
Microsoft permits advertisers to collect user-provided personal information (for example, through web forms embedded in ads).
Advertisers may be required to modify ad units or provided additional disclosure in order to be acceptable for advertising on Microsoft sites.
Advertisers wishing to collect personal information within advertisements (according to specifications above) must follow these guidelines:
Clearly identify organization
Provide link to privacy policy (usually adjacent to the web form’s “submit” button)
Identify purpose for collecting information
Ad Submission Guidelines
All creative must meet the MSA Ad Submission Guidelines
17
300x250 Banner, Expandable
Eksempel
2 5 0 pi x e ls
3 0 0 pi x e ls
300x250 banner expandable, IKKE EXPANDED
3 0 0 pi x e ls
MAx
50
pi x e ls
( E x pand e d )
2 5 0 pi x e ls
ma x 2 0 0 pi x e ls
300x250 banner expandable, EXPANDED
Specifikationer
Dimensioner
(BxH)
300x250
Max 560x300 for
høfligt kreativt
element (expanded)
Filtyper der
Flash
Retning for
understøttes af (Alm. / Expanded) GIF/JPG Animation
udvidelse
tredjepart
Op,
ned,
højre,
venstre
Flash 6.0
Flash 7.0
Flash 8.0
50K / 100K
10MB for høfligt
kreativt element
(expanded)
40K
Lyd
(ved klik)
Maks. 15
Bruger
sekunder
aktiveret
(uendeligt og maks. 30
loop)
sekunder
Streaming
Maks.
30 sek.
Ramme
1 pixel (grå
eller sort
foretrukket)
Clicktag
staves*
on(release){
EB.Clickthrough();
}
Oplevelse for slutbruger
1.Bruger besøger en MSN-side med Eyeblaster Expandable Banner-script. Annoncen på 40 K indlæses på 300x250 anonncepladsen.
2. Flash-oplevelsen begynder og giver brugeren en stor medieoplevelse.
3. Hvis brugeren placerer musemarkøren på visse områder af annoncen, udvides et panel med tilbud om en ekstra stor oplevelse. Panelet er en del af den ”høflige download”, der opstår, når siden er indlæst, og det påvirker ikke sidens indlæsningstid.
4. Efter et fast tidsrum, eller når brugeren flytter musen væk fra annoncen, trækkes panelet tilbage til 300x250 annoncepladsen.
5. Hver gang brugeren flytter musen hen over annoncen, udvides panelet igen.
Rapporteret data
MSN: kun besøgstal. Eyeblaster: Annonceanmodninger og gennemklik.
18
Om lyd, animationer, mv.
•
•
•
•
•
•
•
•
•
•
•
Looping/genafspilninger skal initieres af bruger.
Lyd må ikke vare mere end 15 sekunder.
Lyd skal altid være brugeraktiveret og må aldrig være automatisk.
Hvis der bruges lyd, skal annoncen indeholde en on/off-knap til brugerne.
Alle indsendelser af DHTML-annoncer skal have en ledsagende standardgrafik, som vises til brugere, som ikke har IE 4.0 eller højere.
Animationer er begrænset til de første 15 sekunder, looping er ubegrænset inden for 15 sekunder. Brug animationer forsigtigt. - Hold animationen glat og flydende med langsomme bevægelser og blide overgange. Hurtige og bratte bevægelser er meget irriterende. Undgå visninger/oplevelser, som ’bryder igennem’ siden eller misbruger indholdet.
Flash-filer skal have indlagt en FSkommando i filen.
Hvis du sender flash-filer, så skal du for hvert banner sende en SWF-fil, samt en back-up GIF (eller JPG).
Det kreative element skal have en ramme på 1 pixel (grå [nr. 666666] eller sort anbefales, selvom enhver farve, der tydeligt adskiller annoncen fra indholdet, kan anvendes).
Klik-destinationens URL skal åbnes i en ny browser.
Det er en stor fordel, at teste bannerne inden du fremsender dem til os. Til dette formål kan det gøre det mere over
skueligt at lægge bannerne online på et testlink.
Panelkrav/-kontrolelementer
• Panelet må ikke gå mere end 200 pixel ud over venstre/højre kant i det primære kreative element og 50 pixel ud over de øverste/nederste kanter.
• Paneler må kun udvides, når brugeren klikker på eller flytter musen hen over dem.
• Kontrolelement = ”Luk X”
• Skrifttype = 16 pkt
• Placering = Ved kant af vist annonce (ikke i panel)
• Funktion = Panel trækkes tilbage, når musen flyttes væk.
Brug af video
• Værtsinitieret video kan anvendes ethvert sted i brugeroplevelsen.
• Videovarighed: Maks. 15 sekunder
• Al lyd skal startes af brugerklik.
• Brugerinitieret Flash-buffervideo tilladt (Flash 6.0 og nyere)
• Må kun vises i panelet og må afspilles automatisk, når panelet udvides. Stop/Mute- og Start-knapper er påkrævede.
• Lyd skal startes af bruger og må ikke køre i løkke eller overstige 15 sekunder.
Retningslinier for indsendelse af Eyeblaster-annoncer
Der skal gennemføres to trin for at udsende en Eyeblaster-annonce på MSN. Først skal annoncøren bruge Eyeblasterbrugergrænsefladen til at overføre nødvendige kreative elementer eller sende kreative elementer til Eyeblaster. Eyeblaster opretter derefter annoncekoder, der skal overføres til MSN, for at annoncen kan udsendes.
MSN kræver 3 arbejdsdage fra den dato, hvor koderne modtages fra Eyeblaster, til at teste, planlægge og udgive
koderne på MSN-netværket. MSN-ekspeditionstiden på 3 dage starter, når et komplet kreativt element er modtaget af
MSN, og når en tilsvarende MSN-ordre er underskrevet.
For at lave en annonce til Eyeblaster skal du have adgang til deres brugergrænseflade. MSN kan oprette dig som bruger, hvis du ikke allerede har adgang. Når du har adgang skal du uploade annoncen gennem deres brugergrænseflade.
Eyeblaster har deres egne standarder for click, video og expandable-elementer. Specs. og eksempler kan findes på
www.eyeblaster.com - Når du er færdig med din annonce skal du give MSN besked. Dernæst vil MSN sætte godkendelsesforløbet hos Eyeblaster igang.
Tjekliste – her kan du spare meget tid!
1.
2.
3.
4.
5.
Hvor skal bannerne linke brugerne hen? Husk at angive destinationslinket (URL).
Har du angivet det korrekte click-tag?
Har du tjekket, at filstørrelsen på hvert banner er inden for de angive størrelser?
Såfremt du fremsender Flash-baserede bannere, har du så husket at vedlægge back-up GIF (eller JPG) bannere?
Har du navngivet bannerne korrekt? Husk at det har stor betydning, når der skal aflæses statistik på bannerkam
pagnen. I statistikken vil hvert banner fremgå jf. dets navngivning og vær opmærksom på, at der kan være flere
versioner af hvert banner.
19
Eksempel
9 0 pi x e ls
7 2 8 pi x e ls
728x90 banner expandable, ikke EXPANDED
M A X 2 2 5 pi x e ls
9 0 pi x e ls
7 2 8 pi x e ls
( E x pand e d )
Specifikationer
Dimensioner
(BxH)
Filtyper der
Flash
Retning for
udvidelse
tredjepart
728x90
Max 728x400 for
høfligt kreativt
element (Expanded)
Op,
ned
Flash 6.0
Flash 7.0
Flash 8.0
50K / 100K
10MB for høfligt
kreativt element
(expanded)
40K
Lyd
(ved klik)
Maks. 15
Bruger
sekunder
aktiveret
og
og maks. 15
uendeligt
sekunder
loop
Streaming
Maks.
30 sek.
Ramme
1 pixel (grå
eller sort
foretrukket)
Clicktag
staves*
on(release){
EB.Clickthrough();
}
Rapporteret data
20
•
•
•
•
•
•
•
•
•
•
•
• Panelet må ikke rage mere end 225 pixel ud over bannerets øverste/nederste kant. Panelets bredde må ikke over
skride bannerets bredde (728 pixel). Banneret må ikke udvides vandret.
Brug af video
*Bemærk! Når koder er færdigbehandlet af Eyeblaster, skal de sendes til din MSN-kundekonsulent sammen med sendeformularoplysningerne (ovenfor), hvis MSN-kundekonsulenten endnu ikke er informeret om annoncekodefærdiggørelsen. MSN-kundekonsulenten koordinerer derefter implementeringen direkte med [email protected].
Udfyld sendeformularen, og udskriv eller send den til din Account Executive eller din Account Manager.
1.
2.
3.
4.
5.
21
( P R E - EX P A N D E D )
1 8 0 pi x e ls
2 1 0 pi x e ls
Eksempel
1 8 0 pi x e ls
1 5 0 pi x e ls
1 5 0 pi x e ls
3 7 5 pi x e ls
180x150 banner PRE-expandable, ikke EXPANDED
180x150 banner PRE-expandable, EXPANDED
Oplevelse for slutbrugeren
1.Brugeren besøger Windows Live Messenger Today.
a. Flash-annoncen vises som en 180x150 bannerannonce og udvides oven på sideindholdet i de anførte områder som vist i eksemplet.
2.Efter 8 sekunder minimeres den udvidende annonce til et 180x150 banner i det nederste højre hjørne af siden.
3.Brugeren har mulighed for at genafspille over-the-page-oplevelsen via et call-to-action til at udvide annoncen.
4.Hvis brugeren ikke har Flash installeret eller ikke kan se Rich Media-annoncer, vises der et standardbanner (180x150 GIF eller JPG).
Alle Windows Live Today-placeringer skal godkendes af MSN redaktionen.
Specifikationer
Dimensioner
(BxH)
180x150
Max 555x360 for
høfligt kreativt
element (Expanded)
Filtyper der
Flash
Retning for
udvidelse
tredjepart
Venstre op
Flash 6.0
Flash 7.0
Flash 8.0
50k / 100K
10MB for høfligt
kreativt element
(expanded)
40K
Lyd
(ved klik)
Maks. 15
Bruger
sekunder
aktiveret
loop)
sekunder
Streaming
Maks.
30 sek.
Bemærkninger til annoncespecifikationer
Den maksimale animationslængde er:
o Op til 8 sekunder for det udvidede indhold (expanded);.
o Op til yderligere 8 sekunder for banneret (180x150)
o Dvs. 16 sekunder i alt.
Politik for accept af kreative elementer
Annoncen skal overholde kravene i Microsofts ’Politik for accept af kreative elementer’
Ramme
1 pixel (grå
eller sort
foretrukket)
Clicktag
staves*
on(release){
EB.Clickthrough();
}
22
MESSENGER KLIENT
2 3 4 pi x e ls
6 0 pi x e ls
2 3 4 pi x e ls
6 6 pi x e ls
2 3 4 pi x e ls
6 0 pi x e ls
6 0 pi x e ls
1 9 0 pi x e ls
Eksempel
Oplevelse for slutbrugeren
Dette banner er tilgængeligt for Windows Live Messenger brugere.
Specifikationer
Dimensioner
(BxH)
234x60
300x600 for
høfligt kreativt
element (Expanded)
Skal være fyldt ud
Filtyper der
Flash
Retning for
udvidelse
tredjepart
Op,
ned,
højre,
venstre
Flash 6.0
Flash 7.0
Flash 8.0
50K / 100K
10MB for høfligt
kreativt element
(expanded)
30K
Lyd
(ved klik)
Maks. 15
Bruger
sekunder
aktiveret
loop)
sekunder
Streaming
Maks.
30 sek.
Ramme
1 pixel (grå
eller sort
foretrukket)
Clicktag
staves*
on(release){
EB.Clickthrough();
}
Annoncespecifikationer
Bruger Kontrolpanel
1. Mouse-over (eller klik) for at åbne / Mouse-out for at lukke
Når en bruger laver mouse-over på annoncen, udvides panel; panel formindskes, når musen fjernes.
MDAS kræver ikke et begrænset hotspot.
2. Luk-knap
Panel eller display-annonce skal indeholde en luk-funktion (16 pkt skrift: ”Luk X”), der lukker panelet ved
en brugers klik.
Andre specifikationer
Lyd
1. Tilgængelig ved brugerens klik eller ved mouse-over. Slået fra som default.
a. Hvis indledt ved mouse-over:
1. Der skal være 1 sek. forsinkelse.
2. Lyd skal ophøre, når brugeren fjerner musen fra annoncen.
2. Mute-knap er påkrævet.
Video
1. Video kan anvendes i enhver del af annoncen.
2. Varighed af video: Max 30 sek. Genafspilning er tilladt, hvis det er bruger-aktiveret.
3. Stop og Play-knap er påkrævet.
4. Ledsagende lyd til video er tilladt (se lyd-specifikationer ovenfor).
5. Progressiv download af Flash-video: filstørrelse max. 2,2 MB.
Animation
1. Animation er begrænset til max. 15 sek. varighed.
2. Ubegrænset looping inden for 15 sek.
23
Eksempel
1 8 0 pi x e ls
9 3 0 pi x e ls
1 8 0 pi x e ls
9 3 0 pi x e ls
M A X 4 0 0 pi x e ls
( E x pand e d )
Specifikationer
Dimensioner
(BxH)
Filtyper der
Flash
Retning for
udvidelse
tredjepart
930x180
Max 930x400 for
høfligt kreativt
element (Expanded)
Op,
ned
Flash 6.0
Flash 7.0
Flash 8.0
40K / 500K
10MB for høfligt
kreativt element
(expanded)
40K
Lyd
(ved klik)
Maks. 15
Bruger
sekunder
aktiveret
og
og maks. 15
uendeligt
sekunder
loop
Streaming
Maks.
30 sek.
Ramme
1 pixel (grå
eller sort
foretrukket)
Clicktag
staves*
on(release){
EB.Clickthrough();
}
Rapporteret data
24
•
•
•
•
•
•
•
•
•
•
•
• Panelet må ikke rage mere end 225 pixel ud over bannerets øverste/nederste kant. Panelets bredde må ikke over
skride bannerets bredde (728 pixel). Banneret må ikke udvides vandret.
Brug af video
*Bemærk! Når koder er færdigbehandlet af Eyeblaster, skal de sendes til din MSN-kundekonsulent sammen med sendeformularoplysningerne (ovenfor), hvis MSN-kundekonsulenten endnu ikke er informeret om annoncekodefærdiggørelsen. MSN-kundekonsulenten koordinerer derefter implementeringen direkte med [email protected].
Udfyld sendeformularen, og udskriv eller send den til din Account Executive eller din Account Manager.
1.
2.
3.
4.
5.
25
Windows Live Messenger Tab
Eksempel
4 5 0 pi x e ls
5 5 5 pi x e ls
45
32
Messenger klient
TAB
Brugeroplevelse
Windows Live Messenger tab er tilgængelig for brugere af Windows Live Messenger.
Udvikling
Udviklingen af en tab svarer til at lave en hjemmeside inden for de givne størrelser (555 x 450 pixels). Tab’en kan laves i
Flash, Silverlight eller andet, men det er vigtigt, at vælge en teknologi som er bredt tilgængelig
Specifikationer
1)Tooltip
2)Ikon-URL
3)Indholds-URL
4)Indholdets IP-adresse
Tooltip
Dette er en kort sætning, som vises, når brugeren placerer markøren på Messenger Tab-ikonet. Tooltippet kan være
navnet på klientens selskab eller produkt, en beskrivelse af funktioner, som tilbydes med denne Messenger Tab, eller en
virksomheds slogan. Denne tekst skal oversættes til det passende sprog, før du insender din Messenger Tab til Microsoft Advertising. Tool Tip tekst må ikke være længere end 65 tegn.
Tool Tip
Ikon-URL
En ekstern URL, som linker til thumbnail-grafikken til Messenger Tab. Det er klientens og/eller den lokale Microsoft
Advertising-afdelings ansvar at hoste dette indhold. Det eneste indhold, der håndteres af Windows Live Messenger Tab
Support, er den XML-fil, som henter dette indhold.
(eksempel) http://cp.intl.match.com/plc/msntab/s_img/icons/heart_msnuk.png
26
Windows Live Messenger Tab
Thumbnail-grafikken skal:
• Ikke være bredere end 24 pixel og ikke højere end 24 pixel (24x24)
• Et Portable Network Graphics (PNG)-filformat med alpha (variabel) transparens
• Statisk
• 96 DPI
• Ikke være større end 5 KB
• Være udviklet således, at det tydeligt kan ses i enten en dæmpet eller normal tilstand.
Indholds-URL
Dette er en URL, som peger på Messenger Tab-indholdsfilen. Det er klientens og/eller den lokale Microsoft Advertisingafdelings ansvar at hoste dette indhold. Det eneste indhold, der håndteres af Windows Live Messenger Tab Support, er
den XML-fil, som henter dette indhold.
Denne URL kan også indlæses i en normal browser til forhåndsvisning af Messenger Tab.
(eksempel) http://cp.intl.match.com/plc/msntab/en-uk/m/index.html
• Størrelsen af tab’en er 555 pixels bred og 450 pixels høj.
• ”Overflow” skal sættes til ”auto”
• Vertikal scrollbar skal slås fra (også selvom indhold ikke kræver scroll).
Navn
Navnet på din tab må maks. være 25 tegn.
Navn
27
Personal Expressions
Eksempel
EMoticons
blink
The end user experience
1. Users are exposed to promotional thumbnails within the Messenger conversation window. Users select a content menu (wink, emoticon, display picture, background) where advertiser thumbnails display in a “featured” menu.
o When a user clicks on a promotional thumbnail, the selected content is downloaded and inserted into their “most recently used” menu. In the case of the background image or display picture, clicking on a promotional thumbnail will automatically replace the user’s existing background/display picture with the selected content.
2.After downloading selected content, users may insert emoticons and winks into a conversation; they may also change their background or display picture from the default selection using the “most recently used menu”.
3.Users may also send content to Messenger Contacts during a conversation by inserting a wink or emoticon into the conversation stream or by selecting the “Share Background” option.
4.Once the ad campaign has expired, it will no longer be visible in the content drop down menus. Any installed items will still be visible in a user’s “Most Recently Used” menu as this content is physically saved on the user’s machine.
28
Glossary
•
•
•
•
•
•
•
•
•
•
Background Image - These images are displayed as a backdrop in the background of a conversation window
Display picture - A static image that a user can select for their personal user tile
Dynamic Display Picture - Animated Flash file. Animation usually dependent upon “moods”.
Winks - A dynamic over-the-page experience using sound and animation that is displayed over a user’s messenger window.
Emoticons - Personalized theme characters that can be inserted into a conversation to show moods and emotions.
Content Drop-Down Menu – The four menus which expand in a Messenger conversation window when a user clicks on the icon for a wink, emoticon, display picture, or background. Each menu contains a row of eight Featured thumbnails denoted by a dedicated row and a subsequent “Frequently Used” menu.
Featured Thumbnail – A thumbnail image which displays in the “Featured” section of each Content Drop-Down Menu.
Product Thumbnail – A thumbnail image(s) which displays in the “Frequently used…” section of each Content Drop-
Down indicating the individual components downloaded after a user clicks on a Featured Thumbnail.
Alt Text – The text which appears when a user hovers over a “Featured” or “Product” thumbnail
Key Sequence – The set of characters the user may type into a conversation window to insert an emoticon into the conversation window.
Ad Components
Below is a summary of all ad components that an advertiser must provide as a part of their Personal Expression package.
Specifikationer
Product type
Quantity
Width
Height
File Weight
MSN Served
File Types
Animation
max lenght
in seconds
Loop limit
Alt text
limit
Background
featured
thumbnail
1
32
32
10kb
Maximum
Each
gif (static),
jpg (preferred)
Animation
not allowed
n/a
65
Conversation
window
backround
1-3
800
600
75kb
Maximum
Each
gif (static),
jpg (preferred)
Animation
not allowed
n/a
n/a
Display picture
featured
thumbnail
1
32
32
10kb
Maximum
Each
gif (static),
jpg (preferred)
Animation
not allowed
n/a
65
Static display
picture
1-3
96
96
20kb
Maximum
Each
gif (static),
jpg (preferred)
Animation
not allowed
n/a
n/a
Dynamic display
picture
1
(Up to 5
moods)
98
142
500kb
Maximum
(300 suggested)
swf (Flash 6
preferred, or
lower), and
source .fla file
5 Seconds per
Emotional state;
Flash animation:
18, FPS (Max) /
12 FPS Recommended
1
n/a
Dynamic display
picture.
Down-level
1
96
96
20kb
Maximum
Each
gif (static),
jpg (preferred)
Animation
not allowed
n/a
n/a
Emoticon
featured
thumbnail
1
32
32
10kb
Maximum
Each
gif (static),
jpg (preferred)
Animation
not allowed
n/a
65
Emoticon
1-5
19
19
10kb
Maximum
Each
gif (static),
jpg (preferred)
5 second
maximum
1
n/a
Winks featured
thumbnail
1
32
32
10kb
Maximum
Each
gif (static),
jpg (preferred)
Animation
not allowed
n/a
65
Winks product
thumbnail
1-3
(1 per wink)
32
32
10kb
Maximum
Each
gif (static),
jpg (preferred)
Animation
not allowed
1
65
Wink
1-3
640
Maximum
(400
suggested)
480
Maximum
(300
Suggested)
150kb
Maximum
(75kb
Suggested)
swf (Flash 6
preferred,
Flash 5
possible)
7 Seconds
Maximum;
18 FPS
(Maximum)
/ 12 FPS
(Suggested)
1
n/a
29
Background
image
Display
picture
Emoticon
Product
thumbnails
Featured
thumbnails
*Note: Only the Display Picture (96x96) is shown in example above.
Data Reported
Data is reported for each type of content individually. Winks, emoticons, backgrounds, and display pictures provide
separate reporting metrics. This information may be accessed through our Ad Reports tool.
•
•
Impressions – The number of times users are exposed to the Featured thumbnail in the content drop-down menu within the Messenger conversation window.
Clicks – The number of times a user clicks on the Featured thumbnail and downloads the file associated with a speci
fic type of content.
Ad Specifications:
A Personal Expression campaign includes 4 types of branded elements accompanied by a promotional Thumbnail (a
static 32x32 image).
General Information (Flash)
Personal Expression content must align to the following Flash requirements.**
•
•
•
•
•
Published Version: Flash must be published in Flash 4.0, 5.0 or 6.0 (preferred)
Frame Rate: Verify that the Flash creative does not exceed 18fps. Settings greater than 18fps will result in poor per
formance for many of our users and is not allowed
File Weight: Verify that each creative element does not exceed weight requirements detailed below
Video: Flash components may not include streaming video. Embedded video may be included in Winks and Dyna
mic Display Pictures as specified in the “Creative Technical Requirements” section.
Interaction: Anything that requires user input or interaction, such as buttons, is strictly prohibited within the flash file.
**See “Creative Technical Requirements” section for additional information.
Featured Thumbnail
Each content type (wink, emoticon, display picture, background) must include a featured promotional thumbnail which
will appear in the associated conversation window menu. There may be one featured thumbnail per content type.
• Featured Thumbnail – Background Featured Thumbnail (Quantity: 1), Display Picture Featured Thumbnail (Quanti
ty: 1), Emoticon Featured Thumbnail (Quantity: 1), Wink Featured Thumbnail (Quantity: 1)
o File Type: .gif (static), .jpg (preferred)
o File Dimensions: 32w x 32h (pixels)
o File Weight: 10K
o Animation: No
o Alt Text: 65 Characters including spaces
30
Background Images (Quantity: 1-3)
Display pictures are images applied to a personal user tile within the Messenger conversation window. Display pictures
must be a static image. Advertisers should provide a single static display picture. Additional guidance regarding ActionScripting can be found in the “Creative Technical Requirements” section.
Conversation Window Background
•
•
•
•
File Type: .gif (static), .jpg
File Dimensions: 800wx600h
File Weight: 75K
Animation: No
Display Pictures
Display Picture Picture (Quantity: 1 Dynamic Display Picture & 1-2 Static Display Pictures, OR 3 Static Display
Pictures) Display pictures are images applied to a personal user tile within the Messenger conversation window.
Display pictures can be both dynamic and static.
Static Display Picture
• File Type: .gif (static), .jpg,
• File Dimensions: 96w x 96h
• File Weight: 20kb Maximum (Each)
• Animation: No
Dynamic Display Picture - User selects a DDP from the menu as shown below. If selected, the standard static Display
Picture is replaced with a taller animated Flash file. This file has up to 5 different animated states that can be selected
by the user or triggered by either emoticons or character sequences mapped via xml. For example, the characters ”:)”
could be mapped to an animation sequence of a character smiling. These animations will display on both the users
machine and anyone who communicates with the user and chooses to view Display Pictures.
Note: A DDP element will incorporate up to 5 distinct emotional states –intended to be mapped directly to the Personal
Expression emoticons.
31
• File Type: single .swf published for Flash6 (file compression enabled)
• File Dimensions: 98w x 142h
• File Weight: 500kb (Maximum) / 300kb (Recommended)
• Audio: Limit one sound file per animated state. No looping. (MP3 files may be embedded into frames when crea
ting the .swf file)
• Flash Frame Rate: 18 FPS (Maximum) / 12 FPS (Recommended)
• Key Sequence: Key Sequence for each mood
• Scripting ”Moods”: Utilizing the fla template provided, Dynamic Display Pictures will be able to provide a single swf file containing multiple emotional states/Moods associated with an animation sequence.
o When a user either selects a different state or uses a linked trigger, the messenger client reloads the Flash file while passing it a variable. This variable tells the Flash file which state has been selected and if coded properly, will jump to that point on the timeline.
This variable is defined as displayMood in our supplied template and should not be altered for any reason.
What can be altered freely are the names you give your individual states as these are established via Frame Labels.
o Frame Labels One for each animated state (up to 5 including the default). Please note the names of each label and supply this information to whoever completes the submission documentation. Also note that the use of the word default as a label will cause issues as this is reserved for use with Actionscripting. In our sup
plied template, the states are “none” (for the default state) and state001 through state004. The order that the states appear on the timeline is irrelevant with the exception that the default state should always occur first.
o _root.gotoAndPlay(displayMood); This code should be present no later than the third frame on the main timeline, and before any animation displays. (it is recommended to use a consistent background image for all states to make the transitions as seamless as possible.)
o Building Your Flash File: Here is a screenshot of the supplied template’s main timeline. The first frame that Actionscript occurs in uses the script [ _root.gotoAndPlay(displayMood); ]. This looks for a variable that is passed to the Flash file via the Messenger client and will then jump to the corresponding label. If no variable is passed, the DDP will automatically play the default state.
• Insert Image
• The second frame with Actionscripting is a [ stop(); ] command followed immediately by another frame with the same code as the first scripted frame. This redundancy is there to aid the client in ensuring that the correct state is displayed.
• If built properly, the published DDP will switch between moods within the Flash Player by pres
sing CTRL+ENTER or selecting the Play option from the Control menu.
Building Your Flash File:
Here is a screenshot of the supplied template’s main timeline. The first frame that Actionscript occurs in uses the script [
_root.gotoAndPlay(displayMood); ]. This looks for a variable that is passed to the Flash file via the Messenger client and
will then jump to the corresponding label. If no variable is passed, the DDP will automatically play the default state.
The second frame with Actionscripting is a [ stop(); ] command followed immediately by another frame with the same
code as the first scripted frame. This redundancy is there to aid the client in ensuring that the correct state is displayed.
If built properly, the published DDP will switch between moods within the Flash Player by pressing CTRL+ENTER or
selecting the Play option from the Control menu.
Down-level Experience: If the user has not installed the most current version of the Windows Live Messenger client, a
static Display Picture will be delivered in the place of a Dynamic Display Picture.
•
•
•
•
File Type: .gif (static), .jpg
File Dimensions: 96w x 96h
File Weight: 20kb Maximum
Animation: No
32
Display Picture Product Thumbnail - Thumbnail images which are inserted into the “Most Recently Used” menu after
a Display Picture is downloaded by a user. The featured thumbnail image will be populated into this space.
•
•
•
•
•
File Type: gif (static), .jpg
File Dimensions: 32w x32h
File Weight: 10kb Maximum
Animation: No
Alt Text: 65 Characters or less including spaces
Emoticons (Quantity 1-5)
Personalized theme characters/icons that can be inserted into a conversation to typically show moods and emotions
(can be animated). Note: the most effective emoticons are those that can frequently be applied in the context of a chat
conversation (e.g. smiley character, lunch time icon, going to bed now icon, etc.). They are not intended to always tie
directly to brand logos/imaging.
If a Dynamic Display Picture is created, emoticons should map directly to each emotional state within the Dynamic
Display Picture. This can be done by creating emoticons that display the same emotions as the “moods” implemented
in a dynamic display picture. The “moods” and associated emoticons should utilize the same “Key Strokes.”
• Emoticon
o File Type: gif (static or animated), .jpg
o File Dimensions: 19w x 19h
o File Weight: 10kb Maximum (Each)
o Animation: Yes
o Key Strokes: Not to exceed 6 characters
• Emoticon Key Strokes indicate the short key sequence which may be used to insert an emoticon into a conversation window without the use of the drop-down menu.
Winks (Quantity 1-3):
A user selects a Wink from the menu as shown to the right. Upon selection an animated Flash file displays for 7 seconds
over the chat window (see second image). This animation is viewable by all chat participants unless a recipient has
chosen to block Wink animations. In these instances, the text link that appears in the chat history window will allow the
user play the Wink manually. The animation will automatically unload from the client upon completion of the animation or 7 seconds, whichever occurs first. Any user can replay the animation by clicking the text link as many times as
they would like.
33
Additional guidance regarding ActionScripting can be found in the “Creative Technical Requirements” section.
• Wink
o File Type: single .swf file published for Flash 6 (preferred) or Flash 5 (file compression enabled)
o File Dimensions/Stage Size: 640w x 480h (Maximum) / 400w x 300h (Recommended)
• Note: By default, a Wink will scale uniformly to fit the chat window until one of the two dimensi
ons hits the border of the display area. This is why we recommend using stage dimensions that are taller than they are wider as most users will extend the chat client vertically more often than horizontally.
o File Weight: 150k (Maximum) / 75k (Recommended)
o Animation Length: 7 Seconds Maximum
o Audio: Non-User Initiated Sound in an integrated .wav format.Audio must be integrated into the .swf file (Not as a separate wav file). Streaming only, no event sounds.
o Flash Frame Rate: 18 FPS (Maximum) / 12 FPS (Recommended)
o Animation: Yes
o Scripting Guidance: There are only three pieces of Actionscripting that are allowed to be used in Winks. Any files submitted using code that is not listed below will be rejected by the client and will not display.
• stop(); This is used to stop playback.
• fscommand(“quit”); This must be placed on the last frame of the main timeline and instructs the Messenger client to unload the Flash animation
• No Scale Script - If your Wink is reliant on bitmap imagery, you can use the following script that will prevent the Wink from being scaled any larger than the base stage size, though the file will be scaled down if displayed in a chat window that has been minimized by the user.
• var originalX;
var originalY;
Stage.scaleMode = ”showAll”;
originalX = Stage.width;
originalY = Stage.height;
Stage.scaleMode = ”noScale”;
if (Stage.width < originalX || Stage.height < originalY){
Stage.scaleMode=”showAll”;
}else{
Stage.scaleMode=”noScale”;
}
•
Building Your Flash File:
o As stated in the DDP section, no Actionscripting is allowed outside of the three commands listed. The simplest and most common method of creating a Wink is to manually tween all of the elements on the main timeline, only nesting elements in movie clips that have repeating animation or play a limited number of times and stop. Building on the main timeline also ensures you do not exceed the maximum playback time of 7 seconds.
o Place the “No Scale Script” on the first frame if you wish to prevent the users chat window from scaling the Wink larger than the default stage dimensions. Place the stop and fscommand on the last frame.
o Remember to make sure you output the file in Flash 6 format and ensure that file size does not exceed the 150kb maximum.
• Wink Product Thumbnail - Thumbnail images which are inserted into the “Most Recently Used” menu after Winks are downloaded by a user. There should be a unique thumbnail for each Wink created.
o File Type: .gif (static), .jpg
o File Dimensions: 32w x 32h
o File Weight: 10k Maximum
o Animation: No
o Alt Text: 65 Characters or less including spaces
34
Common Design/Validation Issues
Backgrounds
Typical Issues:
• Often submitted as compressed JPG’s (GIF or uncompressed JPG only)
• PNG Format is not accepted
• Exceeds file size limits
• Bad placement of sponsor logos within the image (ensure logo is visible in conversation window)
• Often treated like one big banner ad
• No thumbnail image provided
Display Pictures
Typical Issues:
• Often submitted as compressed JPG’s (GIF or uncompressed JPG only)
• PNG Format is not accepted
Dynamic Display Pics
Typical Issues:
• Often produced without proper Actionscripting
• Only the white-listed actionscripts listed may be used
• User selected states loop indefinitely or revert to a generic branding state.
• Clients try to embed video (causes failure during validation)
Winks
Typical Issues:
• Created using unauthorized Actionscripting
• Missing Actionscripting that closes the animation
• Animation has too many moving elements, creates choppy or slow playback
• Animation uses compressed bitmaps that distort in larger/smaller chat windows
• Thumbnail images are the wrong dimensions
Emoticons
Typical Issues:
• First frame of animation is blank (translates to a blank thumbnail)
Featured Thumbnail
Typical Issues:
• Submitted as an animated GIF (uncompressed JPG is standard)
• Image dimensions are too large
Creative Business Requirements
General Functionality
Creative
• No Forms allowed
• Flash must be published in Flash 5.0 or 6.0 (including security code) only
• Audio must be user-initiated and never automatic.
Respect the user
• The Messenger Client should remain easy to use
• Creative should focus on being educational and / or entertaining
• Creative should be clever and engaging while conforming to user expectations of the MSN experience
• Never use pulsing or garish colors
Theme Creative Dimensions and Weight
• Verify that Flash components such as Winks and DDP’s do not prompt the user to download Flash or any other Plug-
In in any situation
• Verify that the flash files are of the correct dimensions when rendered
35
Animations
• Keep animation smooth and fluid, using slow motions and gentle fades. Fast and abrupt motion has been shown to be highly irritating
• Avoid experiences that ’break-through’ the client or abuse the content
o Not allowed
• Animation that does not tie into the messaging/ product/ offer
• Repetitive, rapid flashing, or blinking- No animation in excess of 10 seconds (see the individual product creative specs)
• Cycling of sequences/ looping/ repeat animation
Cross Media Campaigns
• Allowed with restrictions
o Advertisements which are part of a cross media campaign are allowed. Advertisements which are featured across advertising mediums provide a level of predictability and familiarity. The expectation of these brands to all viewers, is consistent. Ads which carry an industry acceptance are acceptable to run on our
network.
Imagery
• Not allowed
o Pixilated or unclear designs/ logos/ images
o Imagery that appears to have functionality but does not. i.e. drop down menus, radio buttons, etc.
o Microsoft, MSN, or Windows Live imagery/ logo/ theme cannot be used or called out in advertisement.
o Racy imagery that is not representative of the products being offered.
o Arbitrary imagery which has no association with the product/offering. This type of imagery is unpredicta
ble and misleading to users
Messaging
• Not allowed
o Ads that do not incorporate advertiser’s logo.
o Destination pages linked from an ad that does not include the products/ offers shown in the ad.
o Messaging or offers that mislead the user.
o Racy content that is not representative of the products/services being offered.
o Text that is not representative of the products/services being offered. Text which can be interpreted as misleading or invites a user to an experience which is not predictable to the product/service being offered.
• Allowed with restrictions
o Non-branded Pharmaceutical advertisers who are promoting informational data about a product or drug.
o Non-branded Pharmaceutical advertisers who mention the drug brand name but do not mention the disease or condition. (brand building
Functionality
• Not allowed
o Creative submitted by or on behalf of an advertiser may not:
• Utilize deceptive advertising or misleading user experience to drive user clicks on an advertise
ment. For example; when a user clicks on a specific state for an Ad that says ”Click your state for more information” the landing page must meet the users expectation providing information for that state.
• Utilize fake html or images that elicit unexpected behaviors. Examples of these include but are not limited to:
• Static images of: drop down menus, text boxes, scroll down menus, radio buttons, etc., that are not fully functional
• Text that animates or changes colors that presents users with an expectation of functionality (e.g. text that functions
like a hyperlink or expanding ad components)
• Utilize any element designed to generate a click without relevant information or content at the destination.
• Utilize ’Focus’ commands to make the ad the active window
• Utilize ’fake’ ”Close” icons (for example: when you close an ad, it should close it and not trigger ’unexpected’ beha
vior such as another ad, page, etc.)
• Utilize ’mouse trapping’ whereby the advertiser does not allow users to use their ’back button’ and traps them on
their site
• Ad cannot appear to be part of the UI
• Imitate Microsoft Windows operating system messages, look and feel and/or behavior such as, but not limited to,
error messages, dialog boxes, OS boxes, DOS boxes, and Windows icons
• Imitate in look and feel or functionality the site/section on which it is running (for example: An ad on MSN Search
should not look or feel like the Search box)
36
•
•
•
•
•
•
•
•
•
.
Appear as though it is part of the content/site on which it appears. White and/or ads with a similar color as the
background of the site must have a border or otherwise clearly stand out (see the individual product creative specs
for details)
Imitate presupposed knowledge about the functionality of your personal computer
Pretend to know details about a user’s computer/system, including what is/is not installed, whether it has discovered
viruses, worms, corrupted files, etc. (for example: scare tactics to make users buy/download software etc.)
Promote or contain viruses, worms, corrupted files, cracks or other material that is intended to or may damage or
render inoperable software, hardware or security measures of Microsoft, any user of MSN.com and/or the Microsoft
network of services, or any third party
Appear to make the ad page look broken or as if something is not working what is considered to be normal on a web page
Contain text reference on an ad or on the landing page to a group of Microsoft customers to entice them to view the ad as special for them (for example: ”Attention MSN Users”)
Contain the MSN Butterfly logo without a trademark license from LCA
Have a Pop-Up ad or a Pop-Under ad launched from within an ad or from the landing page whether real or imitated behavior
Perform an automatic download of anything to a user’s system or present a download dialog box without first presenting detailed information to the user about the download and then requiring the user to click to download the product
Creative Technical Requirements
The technical capabilities of both Winks and Dynamic Display Pictures are detailed below. These parameters relate to
the capabilities enabled within Flash for these ad products.
As a general rule, Winks and Dynamic Display Pictures DO NOT allow the following:
1.Access to input/output of any sort; this include to/from a server, the local hard disk, or any devices (including web cams, etc)
2.Any action scripts that would cause Messenger to exhibit unacceptable behavior (such as a wink popping open a browser window to a web page)
3.Any action scripts or flash features in versions of the flash file format that are released after FlashBang is released. Only when FlashBang is updated to handle new flash file versions will those higher version be allowed to passed
4.Anything that is not explicitly defined in the Macromedia Flash (SWF) file format
ActionScript methods below are the actual ActionScript functions or methods that a use would type into the Macromedia Studio MX application. Action opcodes are the binary numbers (which represents particular actions) that are
generated by Studio MX when you export to a *.swf file.
NOTE: For all restriction levels, embedded video (i.e. mpeg-type video) is always disallowed.
General Rules
• You cannot assign to or from a user defined function so: “Movie.OnEnterFrame = myFunction” is not allowed. This also applies to events. What is recommended for events (such as onEnterFrame) is to do Movie.OnEnterFrame { //do stuff } as opposed to using assignment (as above)
• You must declare a function/method/class before calling/using it
• You cannot assign to or from an allowed listed function/object, i.e. Color.setRGB = myFunction() { } is disallowed
• You cannot use exceptions
• You cannot use static methods
37
DDP Allow List
These are ActionScript methods that are allowed:
User Defined
Functions/Objects
Allow All
Color
Allow Create
String
Allow Create
Array
Allow Create
Date
Allow Create
Object
Allow Create
getLocal
Allow Call
floor
Allow Call
getFocus
Allow Call
indexOf
Allow Call
getBeginIndex
Allow Call
getEndIndex
Allow Call
substring
Allow Call
AttachMovie
Allow Call
max
Allow Call
setRGB
Allow Call
gotoAndPlay
Allow Call
gotoAndStop
Allow Call
substr
Allow Call
split
Allow Call
setTransform
Allow Call
stop
Allow Call
getDepth
Allow Call
createEmptyMovieClip
Allow Call
sort
Allow Call
push
Allow Call
moveTo
Allow Call
lineTo
Allow Call
beginFill
Allow Call
endFill
Allow Call
setMask
Allow Call
charAt
Allow Call
getInstanceAtDepth
Allow Call
getUrl(“FSCommand:Quit”)
Allow Call
reverse
Allow Call
slice
Allow Call
localToGlobal
Allow Call
play
Allow Call
random
Allow Call
getHours
Allow Call
getMinutes
Allow Call
round
Allow Call
These are Action Opcodes that are allowed (opcodes only exist in the compiled, *.swf, files). These usually correspond to
an ActionScript method with a very similar name:
ActionCall = 0x9E,
ActionDefineLocal = 0x3C,
ActionDefineLocal2 = 0x41,t
ActionSetMember = 0x4F,
ActionAdd = 0x0A,
ActionAdd2 = 0x47,
ActionAnd = 0x10,
ActionAsciiToChar = 0x33,
ActionBitAnd = 0x60,
ActionBitLShift = 0x63,
ActionBitOR = 0x61,
ActionBitRShift = 0x64,
ActionBitURShift = 0x65,
ActionBitXor = 0x62,
ActionCharToAscii = 0x32,
ActionCloneSprite = 0x24,
ActionConstantPool = 0x88,
ActionDecrement = 0x51,
ActionAdd2 = 0x47,
ActionStopSounds = 0x09,
ActionAnd = 0x10,
ActionStoreRegister = 0x87,
ActionStrictEquals = 0x66,
ActionStringAdd = 0x21,
ActionStringEquals = 0x13,
DDP
Allow List
ActionBitOR = 0x61,
ActionStringExtract = 0x15,
ActionStringGreater = 0x68,
ActionStringLength = 0x14,
ActionStringLess = 0x29,
ActionSubtract = 0x0B,
ActionTargetPath = 0x45,
ActionToggleQuality = 0x08,
ActionToInteger = 0x18,
ActionDelete = 0x3A,
ActionToNumber = 0x4A,
ActionDelete2 = 0x3B,
ActionToString = 0x4B,
ActionDivide = 0x0D,
ActionTrace = 0x26,
ActionEndDrag = 0x28,
ActionTypeOf = 0x44,
ActionEnumerate = 0x46,
ActionWaitForFrame = 0x8A,
ActionEnumerate2 = 0x55,
ActionWaitForFrame2 = x8D,
ActionEquals = 0x0E,
ActionWith = 0x94,
ActionEquals2 = 0x49,
ActionGetMember = 0x4E,
ActionGetProperty = 0x22,
ActionGetTime = 0x34,
ActionCallFunction = 0x3D,
ActionCallMethod = 0x52,
ActionNewObject = 0x40,
ActionGetVariable = 0x1C,
ActionDefineFunction = 0x9B,
ActionGotoFrame = 0x81,
ActionDefineFunction2 = x8E,
ActionGotoFrame2 = 0x9F,
ActionIf = 0x9D,= 0x40,
ActionGoToLabel = 0x8C,
ActionJump = 0x99,
ActionGreater = 0x67,
ActionIncrement = 0x50,
ActionInitArray = 0x42,
ActionInitObject = 0x43,
ActionInstanceOf = 0x54,
ActionLess = 0x0F,
ActionLess2 = 0x48,
ActionMBAsciiToChar = 0x37,
ActionMBCharToAscii = 0x36,
ActionMBStringExtract = 0x35,
ActionMBStringLength = 0x31,
ActionModulo = 0x3F,
ActionMultiply = 0x0C,
ActionNextFrame = 0x04,
ActionNone = 0x0,
ActionNot = 0x12,
ActionOr = 0x11,
ActionPlay = 0x06,
ActionPop = 0x17,
ActionPreviousFrame = 0x05,
ActionPush = 0x96,
ActionPushDuplicate = 0x4C,
ActionRandomNumber = 0x30,
ActionRemoveSprite = 0x25,
ActionReturn = 0x3E,
ActionSetProperty = 0x23,
ActionSetTarget = 0x8B,
ActionSetTarget2 = 0x20,
ActionSetVariable = 0x1D,
ActionStackSwap = 0x4D,
ActionStartDrag = 0x27,
ActionStop = 0x07,
38
Array
Allow Create
Date
Allow Create
Object
Allow Create
getLocal
Allow Call
floor
Allow Call
getFocus
Allow Call
indexOf
Allow Call
getURL(“FSCommand:Quit”)
getBeginIndex
Allow Call
stop
getEndIndex
Allow Call
substring
Allow Call
AttachMovie
Allow Call
max
Allow Call
Wink Allow List
These are ActionScript methods that aresetRGB
allowed for Winks: Allow Call
Also allowed is the following ActionScript
if it is included on the
gotoAndPlay
Allowfirst
Call frame of a wink. This ActionScript can be included
in winks with raster (bitmap) graphics togotoAndStop
ensure that they do Allow
not Call
get stretched larger than their original size (because
they pixilate).
substr
Allow Call
var originalX;
var originalY;
split
Allow Call
setTransform
Allow Call
stop
Allow Call
getDepth
Stage.scaleMode = “showAll”; createEmptyMovieClip
originalX = Stage.width;
sort
originalY = Stage.height;
push
Stage.scaleMode = “noScale”; moveTo
Allow Call
Allow Call
Allow Call
Allow Call
Allow Call
lineTo
Allow Call
getInstanceAtDepth
Allow Call
Allow Call
if (Stage.width < originalX ||
Stage.height <
originalY)
beginFill
Allow
Call
Stage.scaleMode=”showAll”;endFill
Allow Call
else
setMask
Allow Call
Stage.scaleMode=”noScale”;charAt
Allow Call
Allow Call
Wink & Dynamic Display slice
Picture Allow List
Allow Call
reverse
These are the ActionScript methods now
allowed for Winks (as
well
localToGlobal
Allow
Call as Dynamic Display Pictures):
User Defined
Functions/Objects
Allow All
Color
Allow Create
play
Allow Call
random
Allow Call
Allow Call
String
Allow Create
getHours
Array
Allow Create
getMinutes
Allow Call
Date
Allow Create
round
Allow Call
Object
Allow Create
getLocal
Allow Call
floor
Allow Call
getFocus
Allow Call
indexOf
Allow Call
getBeginIndex
Allow Call
getEndIndex
Allow Call
substring
Allow Call
AttachMovie
Allow Call
max
Allow Call
setRGB
Allow Call
gotoAndPlay
Allow Call
gotoAndStop
Allow Call
substr
Allow Call
split
Allow Call
setTransform
Allow Call
stop
Allow Call
getDepth
Allow Call
createEmptyMovieClip
Allow Call
sort
Allow Call
push
Allow Call
moveTo
Allow Call
lineTo
Allow Call
beginFill
Allow Call
endFill
Allow Call
setMask
Allow Call
charAt
Allow Call
getInstanceAtDepth
Allow Call
Allow Call
reverse
Allow Call
slice
Allow Call
localToGlobal
Allow Call
play
Allow Call
random
Allow Call
Yderligere
getHoursspørgsmål? Kontakt venligst
Allow Calldin account manager eller besøg advertising.msn.dk
getMinutes
Allow Call
39
ActionPlay = 0x06,
ActionPop = 0x17,
ActionPush = 0x96,
ActionRandomNumber
0x30, in the compiled, *.swf, files). These usually correspond to
These are Action Opcodes that are allowed
(opcodes only=exist
ActionRemoveSprite
= 0x25,
an ActionScript method with a very similar
name:
ActionCall = 0x9E,
ActionDefineLocal = 0x3C,
ActionDefineLocal2 = 0x41,t
ActionSetMember = 0x4F,
ActionAdd = 0x0A,
ActionAdd2 = 0x47,
ActionAnd = 0x10,
ActionStop = 0x07,
ActionBitOR = 0x61,
ActionDelete = 0x3A,
ActionDelete2 = 0x3B,
ActionDivide = 0x0D,
ActionToInteger = 0x18,
ActionEndDrag = 0x28,
ActionToNumber = 0x4A,
ActionEnumerate = 0x46,
ActionToString = 0x4B,
ActionEnumerate2 = 0x55,
ActionTrace = 0x26,
ActionEquals = 0x0E,
ActionTypeOf = 0x44,
ActionEquals2 = 0x49,
ActionWaitForFrame = 0x8A,
ActionGetMember = 0x4E,
ActionWaitForFrame2 = x8D,
ActionGetProperty = 0x22,
ActionWith = 0x94,
ActionGetTime = 0x34,
ActionGetVariable = 0x1C,
ActionGotoFrame = 0x81,
ActionGotoFrame2 = 0x9F,
ActionGoToLabel = 0x8C,
ActionCallFunction = 0x3D,
ActionCallMethod = 0x52,
ActionNewObject = 0x40,
ActionDefineFunction = 0x9B,
ActionGreater = 0x67,
ActionDefineFunction2 = x8E,
ActionIncrement = 0x50,
ActionIf = 0x9D,= 0x40,
ActionInitArray = 0x42,
ActionJump = 0x99,
ActionInitObject = 0x43,
ActionInstanceOf = 0x54,
ActionLess = 0x0F,
ActionLess2 = 0x48,
ActionMBAsciiToChar = 0x37,
ActionMBCharToAscii = 0x36,
ActionMBStringExtract = 0x35,
ActionMBStringLength = 0x31,
ActionModulo = 0x3F,
ActionMultiply = 0x0C,
ActionNextFrame = 0x04,
ActionNone = 0x0,
ActionNot = 0x12,
ActionOr = 0x11,
ActionPlay = 0x06,
ActionPop = 0x17,
ActionPush = 0x96,
ActionRandomNumber = 0x30,
ActionRemoveSprite = 0x25,
40
41
Date Class
The full Date class has been added to both the Winks and DDP’s AllowLists.
The definition of the Date class shown below is taken from:
http://livedocs.macromedia.com/flashlite/2/main/00000468.html
Object
|
+-Date
public class Date
extends Object
The Date class lets you retrieve date and time values relative to universal time (Greenwich mean time, now called universal time or UTC) or relative to the operating system on which Flash Player is running. The methods of the Date class
are not static but apply only to the individual Date object specified when the method is called. The Date.UTC() method
is an exception; it is a static method.
The Date class handles daylight saving time differently, depending on the operating system and Flash Player version.
Flash Player 6 and later versions handle daylight saving time on the following operating systems in these ways:
•
Windows - the Date object automatically adjusts its output for daylight saving time. The Date object detects whether daylight saving time is employed in the current locale, and if so, it detects the standard-to-daylight saving time tran
sition date and times. However, the transition dates currently in effect are applied to dates in the past and the future, so the daylight saving time bias might calculate incorrectly for dates in the past when the locale had different transi
tion dates.
To call the methods of the Date class, you must first create a Date object using the constructor for the Date class, described later in this section.
Availability: ActionScript 1.0; Flash Lite 2.0
Property summary
Properties inherited from class Object
constructor (Object.constructor property)
__proto__ (Object.__proto__ property)
prototype (Object.prototype property)
__resolve (Object.__resolve property)
Constructor summary
Signature
Description
Date([yearOrTimevalue:Number], [month:Number],
[date:Number], [hour:Number], [minute:Number],
[second:Number], [millisecond:Number])
Constructs a new Date object that holds the
specified date and time.
42
Method summary
Modifiers
Signature
Description
-
getDate() : Number
Returns the day of the month (an
integer from 1 to 31) of the
specified Date object according to
local time.
-
getDay() : Number
Returns the day of the week (0 for
Sunday, 1 for Monday, and so on)
of the specified Date object
according to local time.
-
getFullYear() : Number
Returns the full year (a four-digit
number, such as 2000) of the
specified Date object, according to
local time.
-
getHours() : Number
Returns the hour (an integer from 0
to 23) of the specified Date object,
according to local time.
-
getLocaleLongDate() : String
Returns a string representing the
current date, in long form,
formatted according to the currently
defined locale.
-
getLocaleShortDate() : String
current date, in short form,
formatted according to the currently
defined locale.
-
getLocaleTime() : String
current time, formatted according
to the currently defined locale.
-
getMilliseconds() : Number
Returns the milliseconds (an integer
from 0 to 999) of the specified Date
object, according to local time.
-
getMinutes() : Number
Returns the minutes (an integer
-
getMonth() : Number
Returns the month (0 for January, 1
for February, and so on) of the
local time.
-
getSeconds() : Number
Returns the seconds (an integer
-
getTime() : Number
Returns the number of milliseconds
since midnight January 1, 1970,
universal time, for the specified
Date object.
-
getTimezoneOffset() : Number
Returns the difference, in minutes,
between the computer's local time
and universal time.
-
getUTCDate() : Number
Returns the day of the month (an
integer from 1 to 31) in the
universal time.
-
getUTCDay() : Number
Returns the day of the week (0 for
Sunday, 1 for Monday, and so on)
of the specified Date object,
according to universal time.
-
getUTCFullYear() : Number
Returns the four-digit year of the
universal time.
-
getUTCHours() : Number
Returns the hour (an integer from 0
to 23) of the specified Date object,
-
getUTCMilliseconds() : Number
object, according to universal time.
-
getUTCMinutes() : Number
-
getUTCMonth() : Number
Returns the month (0 [January] to
11 [December]) of the specified
Date object, according to universal
time.
-
getUTCSeconds() : Number
-
getUTCYear() : Number
-
setDate(date:Number) : Number
Returns the year of this Date
according to universal time (UTC).
getYear() : Number
Returns the year of the specified
Yderligere spørgsmål? Kontakt venligst din account manager eller besøg advertising.msn.dkDate object, according to local time.
Sets the day of the month for the
-
getUTCMilliseconds() : Number
getUTCMinutes() : Number
Personal
Expressions
-
getUTCMonth() : Number
Returns the month (0 [January] to
11 [December]) of the specified
Date object, according to universal
time.
-
getUTCSeconds() : Number
-
getUTCYear() : Number
-
getYear() : Number
Returns the year of this Date
according to universal time (UTC).
Returns the year of the specified
Date object, according to local time.
-
setDate(date:Number) : Number
-
setFullYear(year:Number,
Sets the year of the specified Date
[month:Number], [date:Number]) : object, according to local time and
Number
returns the new time in
milliseconds.
-
setHours(hour:Number) : Number
-
setMilliseconds(millisecond:Number) Sets the milliseconds for the
: Number
specified Date object according to
local time and returns the new time
in milliseconds.
-
setMinutes(minute:Number) :
Number
Sets the minutes for a specified
Date object according to local time
and returns the new time in
milliseconds.
-
setMonth(month:Number,
[date:Number]) : Number
Sets the month for the specified
Date object in local time and
milliseconds.
-
setSeconds(second:Number) :
Number
Sets the seconds for the specified
Date object in local time and
milliseconds.
-
setTime(millisecond:Number) :
Number
Sets the date for the specified Date
object in milliseconds since
midnight on January 1, 1970, and
milliseconds.
-
setUTCDate(date:Number) :
Number
Sets the date for the specified Date
object in universal time and returns
the new time in milliseconds.
-
setUTCFullYear(year:Number,
Sets the year for the specified Date
[month:Number], [date:Number]) : object (my_date) in universal time
Number
milliseconds.
-
setUTCHours(hour:Number,
[minute:Number],
[second:Number],
[millisecond:Number]) : Number
-
setUTCMilliseconds(millisecond:Num Sets the milliseconds for the
ber) : Number
specified Date object in universal
time and returns the new time in
milliseconds.
-
setUTCMinutes(minute:Number,
[second:Number],
Sets the minute for the specified
Date object in universal time and
returns the new time in milliseconds
-
setUTCMonth(month:Number,
Sets the month, and optionally the
day, for the specified Date object in
universal time and returns the new
time in milliseconds.
-
setUTCSeconds(second:Number,
milliseconds.
-
setYear(year:Number) : Number
object in local time and returns the
new time in milliseconds.
-
toString() : String
Returns a string value for the
specified date object in a readable
format.
Sets the day of the month for the
local time, and returns the new time
in milliseconds.
Sets the hours for the specified
Date object according to local time
milliseconds.
Sets the hour for the specified Date
object in universal time and returns
the new time in milliseconds.
static
UTC(year:Number, month:Number, Returns the number of milliseconds
[date:Number], [hour:Number],
between midnight on January 1,
[minute:Number],
1970, universal time, and the time
[second:Number],
specified in the parameters.
-
valueOf() : Number
Returns the number
43
-
setUTCMonth(month:Number,
Sets the month, and optionally the
day, for the specified Date object in
universal time and returns the new
time in milliseconds.
-
setUTCSeconds(second:Number,
milliseconds.
-
setYear(year:Number) : Number
object in local time and returns the
new time in milliseconds.
-
toString() : String
Returns a string value for the
specified date object in a readable
format.
static
UTC(year:Number, month:Number,
[date:Number], [hour:Number],
[minute:Number],
[second:Number],
Returns the number of milliseconds
between midnight on January 1,
1970, universal time, and the time
specified in the parameters.
-
valueOf() : Number
Returns the number
of milliseconds since
midnight January 1,
1970, universal time,
for this Date.
Methods inherited from class Object
addProperty (Object.addProperty method), hasOwnProperty (Object.hasOwnProperty method), isPropertyEnumerable (Object.isPropertyEnumerable method), isPrototypeOf (Object.isPrototypeOf method), registerClass (Object.
registerClass method), toString (Object.toString method), unwatch (Object.unwatch method), valueOf (Object.valueOf
method), watch (Object.watch method)
Embedded Video in Flash
The following ActionScript tags have been added to both the Winks and DDP’s Allow Lists:
• VideoFrame
• DefineVideoStream
[The information below on the VideoFrame and DefineVideoStream tags has been taken from Macromedia_v7_flash_
file_format_specification.pdf .]
SWF Video Tags
The following tags define embedded video data within a SWF file. These tags are permissible only in SWF version 6 or
later.
Video embedded in SWF is always streamed: video frames are located in the SWF frames with which they are temporally associated, and video playback can begin before an entire video stream has been downloaded. This is comparable
to the way that streaming sounds are defined (see streaming sound).
DefineVideoStream
Defines a video character which can later be placed on the display list (see The Display List).
DefineVideoStream
Field
Type
Header
RECORDHEADER
CharacterID
UI16
NumFrames
UI16
Width
UI16
Height
UI16
VideoFlagsReserved
UB[5]
VideoFlagsDeblocking
UB[2]
VideoFlagSmoothing
UB[1]
CodecID
UI8
Comment
Tag type = 60
ID for this video character
Number of VideoFrame tags
that will make up this stream
Width in pixels
Height in pixels
Reserved bitfields
00:use VIDEOPACKET value
01: off
10:on
11:reserved
0:smoothing off (faster)
1: smoothing on (higher quality)
2:SorensonH.263
3:Screen video (SWF 7 + only)
44
45
VideoFrame
Provides a single frame of video data for a video character that has already been defined with DefineVideoStream
In playback, the time sequencing of video frames depends on the SWF frame rate only. When SWF playback reaches a
particular SWF frame, the video images from any VideoFrame tags in that SWF are rendered. Any timing mechanism
built into the video payload are ignored.
VideoFrame
Field
Type
Comment
Header
RECORDHEADER
Tag type = 61
StreamID
UI16
ID of video stream character of
which this frame is a part
FrameNum
UI16
Sequence number of this frame
within its video stream.
Frames start at 0 and increment
by 1 each frame.
VideoData
if CodecID = 2 H263VIDEOPACKET
Video frame payload
if CodecID = 3 SCREENVIDEOPACKET
Ad Submission Guidelines:
Submit all advertising elements and URLs to your Microsoft Account Executive, Account Manager or Sales Planner.
United States submissions may alternately be submitted directly to [email protected].
Required Submission Information: Please include the following information with your submission (placement of your
order may be delayed if any required information is missing):
• Submission information must include: Advertiser Name, Microsoft Order Number, Creative Start Date
• Completed Creative Submission Document (CSD) or specific instructions on how ad element(s) should run, rotate, and/or replace other creative must also be included. The CSD or specific instructions will include creative file name, click though URL and alt text for each MSN placement, as well as the rotation percent of each creative. Contact your MSN account representative for more information.
o Creative may not contain “fake html” functions. This includes, but is not limited to, drop down boxes, text boxes and radio buttons. For more information, please view MSN’s Creative Acceptance Policy.
• Please also include all advertising elements (as individual files, ZIP archives, or via third party served Web site), including SWF, GIF, JPEG and HTML files. Specify a down level or backup gif for Flash creative. Additionally, all custom fonts used within the Flash files must also be submitted.
Creative Processing Turnaround Times SLA
Turnaround Time
Creative Type
Product Type
1. locally served .gif
2. 3rd party served .gif
•
Featured Offers
3rd party served
HTML
HTML
Flash
•
MSN Rich Media
(processed by Ops)
•
JavaScript/DHTML/Ne
tshow
•
MSN Rich Media (sent
to test)
5 full business days
•
hard coded ads
•
advertorials
•
•
streaming media
Home Page Content
Sponsorship
•
•
•
46
Examples:
• GIF/JPEG Creative/copy changes that should start on a Monday morning must be received by the beginning of the business day PST/PDT the previous Thursday.
• Hard coded creative/copy changes that should start on a Monday morning must be received by the beginning of the business day PST/PSD the previous Monday.
• One week advanced notice is recommended for new advertisers.
Note Any element not meeting spec will be returned for revision, which may delay the expected live date. To
review any creative spec, please see the MSN Advertising Web site.
If you have any questions regarding creative submissions, please e-mail your Microsoft Account Executive, Account
Manager or Sales Planner.
Disclaimers
(A) Click-through tracking is not available on the following advertising elements:
• HTML advertising elements that use method=”POST” for form submittal.
• Rich media elements that use embedded or compiled URL information (Macromedia Flash creatives that do not use the FS command, for example).
• Third party served HTML (IFrame) campaigns.
(B) Cache-busting is available automatically for pre-approved third party served agencies, others by request only. Exception: Third party served click URLs for hard-coded placements (text links, etc.) are not cache busted. Therefore, MSN
click data for hard-coded placements using third party served click URLs may not match click data from the third party
agency. Please enter the Cache busting tags; MSN is not responsible for entering these tags.
(C) Different MSN properties (MSN Money, MSN Hotmail, etc.) have different rich media acceptance requirements.
Please consult the MSN Advertising website for the most current specifications:
• MSN Rich Media Guide
• MSN Rich Media Solutions
• Third Party Rich Media
• Individual site pages for product acceptance
• Creative Acceptance Policy
(D) Reserved parameters:
• The PID= parameter is currently used by the MSN reporting system. If any linking URL contains this parameter click-through data will not be recorded for the ad placement. This parameter has no current workaround; escaping/
encoding will not work.
• The CLICK= parameter was previously used in click-through tracking URLs on TPS HTML creatives. This is no longer supported. This applies to all URLs except Unicast Enliven products. This parameter has no current workaround;
escaping/encoding will not work.
47
Video
Eksempel
s e sp e cs
s e sp e cs
2 5 0 pi x e ls
3 0 0 pi x e ls
60
pi x e ls
3 0 0 pi x e ls
Msn video
Specifikationer
4:3 Aspect Ratio Streamin Video
Udbyder
Dimensioner
(BxH)
Filstørrelse
CPM
320x240
1000k
16:9 Aspect ratio
Third Party
Microsoft served
served filetypes
file types
WMP 9 via
BetaSP
encoding
None
Udbyder
Dimensioner
(BxH)
Filstørrelse
CPM
423x240
1000k
Udbyder
Dimensioner
(BxH)
Filstørrelse
CPM
300x60
20k
Epanding ad (includes expanded & resting state)
Udbyder
Dimensioner
(BxH)
Flash
CPM
300x240
50k
Udbyder
Dimensioner
(BxH)
Filstørrelse
CPM
300x240
20k
Third Party
Microsoft served
served filetypes
file types
Flash
None
Third Party
Microsoft served
served filetypes
file types
WMP 9 via
BetaSP
encoding
None
300x60 Image
Third Party
Microsoft served
served filetypes
file types
None
JPG
Additional Specifications
300x240 Image
Third Party
Microsoft served
served filetypes
file types
JPG
None
Udbyder
Product type
Dimensioner
(BxH)
Click-thru
URL Limit
Audio
Limit
CPM
Streaming
Media
300x60
450
characters
?
Ad duration
15
sekunder
Animation
Alt text limit
Max Lenght
(in seconds): 30;
Loop limit: 2
65 char.
incl spaces
Brugeroplevelsen
The MSN Video Ad consists of three elements
• 15 second streaming ad (4:3 aspect ratio - 320x240 or 16:9 aspect ratio - 426x240)
• 300x250 defaults open upon play of streaming video ad
• 300x60 horizontal ad that remains present during the video ad stream and the following content clip.
1. The user chooses to view streaming content on MSN and clicks a streaming link.
2. The streaming ad plays and the 300x250 banner expands to the left.
a. MSN Video Player will essentially ’hide’ the control buttons during the streaming ad play which will not allow the user the opportunity to stop the stream during the ad. The only option the user will have to close out of the advertisement is by closing the player completely.
b. If the advertisement is stopped or closed, the user will not see the selected content stream..
c. Users do have the option of closing the 300x250 ad while it is expanded. Closing this element will not stop the pre-roll or alter the 300x60
3. Upon completion of the advertising stream, the expanding section will retract back into the player.
4. The selected streaming content plays.
5. The 300x60 horizontal ad that corresponds to the streaming video ad as well as the 300x250, remains present during video stream and following content clip.
6. This combined ad experience appears after every 180 seconds of content have been played. This can be any num
ber of short clips totaling 180 seconds or after a single piece of content longer than 180 seconds. The case where a clip exceeds 180 secs, an ad will be played immediately after the clip is complete.
7. There is no ad shown when the content stream is user generated content from Soapbox.
48
Video
Data Reported
Impressions, Click-through, Flash First Play, Flash Replay. Note: tracking provided on expanding Flash portion of the
product only.
Ad Specifications
Streaming Ad Requirements
The player is built to feature streaming content/ads in a 4:3 aspect ratio window. There are 2 options for the streaming
ad placement:
• Submit BetaSP tape to be converted to digital format, or;
• Submit digitized file. Accepted video formats (note: these formats will be re-encoded into WMV)
o Windows Media Format
o QuickTime
o MPEG
• Sound is required
Streaming Requirements: BetaSP
• 15-30 second Beta SP tape
• Submitted to Origin Digital for Encoding to WMP 9 streaming file (see submission location guidelines below)
Streaming Requirements: Digital File
• Max file size = 2MB
• Digital files should be built to fit either 4:3 (w320x240h) frame dimensions or 16:9 (w426x230h) frame dimensions
300x60 Expanding Ad Requirements
There are 2 options for submitting the expanding ad unit:
• 2 .jpg images
• Flash file
Expanding Ad Requirements: 2 .jpg images
• 1 – 300x60 .jpg file
• 1 - 300x250 .jpg file
• .jpg ONLY supported – unable to support .gif or animated .gif images
• Max file size = 20k per each file
• Maximum of 2 Click-through URL’s allowed/required - 1 for the 300x60 .jpg, 1 for the 300x240 .jpg
Limitations:
• Only .jpg images can be submitted (cannot use .gif)
• Third-party served .jpg images will not be supported. All images must be hosted by MSN
• .jpg files will be dynamically imported into a MSN Flash container
• Functionality is not as customizable as creating a pure Flash file is
o Only 2 click-through URL’s will be allowed (1 for the 300x60 .jpg, 1 for the 300x250 .jpg)
o Expand/Collapse labels will be contained in the common .swf file which will be referenced and will provide the expanding functionality of the 2 .jpg images. Agencies/clients will not have the ability to create their own labels and customize placement of those labels. Labels will sit in the top right hand corner to ‘expand’ and the top left hand corner to ’collapse’.
See illustration below:
49
Video
Expanding Ad Requirements: Flash
• Single Flash file containing the expanding and resting portions. The Flash stage should be set to 300x250
o Fully expanded state = 300x250
o Collapsed state = 300x60
• Flash 5.0 or above
o If Flash 6 or above is used, the following code must be present (exactly as shown) as a frame action on frame 1 of the Flash file.
o System.security.allowDomain(fd);
• Max file size = 50k
• Maximum of 2 loops
• Both the .swf and the .fla file must be submitted during the submission process
• Click command should open new window
• Build in ability to expand/collapse creative (with labels on creative) after initial 15 - 30 second ad play has finished
• Tracking tags should be submitted in the following format:
Example:

http://ad.doubleclick.net/click;h=v2|3323|0|0|%2a|g;6531562;0-0;0;8588164;31-1|1;3756702|3774598|1;;%3fhttp://msn.
com/msn/data/promo/

http://ad.doubleclick.net/imp;v1;f;6531562;0-0;0;8588164;1|1;3756702|3774598|1;;cs=f%3fhttp://m.doubleclick.net/dot.
gif
• Note that MSN does not support the ability to implement ’ad’/’jump’ tracking tags.
• Built-in ability to expand/collapse creative (with labels on creative) after initial 15-second ad play has finished
• Use single Flash file including the 300x60 banner ad with expanded 300x250
• Audio must never be used to avoid conflict with streaming TV commercial audio
• Animation is limited to first 15 - 30 seconds; continuous looping animation not accepted
o Extremely light (if any at all) animation should be used to avoid conflict with the streaming video portion. This
placement should be used more as a billboard that enhances the streaming video rather than an animated banner
o Interactive functions in the expanding state are recommended to invoke user interaction but must stop if the user collapses the ad
• Flash files require that an FSCommand is embedded in the file. See Flash guidelines below.
• Creative must feature a 1 pixel border (gray [#666666] or black [#000000] is recommended, though any color that clearly distinguishes the ad from the content may be used)
• There will be no down-level experience for the streaming ad. If user does not meet the minimum requirements, the MSN Video Player will not open
• User control, COLLAPSE must only be visible AFTER the first play. User control, EXPAND must only be visible in the 300x60 residual banner state. The user should not have the option to COLLAPSE the expanded portion when the corresponding TV Commercial is playing
• The duration of the Flash asset on the first expansion is controlled by the streaming video commercial and not in the Flash asset itself. (see Flash file structure below) If the streaming commercial is :15 seconds, the Flash ad will remain expanded for the same duration. After the ad is collapsed the user can again expand the ad, but must manually collapse the ad or the ad will remain in the expanded state.
Flash File Structure: If you have not received the .FLA template that includes all of the below code, please contact
your sales representative. FLA Template (Flash MX) – The .FLA template contains all of the necessary MSN code to make
the ad function. Please refer to this spec document and the instructions layer in the Flash file for clarity.
Video
50
51
Video
Flash Ad Requirements
The Flash vendor creating the swf file must adhere to specific coding requirements of the Flash file. They are as follows:
1. There will be one Flash file representing the expanded banner (300x240) and the residual banner (300x60) experi
ence. The residual banner component will contain an EXPAND button that, when user initiated, will expand the ad. All clear gif tracking calls will be initiated either by the load of the banner Flash, or by an fscommand() within the banner file that will initiate an http call.
2. Frame 1 of the banner component should not have any animation, sound or graphic.
3. The code that must appear in the invisible button (click-through URL button) on top of the banner file is:
on (release) {
fscommand(”URL1”);
}
4. Code to be used in the EXPAND button
on (release) {
fscommand(”NGAPReplay”, ”NGAPExpand”);
}
5. Code to be used in the COLLAPSE button The FLA template includes this code and the buttons may be custom
ized and relocated, as long as it is clear to the user that they are present and they function
on (release)
{
tellTarget (”/”) {
gotoAndPlay(”NGAPCollapse”);
}
fscommand(”NGAPCollapse”);
}
FSCommand Descriptions
Command: URL1
Parameter: None
Description: This will invoke the URL based on information that is completed at the time of the ad creation.
Example: fscommand(“URL1”) - will go to a URL specified when creating the ad.
Command: NGAPReplay
Parameter: Optional Frame Number
Description: When the replay button of a Flash asset is clicked, the movie will either rewind and start playing at the first
frame, or it will go to the optional frame number and begin playing.
Example: fscommand(“NGAPReplay”, “2”) - will go to frame 2 and begin playing. Since frame 1 is blank, frame 2 should
be designated as the start of the replay.
Frequency control for the streaming ads is such that a user will see an advertisement upon selection of every other
content stream. The streaming ad will also run in parallel with an expanding ad (420x240) which will take over the
meta data content section during the 15 second duration of the advertising stream.
Ad opens into new browser.
Submission must include the following ad components:
1. File Name/Clip Name
2. ISCI Code
3. jpeg files or expanding flash file
4. Click-thru URL
5. Timing
6. Length of Video (in seconds)
7. Aspect Ratio
52
Video
Advertisers will be contacted by their Technical Account Managers within one business day of tape receipt.
Digital file submissions
Digital Files (i.e., .avi, .mpeg) should be sent to your Technical Account Manager.
If Flash Format:
Before flash creative components can be implemented, the expanding ad unit must be QA’d and approved to run
AM sends the expanding flash ad to the TAM with the following elements.
• FLA file
• Fonts
• SWF files
• Creative Mapping Instructions
• Encoded Stream
• DL survey/JavaScript tag (if being used)
53
Take-over med Eyeblaster.
Eksempel
x pi x e ls
x pi x e ls
60
pi x e ls
7 2 8 pi x e ls
3 0 0 pi x e ls
3 0 0 pi x e ls
FØR TAKEOVER
EFTER TAKEOVER
Andre Eksempler
EFTER TAKEOVER
EFTER TAKEOVER
Specifikationer
Take-over
Udbyder
Ikke udbudt
af MSA,
udbydes af
tredjepart
Dimensioner
(BxH)
Flash
GIF/JPG
300x250
40k
20k
728x90
30k
15k
Animation
Lyd
Maks. 15
sekunder
og
uendeligt
loop
Bruger
aktiveret,
tilladt
ved klik
Streaming
Maks. 30
sekunder
Video
Ramme
Clicktag
staves*
2,2 MB
1 pixel grå
ramme om
banneret.
Ingen ramme
for høfligt
kreativt element.
(Expanded)
Se
Eyeblaster
specs
Retning For Paneludvidelses Størrelse
Annoncen må udvide sig til at fylde hele siden.
Brugeroplevelsen
• Brugeren besøger MSN’s hjemmeside.
• To display-annonceenheder præsenteres for slutbrugerne: 300x250-display-annoncen og 300x165-spotlight-elemen
tet, hvilket giver dem en Rich Media-oplevelse.
Bemærkninger til annoncespecifikationer
• Størrelserne på begge kreative elementer skal oplyses.
Politik for accept af kreative elementer
Annoncen skal overholde kravene i Microsofts ’Politik for accept af kreative elementer’.
Lyd
Link-aktiveret lyd er tilladt i enten den 300x250 store display-annonce eller i 300x165-spotlight-elementet. Klik-aktiveret ledsagende lyd accepteres enten i 300x250-display-annoncen eller 300x165-spotlight-elementet i eksponeringer,
som anvender video.
54
Take-over med Eyeblaster.
Video
1.Værtsaktiveret video kan bruges i enhver del af 300x250-display-annoncen eller 300x165-spotlight-elementet.
2.Videovarighed: 30 sekunder.
3.Al ledsagende lyd skal startes af brugerklik.
a.Hvis der anvendes lyd, skal det kreative element indeholde en mute-knap eller en automatisk on/off-omskifter.
Genafspilninger af video skal være brugeraktiverede.
Yderligere kreative elementer
1.Video og andre ’høfligt’ downloadede aktiver er acceptable.
2.Maks. størrelse for hvert videoaktiv: 2,2 MB.
Certificerede Rich Media-leverandører
Det amerikanske marked:
1.Understøttes eksklusivt af Microsofts Premier Media Group
Alle andre markeder:
Kontakt venligst din account manager
Rapporterede data
1.Microsoft-understøttede løsninger: forevisninger, klik, tilgængelige interaktionsmetrikker (evaluer/godkend tilgæn
gelige interaktionsmetrikker med dit Account Team).
1.Microsoft rapporterer klikdata til de følgende tredjeparts-partnere:
1.Atlas Rich Media (kun Rich Media-annoncer)
2.Eyeblaster
3.Tangozebra
4.Eyewonder
5.United Virtualities
6.Admotion
7.Unicast
8.Flashtalking
• Tredjeparts-Rich Media: Tredjepartspartnere vil normalt levere forevisninger og gennemkliksdata samt forbedrede
interaktionsmetrikker. Få flere oplysninger hos din ønskede Rich Media-partner.
Dataindsamling
• Microsoft tillader annoncører at indsamle brugerafgivne personlige oplysninger (eksempelvis gennem web-formularer, som er indlagt i annoncer).
• Annoncørerne kan blive pålagt at redigere annonceenheder eller foretage yderligere offentliggørelser, for at de kan
være acceptable til annoncering på Microsofts sider.
• Annoncører, som ønsker at indsamle personlige oplysninger (i overensstemmelse med specifikationerne herover) i
annoncer, skal følge disse retningslinjer:
o Identificer organisationen tydeligt.
o Inkluder et link til fortrolighedspolitikken (normalt i nærheden af web-formularens ’Indsend’-knap).
o Forklar formålet med indsamlingen af oplysningerne.
Retningslinjer for indsendelse
• Microsoft-standard
55
Games
Eksempel
? pi x e ls
? pi x e ls
messenger klient
games
Specifikationer
Games
Dimensioner
(BxH)
300x250
Flash
30k
GIF/JPG
20k
Microsoft Served
File Types
Third Party Served
File Types
DHTML, Flash,
Maks. 7
GIF, HTML,
sekunder
og uendeligt Javascript/jscript,
JPEG, No support
loop
for fly-out ads
DHTML, Flash,
GIF, HTML,
Javascript/jscript,
JPEG, No support
for fly-out ads
Animation
Click-thru
URL Limit
Alt Text
Limit
450
25 char. incl.
characters
spaces
The End User Experience
1. The user opens and signs into MSN Messenger.
2. The user clicks on the Launchpad icon in the top navigation of the Messenger window.
3. The Games and Applications drop-down menu appears.
4. The user chooses a Game to play.
a. If it’s a 2-person game, the application will prompt the user’s MSN Messenger contact to opt-in to the game.
5. As the game begins to load, a 300x250 interstitial creative will appear, lasting for 15 seconds.
6. The game will appear.
7. Once the game has ended, upon exit the user will see a 300x250 creative.
Games
Data Reported
Ad requests & click-through. MSN will NOT be reporting on click-through for 3rd party served rich media (i.e. Flash
served by a 3rd party serving agency).
Ad Specifications
• Audio must be user-initiated and never automatic
• Audio insertion into flash file may begin no earlier than the second frame.
• If audio is used, creative must include an On/Off switch for users.
• All DHTML creative submissions need to have an accompanying default graphic that is shown to users that do not have IE 4.0 or higher
• Animation is limited to 7 seconds. Use animation carefully: Keep animation smooth and fluid, using slow motions and gentle fades. Fast and abrupt motion has been shown to be highly irritating. Avoid experiences that ’break-
through’ the page or abuse the content.
• Flash files require that an FSCommand is embedded in the file. For detailed Flash guidelines, visit advertising.msn.
com.
• Creative must feature a 1 pixel border (gray [#666666] or black recommended, though any color that clearly distin
guishes the ad from the content may be used)
• Ad opens into new browser.
Ad Submission Guidelines
Network Standard
Submit all advertising elements and URLs to your Microsoft Account Executive, Account Manager or Sales Planner.
United States submissions may alternately be submitted directly to [email protected].
Required Submission Information: Please include the following information with your submission (placement of your
order may be delayed if any required information is missing):
• Submission information must include: Advertiser Name, Microsoft Order Number, Creative Start Date
• Completed Creative Submission Document (CSD) or specific instructions on how ad element(s) should run, rotate, and/or replace other creative must also be included. The CSD or specific instructions will include creative file name, click though URL and alt text for each MSN placement, as well as the rotation percent of each creative. Contact your MSN account representative for more information.
o Creative may not contain “fake html” functions. This includes, but is not limited to, drop down boxes, text boxes and radio buttons. For more information, please view MSN’s Creative Acceptance Policy.
• Please also include all advertising elements (as individual files, ZIP archives, or via third party served Web site), including SWF, GIF, JPEG and HTML files. Specify a down level or backup gif for Flash creative. Additionally, all
custom fonts used within the Flash files must also be submitted.
Creative Processing Turnaround Times SLA
Examples:
• GIF/JPEG Creative/copy changes that should start on a Monday morning must be received by the beginning of the business day PST/PDT the previous Thursday.
• Hard coded creative/copy changes that should start on a Monday morning must be received by the beginning of the business day PST/PSD the previous Monday.
• One week advanced notice is recommended for new advertisers.
Note Any element not meeting spec will be returned for revision, which may delay the expected live date. To
review any creative spec, please see the MSN Advertising Web site.
If you have any questions regarding creative submissions, please e-mail your Microsoft Account Executive, Account
Manager or Sales Planner.
56
57
Games
Disclaimers:
(A) Click-through tracking is not available on the following advertising elements:
• HTML advertising elements that use method=”POST” for form submittal.
• Rich media elements that use embedded or compiled URL information (Macromedia Flash creatives that do not use the FS command, for example).
• Third party served HTML (IFrame) campaigns.
(B) Cache-busting is available automatically for pre-approved third party served agencies, others by request only. Exception: Third party served click URLs for hard-coded placements (text links, etc.) are not cache busted. Therefore, MSN
click data for hard-coded placements using third party served click URLs may not match click data from the third party
agency. Please enter the Cache busting tags; MSN is not responsible for entering these tags.
(C) Different MSN properties (MSN Money, MSN Hotmail, etc.) have different rich media acceptance requirements.
Please consult the MSN Advertising website for the most current specifications:
• MSN Rich Media Guide
• MSN Rich Media Solutions
• Third Party Rich Media
• Individual site pages for product acceptance
• Creative Acceptance Policy
(D) Reserved parameters:
• The PID= parameter is currently used by the MSN reporting system. If any linking URL contains this parameter click-through data will not be recorded for the ad placement. This parameter has no current workaround; escap
ing/encoding will not work.
• The CLICK= parameter was previously used in click-through tracking URLs on TPS HTML creatives. This is no longer supported. This applies to all URLs except Unicast Enliven products. This parameter has no current workaround; escaping/encoding will not work.
58
In Game Advertising
Ad Specs
Please submit ALL of the standard sizes listed below. Most ad sizes appear smaller in-game:
Specifikationer
Creative Static Sizes
Primary sizes
Secondary sizes
Format
Naming files
512x512
256x512
512x256
512x128
256x256
128x128
128x256
256x128
512x64
72 dpi RGB Photoshop Layered Format
“Advertiser_512x512.psd”
Text in your ad should
be large and kept brieft
Lorem Ipsum is simply dummy text of the printing and
typesetting industry. Lorem Ipsum has been the industry's
standard dummy text ever since the 1500s, when an
unknown printer took a galley of type and scrambled it to
make a type specimen book. It has survived not only five
centuries, but also the leap into electronic typesetting,
remaining essentially unchanged. It was popularised in the
1960s with the release of Letraset sheets containing Lorem
Advertiser logo
Advertiser logo
Video Specs
Ratio
Length of Video
Size
Format(s)
2x1
15 seconds maximum
1-5 MB
MOV, MPEG/MPG/MP4,
MPV, WMV
Creative End–to–End Process
1. CLIENT SUBMITS CREATIVE: Photoshop layered files and video(if applicable) are uploaded to Massive FTP.
www.massiveincorporated.com/creativeupload(username / password: upload/upload). Please refer to ad specs for file
dimensions and video formats.
2. CREATIVE REVIEW (1 BUSINESS DAY on average): Depending onlist of games for this campaign the Creative Services
team will resize to various formats, mostly within same ratio, and if necessary make minor adjustments / suggestions
(if font too small to be read in-game, contrast too low, URL not visible etc.)
3. CLIENT PRE-APPROVAL: Client reviews creative. This step is meant to allow client to review creative one last time
before all of the assets are created for the respective titles. Please verify all trademarks, legal and logos are correct.
4. CREATIVE INTEGRATION(3 BUSINESS DAYS on average): Creative Services integrates the pre-approved creative into
each of the titles for this campaign, and takes screenshot samples within the games in an actual “live” gaming
environment on Massive’stest servers (which mirror exactly how the real life gamer will see the ads).
5. CLIENT FINAL APPROVAL: Client receives final media assets (complete assets for all games)and screenshot samples.
Please refer to screenshot samples for realistic visuals of ads in games. Media Assets often feature templates and
textures to adjust to each title’s gaming environment.
6. PUBLISHER APPROVAL: Once final approval is given by the client, the campaign is sent to the game publishers for
final sign-off before being sent live (average APPROVAL TIME 2-3 BUSINESS DAYS).
7. CAMPAIGN GOES LIVE!
59
In Game Advertising
Creative Integration Best PracticesCreative
Creative Recommendation
• Creative assets to be delivered at least 14 days prior to campaign start date. Possibility of campaign to be delayed if
not delivered on time.
• All creative assets are to be delivered in our standard Photoshop Layered formats
• Creative media assets should be simple and not too copy heavy
Creative Best Practices
Creative Guidelines
• Simple and clear creative layout.
• Brief copy and easy to read text.
• Brand Recognition/Clear and memorable images.
• High contrast colors in ad –high contrast between text and background
• Use strong bold fonts
Eksempel
60
In Game Advertising
Logo Based Games
For maximum visibility, it is recommended for creativesin Sports and Racing games to be logo based:
• NBA
• NHL
• Project Gotham Racing
• Pro Evolution Soccer
• Sensible World of Soccer
• Tiger Woods
• Guitar Hero 3
Eksempel
61
Messenger TV
The Ad Experience
• The MSN Inline Video Ad consists of a 15 – 30 second streaming ad (4:3 aspect ratio - 320x240 or 16:9 aspect ratio
(426x240) and a 300x60 horizontal ad. Check with your local MDAS representative for maximum duration of
streaming ad.
• The user clicks to play a content stream. The content is preceded by a video ad with a 300x60 clickable JPEG below. The selected content plays after the video ad and the 300x60 persists below the content until the end of the con
tent stream.
• Between streams, when a new video ad is not called, a new 300x60 JEPG will appear. New video ad and associated 300x60 will stream after 180 seconds of content have played (might vary from market to market).
Eksempel
30
120
60
pi x e ls
2 1 6 pi x e ls
3 0 0 pi x e ls
3 0 0 pi x e ls
The End-User Experience
1. The user chooses to view streaming content on MSN and clicks a streaming link on the inline player.
2. The streaming ad plays and shows the 300x60.
o The user may stop or pause the ad.
o But, the selected content cannot be viewed unless the ad stream completes playing.
3. The selected streaming content plays.
4. A streaming ad appears after 180 seconds of content have been played (might vary from market to market).
Data Reported:
Impressions, Click-through on 300x60
Ad Specifications:
Streaming Ad Requirements
The player is built to feature streaming content/ads within a 16:9 window. However, MSN Video will still be able to support the submission of streams using a 4:3 window.
• Submit digitized file. Accepted video formats (note: these formats will be re-encoded into WMV)
o QuickTime
o MPEG
• Sound is required
Streaming Requirements: Digital File
• Max file size = 2MB
• Digital files should be built to fit either 4:3 (w320x240h) frame dimensions or 16:9 (w426x230h) frame dimensions
62
Messenger TV
Ad Specifications:
• Preferred 15 seconds maximum. Will accept up to 30 seconds maximum.
• Submit digitized file. Accepted video formats (note: these formats will be re-encoded into FLV):
o QuickTime
o MPEG
Specifikationer
4:3 Aspect Ratio Streaming Video:
Dimensioner
(BxH)
Text Length
File Weight
Flash File Weight
Microsoft Served File Types
Third Party Served File Types
320x240
n/a
1000k
n/a
WMP 9 via BetaSP encoding
None
16:9 Aspect Ratio:
Dimensioner
(BxH)
Text Length
File Weight
Flash File Weight
426x240
n/a
1000k
n/a
WMP 9 via BetaSP encoding
None
300x60 Image:
Dimensioner
(BxH)
Text Length
File Weight
Flash File Weight
300x60
n/a
20k
n/a
JPEG
None
Additional Specifications:
Product Type
Overall
Dimensions
Click-thru
URL Limit
Audio Limit
Ad Duration
Animation Max.
Length (in seconds)
Loop Limit
Streaming Media
300x60
450 chars
n/a
15 seconds
15 seconds
n/a
Alt Text Limit
65 char.
incl. spaces
Creative Business Requirements: Digital file submissions
Digital Files (i.e., .avi, .mpeg) should be sent to your Technical Account Manager.
300x60 Ad Requirements
• JPG Image only
• Max file size = 20k
• Limitations:
o Only .jpg images can be submitted (cannot use .gif)
o Third-party served .jpg images will not be supported. All images must be hosted by MSN
63
Nyhedsbrev
Eksempel
email
Specifikationer
Email
Bredde
Højde
GIF/JPG
MSN Served
file types
Third party
served file
types
500
300
25k
GIF, HTML,
JPG
None
Animation Alt text limit
Nej
See below
Overall
dimensions
E-MAIL_E
Rapporterede data
Subscribers, Deliveries, Opens and Clicks data of users who opened offer e-mails (click information is aggregate for
mailing) will be available through online reporting on http://adreport.msn.com 72 hours after delivery
Ad specifications
Please choose from one of these two mailing formats of e-mail creative: Single Image or Free-Form HTML. Prepare the
creative according to the specs below and submit with the submission template provided by your Microsoft Account
Representative.
Single Image E-mail creative
For Single Image e-mails, it is only necessary to send an image, URL, alt text, and subject line. No HTML is necessary.
• Total file size for image should be 25K or less
• GIF or JPG dimensions: 500 width x 300 height
• Alt-text: 80 characters max, including spaces
• Click-through URL
• Subject line needed for each mailing: 40 characters max, including spaces; sentence case*
• *Acceptance of subject line provided by the advertiser is subject to legal/editorial review
• No animation or rich media will be accepted
• Content must be directly related to targeted category
Note: Creative (complete and to the spec) must be submitted to your Microsoft Account Representative at least 3
business days prior to mail delivery.
64
Nyhedsbrev
HTML E-mail creative
For Free-Form HTML e-mails, it is only necessary to send an HTML file and subject line. Images must be hosted on the
advertiser’s server.
• Total file size for HTML + images must be 25K or less
• Dimensions: 500 width x (no height restriction)
• Subject line needed for each mailing: 40 characters max, including spaces; sentence case*
• *Acceptance of subject line provided by the advertiser is subject to legal/editorial review.
• No auto downloads of program/software directly from link within e-mail. Any downloads must take place from
advertiser’s site
• No animation or rich media will be accepted
• Content must be directly related to targeted category
• Only error-free HTML will be accepted. HTML must be run through an HTML validator program for any errors and
warnings. You can get a good freeware HTML validator at: http://www.htmlvalidator.com/lite/. It is suggested that you
check your HTML in Firefox.
• See HTML Technical Specifications below
Note: Creative (complete and to the spec) must be submitted by advertiser to Microsoft Account Representative at
least 3 business days prior to mail delivery date for Microsoft Offers customers.
Microsoft Offers HTML Rules & Guidelines
The HTML code that you use to create your content will appear within Hotmail’s HTML which uses its own style sheet
to format the look and feel of Hotmail; therefore we need you to comply with some simple but important coding
guidelines. Some codes that may work in a browser alone may not be permissible in MSN Newsletter content.
Creative booking instructions
The completed Order Confirmation template and creatives should be provided to the appropriate Ops/Sales contacts
(depending on region) to ensure successful implementation into the ACDM platform.
Order Confirmation Template
Ad submission guidelines
Submit all advertising elements and URLs to your Microsoft Account Executive, Account Manager or Technical Account
Manager.
Please include the following information with your submission (placement of your order may be delayed if any required
information is missing):
• Advertiser Name
• Mailing Delivery Date
• Name of your Microsoft Account Executive/Account Manager
• Advertising Elements (as individual files, or a ZIP archive, or via third party served Web site), including all Flash
source files (FLA and all supporting SWF files) and any custom fonts
• Choice of mailing template e.g. Single image or HTML
• Microsoft’s confirmed order number
• Category name
All advertising elements must be submitted complete and to the spec at least 3 business days prior to the mailing
delivery date for report Microsoft Offers customers. If you have any questions regarding submissions, please e-mail
your account representative. Note: Any element not meeting spec will be returned for revision, which may delay the
expected live date.
MSN will not accept any adult and/or ’borderline’ adult content, whether directly or indirectly promoted, for any categories within Hotmail Featured Offers. This includes, but is not limited to the following:
• Images of teenagers/adults that reveal any nudity and/or near nudity such as nipples, genitals, buttocks, excessive
cleavage, scantily clothing, etc.,
• Images of people in positions or activities that are excessively suggestive or sexual in nature
• Images containing text that either in itself and/or in combination with an image are excessively suggestive or sexual
in nature
MSN reserves the right to make exceptions to these guidelines on a case-by-case basis at any time as well as to make
changes and add to this at any time and for any reason.

Tekniske specifikationer

Transcription

Similar documents

Haix Fire Flash® Pro

NetApp Nyheder - Fujitsu | Storage Club

RABALDER PROGRAM PARKEN

Dit liv er et mesterværk

2X-F-seriens brandcentraler, kompatibilitetsliste

R1C1 R1 SU-800 SB-R200

SB-800 - Til jankruse.dk

New

SB-600 Dk

Mediainfo 2016 Ugeskrif for Læger (English)

Rubow_lowres

“sådan virker reklame!”

87205 DK ALDI N Content MSN 5004 8319 Final REV1.indd

Monte Carlo på DR3 brugerinvolvering på Twitter, Snapchat og Relay

Free entrance - Odense International Film Festival

bogen som pdf - Statens Museum for Kunst