Engagement and monetization
Provide publishers with a metric-based experience, with revenue split by media and ad type. Restructure the information architecture, navigation menu, and layout.
As a UX designer, I was responsible for working with the existing publisher portal to redefine IA, create new experiences, UI components, and new interactions.
Publishers will get vital revenue metrics based on ad types to develop a content strategy based on which content generates the most revenue.
When I joined this project, users struggled to get crucial metrics to gain insight into which content generates the most revenue. All aggregate data was split into numerous categories rendered as data cards sometimes without being connected to each other within the same entity. Deeper insights were available only when users navigate each data card “View details” page losing context while leaving the main portal page. When users navigated to the “View details” page for each data card, they lost context while leaving the main portal page. Navigation was placed at the top of each page and was limited in horizontal space, preventing adding new menu items as needed.
Publisher Portal 2.0 is a complete redesign of the current portal with a new navigation architecture and new revenue reports. Allow access to the new portal and the features being rolled out while still letting customers see and access their current production data and reports.
Before jumping into the redesign of a new information architecture and navigation system, I found more reason to relocate the navigation bar from the top to the left. The trend behind drawer nav menus became apparent after running a short competitor analysis.
A number of whiteboarding sessions, wireframes, UI designs, testing sessions, feedback, and iterations enabled me to validate ideas with internal and external teams. This resulted in the menu moving to the left and becoming vertical, which allowed new items to be added without restriction. I also made the menu bar collapse to a smaller size, leaving only icons visible. This feature added some room for content on the right side of the screen.
At the top of the page for each of the revenue reports (Revenue, Unit Load RPM, and Unit Loads) I show 3 small cards that take the width of the page that will show context across each of the revenue drivers so the user has context. Chart data is rolled up Daily, Weekly, Monthly, and Quarterly.
At the top of the page for each of the revenue reports (Revenue, Unit Load RPM, and Unit Loads) I show 3 small cards that take the width of the page that will show context across each of the revenue drivers so user has context.
By providing more real-time insights into most essential metrics, we encourage users to return regularly to check for updates. The unit Load RPM tab will have the same reports as Revenue but will substitute Unit Load RPM for revenue and contain RPM at the top of the graph as it won’t break it down by Video or Display. Display the small cards at the top of the page as described above. The Unit Load tab will have the same reports as Revenue, but it will show only the overall unit loads at the top of the graph since we won’t break it down by Video or Display. I used stacked bar charts for data that is additive and can be totaled. Some multi-line charts are used when aggregate data are measured in different units on parallel axes.
I redesigned the date picker UI to include new time range presets. Users need to be able to select from some default shortcut calendar timeframe and pick custom date ranges:
I also added an option to select comparison period:
In order to deliver this project, I developed the following:
This has resulted in a look and feel that is not only professional but also colorful and playful; a component library that can be leveraged when building out new pages; and usability improvements that make hierarchy and tasks more clear and easier to perform.