1 / 39

New Publishing Process

Primary colors. EB Orange 246/137/51. EB Green 52/70/13. EB Gray 161/161/161. EB Yellow 255/200/40. Light tint. New Publishing Process. 250/196/153. 153/162/134. Presented by: Limor Nadav-Greenberg ● S olution Specialist ● 26 st Aug 2009. 208/208/208. 255/227/147. Dark tint.

Télécharger la présentation

New Publishing Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Primary colors EB Orange 246/137/51 EB Green 52/70/13 EB Gray 161/161/161 EB Yellow 255/200/40 Light tint New Publishing Process 250/196/153 153/162/134 Presented by: Limor Nadav-Greenberg ● Solution Specialist ● 26st Aug 2009 208/208/208 255/227/147 Dark tint 123/69/26 26/35/7 81/8181 128/100/20

  2. Content • Introduction • Overview of the New Publishing Process (NPP) • NPP in the ACM • Q&A • Upgrade Plan • Next Step

  3. The New Publishing Process - Introduction Rational • Remove obstacles and shorten work processes Eyeblaster should not be the bottle-neck and enforce unecessary work processes • Streamline the work process between media and publishers • Publishers work – less effort, less time Upgrade to NPP • All clients in one go (media, publishers and creative) • Separate from upgrade to MediaMind • First in Beta markets (ES, DE, NZ), then worldwide

  4. Overview of the NPP The New Process: • Ads are published • With one click - Agency generates and sends a code package to the publisher • Publisher receives an email with a link to preview ads and take tags • Publisher can log in to the system, preview, and reject ads • Agencies can republish rejected ads after solving the problem The Old Process: • Agency/Creative Shop sends ads for approval • Publisher logs in to the system, previews the ad, and approves it • Publisher is required to generate tags for all flights

  5. The NPP Workflow The publisher can log in to the ACM at any time, review ads, generate tags, and so on. However, this is now optional, not mandatory

  6. New Publishing Process in ACM

  7. Media View

  8. Publishing Campaign New button added to the Campaigns list Allows you to publish the whole campaign

  9. Publishing Campaign From this page: Select publishers Publish the campaign Send to contacts / yourself Add a note to publishers Send the code package to publishers.

  10. Select Site Contacts • If the user chose to send the code package to site contacts, • a floater window will open in which the user can: • Add a new contact. • Remove a contact from the recipients list.

  11. Select Site Contacts : Make sure there is at least one contact per publisher if a publisher has no contacts in this list – no one will receive the code package

  12. Select Site Contacts • When clicking Add New, another floater opens in which the user can: • Either select an existing contact to add to this list, • Or enter details of a new contact. • This contact will be added as a user to the publisher’s contact list.

  13. Messages Received Upon Sending the Code Package After selecting the site contacts, and clicking on 'send code' you will receive the message below Note: Each site will get his own code package!

  14. Messages Received Upon Sending the Code Package Would generate the IO Would cancel the action • Then the IO will need to be signed • Then generation of code package will be available Note: If IO has not been generated yet – you would get the message below

  15. Messages Received Upon Sending the Code Package Would send the code package Would not send it • Placements pending IO would appear with no tags • Placements with no published ads • would not appear at all If there are placements pending IO signature or with no published ads – you would be asked whether or not to send code package

  16. Recommended workflow (if IO is required) Set up campaign flights and ads Publish the whole campaign Click 'yes' to continue and generate the IO Sign the IO Publish the whole campaign again Select the relevant contacts for each publisher Send the code package to the selected publishers Mission is complete! Remember: If new flights are added to a campaign for which code package has already been generated – notify the publisher on the new flight or send them the code package again If you wish to publish a whole campaign without sending a code package to publishers – you can do it by sending it to yourself only

  17. Publishing the Campaign is Complete! Media initiates the process Once published – ads are immidiately available for serving All that is required now is for the publishers to take the tags (that were sent to them) and put them on their site.

  18. Publishers’ View

  19. Email Alert Sent to Publishers General Information Does not require a log in!

  20. Email Alert Sent to Publishers Plain Text Version (tags) Does not require a log in!

  21. Plain Text Version

  22. Email Alert Sent to Publishers Link to Code Package Does not require a log in!

  23. HTML Code Package • : Information in this page is always up to date!

  24. HTML Code Package • Link to EB will take the user to the relevant campaign (requires login) • The first section: “Action Required” – contains tags

  25. Account Settings

  26. Preview Placement Does not require a log in

  27. HTML Code Package • The second section includes flights that are live / pending IO (no tags)

  28. HTML Code Package • The second section includes flights that are live / pending IO (no tags)

  29. Get Tags Code package Email alert Publishers view summary Publisher recieves email alert  go to code package  review ads (optional through logging into ACM)  grab tags. Note: the publisher can login to ACM at all times to: Grab tags for published flights / for the whole campaign Regenerate tags according to different settings (if needed) Review and reject ads

  30. Additional Publishing Options

  31. Publishing Flights • In the ACM - Flights still need to be published before an ad can be published • If agency published a flight – it will be visible to the publisher in EB

  32. Ads ‘submitted’ will become published • Published ads will be immediately available for serving

  33. Publishing Campaign & Ads - Summary Publishing Options (for media) Whole campaign Individual ads Flight The Meaning of Publishing Published = approved (in the old process) Agency can publish an ad at any time: Attached Rejected Publisher and Agency can reject an ad (replaces the recall process)

  34. Q&A

  35. Important Upgrade Milestones Upgrade Method: 1. Sep 13th - First email notification 2. Sep 27th–Second notification; AMs start training major clients 3. Oct 11th–Release date; Third notification & Pop up message

  36. Email Notifications • Dear <client name / user name>, • We are pleased to announce several upcoming enhancements to the campaigns publishing process within the Eyeblaster Ad Campaign Manager (ACM). • Highlights of upcoming enhancements: • 1-click ad publishing, no time consuming approvals • Instant, fully functional tags for entire campaign • Auto code generation based on custom preferences • Click & Grab tags, no more fussing with logins or passwords •  The new campaign publishing process • Quick Start Videos • Agency users - click here for details (media & creative) • Site users – click here for details • What now? • For now there is nothing for you to do. We simply wanted to bring this plan to your attention. You will receive another alert on August 17 when the new process is launched. Then you can start enjoying all of its advantages. Until then, please contact me directly if you have any questions. • Sincerely, • <AM name> and the Eyeblaster Team

  37. Next Steps What is required of you now: Translate email notifications (optional). Send them back by Sep 4th Review and approve the recipients list for your region by Sep 4th Map your clients and decide which require in-person training Set up meetings with those clients Share with the UE team your training plans (please send it to me) Meet with clients and explain how the new process works Support clients when the NPP is released (Oct 11th ) Monitor upgrade to NPP: • Make sure agency clients send code packages to publishers (be in touch with them) • Make sure tags are generated at least a day prior to serving date

  38. Recipients list

  39. GOOD LUCK!

More Related