1. Data and Reporting Workstream September, 17 2009 GAD Process: Eyeblaster Training

2. Deployment Meeting June 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 – Trafficking Workflow Summary – Data Collection & Reporting

3. Deployment Meeting June 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. Will Eyeblaster be used in your Market?

4. Deployment Meeting June 2009 Standard workflow Creative Agency provides - copy deck -.FLA file - image library local WUN takes Local Media Plan (and buys fonts) local WUN localize (translation, localization and re- sizing) local WUN does QA validation against media specs (size, weight) local WUN takes trafficking workbook and assigns banner per Atlas tags local WUN sends banner ads to UM for QA and tagging local UM does QA, creates Atlas tags and publishes banners to media placement local WUN and local UM collect reports for all-up IMAPS (& RIO) reporting

5. Deployment Meeting June 2009 Eyeblaster workflow JWT provides - copy deck -.FLA file -EBC and EBS Files -Preview link - image library local WUN takes Local Media Plan (and buys fonts) local WUN localize (translation, localization and re-sizing) Translation and localization are done in Smart Versioning local WUN does QA validation against media specs (size, weight) Done on Eyeblaster platform local WUN takes tagging matrix and assigns banner per Atlas tags Done on Eyeblaster platform local WUN sends banner ads to UM for QA and tagging Just send Ad IDs local UM does QA and Atlas tagging and publishes banners to media placement Done on Eyeblaster platform local WUN and local UM collect reports for all- up IMAPS (& RIO) reporting

6. Deployment Meeting June 2009 Production

7. Deployment Meeting June 2009 Assets In addition to the usual delivery of files thru the Xinet system (swfs, FLAs, fonts, etc), the creative agency will also deliver the following: 1)EBC file. This handles all of the Eyeblaster settings and has the FLAs contained in a single package. 2)EBS file. This will allow you to upload the ad to your local Eyeblaster account without editing the Flash files. 3)Eyeblaster preview of the original ad. This will allow you to see how it should function. ProjectLogosSmartV_300x250 (Ad ID: 1872264) ProductionTraffickingReporting

8. Deployment Meeting June 2009 Are Flash edits needed? If no: 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. ProductionTraffickingReporting

9. Deployment Meeting June 2009 Smart Versioning ProductionTraffickingReporting

10. Deployment Meeting June 2009 Smart Versioning To localize your ad: 1)Download the EBS file from Xinet. 2)Log in to the Eyeblaster platform at www.eyeblasterwiz.comwww.eyeblasterwiz.com 3)Select the “Creative” tab at left and click “Create Ad from Bundle.” ProductionTraffickingReporting

11. Deployment Meeting June 2009 Smart Versioning 4)Browse to your EBS file and then click “Upload Bundle and Create Ad” 5)In your ad list you should see a new ad at the top (may need to refresh the list). You can note the Ad ID number for later. 6)Double click to edit and then proceed to the “Smart Versioning” tab. ProductionTraffickingReporting

12. Deployment Meeting June 2009 Smart Versioning 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. ProductionTraffickingReporting

13. Deployment Meeting June 2009 Are Flash edits needed? 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. ProductionTraffickingReporting

14. Deployment Meeting June 2009 Trafficking

15. Deployment Meeting June 2009 Responsibilities Before the Ads can be assigned to specific placements by UM, WUN teams must: Complete RIO Preparation Enter Naming Information Enter Destination URLs Provide AD ID to UM Before tags are delivered to publishers, WUN teams must QA the assets against the publisher specs. ProductionTraffickingReporting

16. Deployment Meeting June 2009 Rio Preparation 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.  The first script msft_interaction.js was developed by Eyeblaster and utilizes some of our custom event handlers. Specifically, it uses our onHandleInteraction event which is triggered every time an interaction is triggered. The script checks to see if the interaction triggered in the list of RIO interactions (see above). If it is, it sends tracking information to an Atlas tag and the Microsoft tag. The information sent is Interaction, Placement ID and Cell Code.  The second script RioTracking2_Rmt.js was developed by Microsoft and is a JavaScript library we use to make the calls to the two tracking tags. ProductionTraffickingReporting

17. Deployment Meeting June 2009 Rio Preparation ProductionTraffickingReporting

18. Deployment Meeting June 2009 Rio Preparation Ad tag modification: var gstrEbPreLoadScripts = "msft_interaction.js"; ProductionTraffickingReporting

19. Deployment Meeting June 2009 Naming Conventions Recommended Eyeblaster naming conventions as will be reflected in reporting:  Campaign Name  Placement Name (Section Details)  Ad Name  Panel Name  Video Asset Name Campaign Name CountryCode_ CampaignName_Details UK_ itPro_FirstRelease Placement Name CountryCode_CampaignName_Site_Dimensions UK_itPro_MSN_300X250 Ad Name CountryCode_CampaignName_CreativeName_Dimensions UK_itPro_Product_300X250 Panel Name CreativeName_PanelName Product _Panel1 Video Asset Name CountryCode_CampaignName_VideoName_Length UK_itPro_Promo_30 We are holding on Eyeblaster recommended naming conventions until we confirm compatibility with Atlas / RIO reporting. ProductionTraffickingReporting

20. Deployment Meeting June 2009 Where does the URL go? Two tabs back from Smart Versioning you will find “Actions and Tracking”. Open this tab and you will find the default clickthrough URL. 3 rd party tracking can also be done from here. ProductionTraffickingReporting

21. Deployment Meeting June 2009 Hand off to UM 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. ProductionTraffickingReporting

22. Deployment Meeting June 2009 Hand off to UM 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. 1 2 3 ProductionTraffickingReporting

23. Deployment Meeting June 2009 Ad QA – overview 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.) ProductionTraffickingReporting

24. Deployment Meeting June 2009 QA on ACM Start with the ad preview Preview the ad ProductionTraffickingReporting

25. Deployment Meeting June 2009 QA on ACM Start with the ad preview Check the ad’s general behavior and functionality using the interactions monitor. In this example we see the click command triggered. ProductionTraffickingReporting

26. Deployment Meeting June 2009 QA on ACM Previewing the assets Edit the ad (or right click and then Edit) ProductionTraffickingReporting

27. Deployment Meeting June 2009 QA on ACM Previewing the assets Preview the default image: Check that the image dimensions match the ad dimensions and its size in KB Check that default image/ flash size doesn’t exceed publisher spec Preview the default flash asset: See next slide ProductionTraffickingReporting

28. Deployment Meeting June 2009 QA on ACM Previewing the assets All asset sizes, types and frame rate info are listed here. Interactions monitor is available here. ProductionTraffickingReporting

29. Deployment Meeting June 2009 Publisher Specs 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. ProductionTraffickingReporting

30. Deployment Meeting June 2009 Publisher Specs ProductionTraffickingReporting

31. Deployment Meeting June 2009 Reporting

32. Deployment Meeting June 2009 A couple of particulars... 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. ProductionTraffickingReporting

33. Deployment Meeting June 2009 Eyeblaster Reporting ProductionTraffickingReporting

34. Deployment Meeting June 2009 Sample Report ProductionTraffickingReporting

35. Deployment Meeting June 2009 Fin