Project goal
Helps analyse competitor's traffic and metrics on a site.
NDA
Any metrics related to users or money under NDA. They can't and won't be used in this case descriptions.
Traffic Analytics
Comparison
Goal: improv work with competitors comparison
What was done
- 1ResearchAnalysed how often users work with comparison mode. Was designed experiment how can we improve work.
- 2WireframesCreated prototypes. Worked with a UX writer.
- 3DevelopmentChecked UI design, how it works in real life. Found bugs on a stage.
- 4Check resultAnalysed by GA how users changed interactions with the new interface. Checked metrics.
User returns at least one time in a month and regular checked same sites as previous month. We needed to create simple solution without big development. That why we decide to to do such thing using only users cookies.
Old comparison form. To go to the comparison form, there was only one button and when you push it then opened form from previous picture. This case is about what is simple not equal effective. We changed it.
New comparison form. Form was designed for faster activation user with showing as much features as we can. This simple changes (adding input, button that compare 2 sites immediately) resulted in an increase of over 900% in comparison mode transitions.
Traffic Analytics
Audience Overlap
Goal: help to understand how audience overlap with competitors
What was done
- 1WireframesCreated prototype and tested them on users. Worked with a UX writer.
- 2DevelopmentChecked UI design, how it works in real life. Found bugs on a stage.
- 3Check resultAnalysed by GA how users changed interactions with the new interface. Checked metrics.
First version of Audience overlap graphics. We choose venn diagram to show overlap. Using this type of diagram we find a problem with showing overlap more than 3 items — they become unreadable. Splitting on 5 separated diagrams helped with this issue.
Second version of Audience Overlap. We founded that user was frustrated about different size of "the main bubble", thinking that this is different size auditories. Solution for "the main bubble" was always showing the same size on each diagram in a raw.
Traffic Analytics
Payment
Goal: increase self-payments
What was done
- 1Information ArchitectAnalysed which data we can use and how we can show it graphics.
- 2WireframesCreated prototypes with different visualisation.
- 3Text improvementWorked in collaboration with UX writer.
- 4DevelopmentChecked UI design, how it works in real life. Found bugs on a stage.
Old version of a payment dialog.
New payment dialog with call to action and description of paid opportunities.
Traffic Analytics
API
Goal: explain user how to work with API
What was done
- 1Research & Information ArchitectAnalysed how developers worked with API. Analysed what data is available and in what format.
- 2WireframesCreated prototype and deferent type of instructions for developers and managers.
- 3DevelopmentChecked UI design, how it works in real life. Found bugs on a stage.
Who it's about
API has two users persona. Managers who need data and they want understand witch kind of data API provides. Second are developers that needed to know how work with API and provided data.
This is how we shows our data in result.
This is how we shows API request. Every user can use request instead asking developer to write it.
Documentation for API for advanced using it.
Traffic Analytics
Bonus track
A little cool things that I did with the UI designer
States for subscription on Push or slack notifications.
Browser Push notification design.
Data collecting only once a month. Many users asked where the new data? We decide to show them an actual information from knowledge base in an actual place.
This is flow for Slack bot. We found out that most of users use slack and decided integrate new communication path.
