The Chronicle of Higher Education New Commerce Platform Fulfillment Tracker and Customer Dashboard Betsy Barefoot, The Chronicle of Higher Education
History of New Commerce Platform (NCP) The original scope of NCP was one project encompassing the entire Adbase ecosystem – move backend from 2.26 to current software, move entire Self Service Portal to modern architecture -- utilizing Web services, add credit card tokenization, replace AdWatch with MediaLink, move Internet ads from Preprint tab to Internet tab, add Doubleclick integration, add BI database. For a variety of reasons, the project was broken into smaller pieces NCP 1.0 – launched May 2014 NCP 1.5 – launched August 2015 NCP 2.0 – launch TBD, in planning & configuration NCP 2.5 – launch TBD
NCP 1.0 – overhaul Self Service Portal Objectives Improve the site to make it easier to do business Broaden products & offerings Introduce Provide job ad performance metrics to customers Create easier way to manage Web Packages internally and externally Stabilize Self Service while remaining on 2.26 Deliverables New branding, look and feel for CHE and COP portals Web Only Workflow to FuelPHP and add CC Processing via PayPal APIs Fulfillment Tracker for Web Packages Customer Dashboard Job Performance Metrics Manage Web Packages Manage Ads – full functionality in 1.5
Fulfillment Tracker (internal tool to manage Web Packages) Previously we used Contract Manager to manage Web Packages (prepaid bundles of job postings), but Contract Manager is not the ideal tool – It is designed to count up to a new level not down to 0. It is not designed to automatically end a contract that has been fulfilled or gone past its end date. Someone had to monitor those Contracts constantly in order to close them properly and not allow a customer to place additional ads for free. End date on Contract Manager is date not date/time, so even with someone monitoring the Contracts, we had to use a combination of back dating and no fulfill and external fulfill in order to end one package and start a new one for customers.
Fulfillment Tracker (con’t) Web-based tool with access controlled by Active Directory and Adbase user settings Utilizes the XML Importer Starting point for setting up Web Package Internal user creates Web Package in FT FT sends the order to Adbase (via XML Importer), for billing purposes Any ad placer allowed to utilize a Web Package must be added as a user in FT Ad Placers can be users on multiple Web Packages at one time Ad Placer specifically selects Web Package during the Self Service workflow OR when sending an ad through our API
Fulfillment Tracker (con’t) If no enhancements are added to the job posting, the payment page is bypassed and the order comes into Adbase at a cost of $0 If enhancements are added, the payment page is not bypassed, and the customer pays for the enhancements via purchase order or credit card When a Customer uses the last ad available in a package, the packages is automatically set to a status of Fulfilled, and additional ads CANNOT be placed against it When a package passes its end date, even if there are remaining ads, the package is automatically set to a status of Expired, and additional ads cannot be placed against it
Customer Dashboard Order History “on steroids” Shows 3 Most Recent Ads with button to view all ads from past 6 months Shows Metrics from Omniture Shows 3 Most Recent Web Packages with button to view all Packages From Package, can view all ads on that package, regardless of “who” placed the ad Place new ad on package directly from Dashboard Allows customer to Edit, Cancel, or Rebook a Web Only ad View by Client for Agency Reps