GAD Process: Eyeblaster Training. September, 17 2009. Overview. This deck is designed to capture the production, trafficking, and reporting considerations for campaigns using Eyeblaster to traffic rich media – in particular, BIEB. Included are: Production Considerations
September, 17 2009
The decision of whether to use the Eyeblaster (EB) version of media or standard flash file is a local decision.
If adopted in your market, Eyeblaster will issue local credentials to WUN subs to access their local accounts.
In addition to the usual delivery of files thru the Xinet system (swfs, FLAs, fonts, etc), the creative agency will also deliver the following:
ProjectLogosSmartV_300x250 (Ad ID: 1872264)
Edits can be done using the Eyeblaster’s Smart Versioning tool.
Smart Versioning is an online tool that will not require you to purchase fonts or recompile Flash. Edits to both copy and images can be done within the tool.
Note: If you need to change the publisher’s specs or make fundamental animation changes you will need to edit the Flash. This method will be explained below.
To localize your ad:
7) Double click on any of the items you want to edit, make your changes and press “Apply”.
8) When all edits are done, click “Save” and we’re done.
If yes (resizes, market specific edits):
Local sub can open the EBC file with all needed assets and edit in Flash using the Eyeblaster Workshop to preserve all of the settings.
Finished assets can be previewed locally and uploaded directly to the Eyeblaster platform from Workshop.
Before the Ads can be assigned to specific placements by UM, WUN teams must:
Before tags are delivered to publishers, WUN teams must QA the assets against the publisher specs.
The Microsoft RIO Integration involves sending specific “cell code” information to an Atlas tag and to a Microsoft tag for their tracking purposes. The implementation is accomplished by the integration of two custom scripts.
Ad tag modification:
vargstrEbPreLoadScripts = "msft_interaction.js";
<a href="http://bs.serving-sys.com/BurstingPipe/BannerRedirect.asp?FlightID=944351&Page=&PluID=0&Pos=9272" target="_blank"><imgsrc="http://bs.serving-sys.com/BurstingPipe/BannerSource.asp?FlightID=944351&Page=&PluID=0&Pos=9272" border=0 width=300 height=250></a>
Recommended Eyeblaster naming conventions as will be reflected in reporting:
Video Asset Name
We are holding on Eyeblaster recommended naming conventions until we confirm compatibility with Atlas / RIO reporting.
Two tabs back from Smart Versioning you will find “Actions and Tracking”. Open this tab and you will find the default clickthrough URL. 3rd party tracking can also be done from here.
Instead of packaging files, building instructions and URLs, all that would need to be delivered is an Ad ID number. All asset QA and verification can be done on the Eyeblaster platform.
Where do I find the Ad ID number?
Log in to the Eyeblaster website.
Select the “Creative” tab on the far left and then click on “Ads.”
You will see a full listing of all ads in your account. Your Ad ID number is available here.
QA is handled through the Ad Campaign Manager (ACM).
QA is done on two dimensions:
• General preview – to check the expected behavior of the final ad on websites (expansion, close, clickthrough etc.)
• Assets preview – to check proper setup and functionality of each asset (default image\flash, rich, panels, video etc.)
Preview the ad
Check the ad’s general behavior and functionality using the interactions monitor.
In this example we see the click command triggered.
Edit the ad
(or right click and then Edit)
Preview the default image:
Check that the image dimensions match the ad dimensions and its size in KB
Preview the default flash asset:
See next slide
Check that default image/ flash size doesn’t exceed publisher spec
Interactions monitor is available here.
All asset sizes, types and frame rate info are listed here.
If you need to create a lowest common denominator spec for your region, Eyeblaster has a Publisher Spec tool available. This is found in the “Tools” tab under “Search Specs.”
Select your sites from the list and then click “View Specs.” You will be presented with a web version showing each individual spec in a column and also a LCD column. You also have the option to download as an XL document.
Atlas Reporting - both Atlas click tags and post-click "conversion" tagging will function normally and data will be retrievable from atlas.
RIO Reporting - Eyeblaster has worked with RIO team to implement minor adjustments to allow for standard RIO reporting. RIO team also working to import behavioral data from Eyeblaster so ALL data from Eyeblaster would be available in RIO.