1027176 - Add public Statistics dashboard

Status: VERIFIED FIXED

(Firefox Affiliates Graveyard :: affiliates.mozilla.org, defect, P1)

Description

[Osmose [:osmose, :mkelly]]

We have a lot of stats we want to show (bug 1004622) but nowhere to put them, so the best place to start would be a public stats dashboard! To start out, the dashboard should show basic site-wide metrics (number of users, banners, and clicks) as well as allow for drilling down to per-category and per-banner metrics.

I have a WIP version of such a dashboard done, and will attach screenshots for feedback and copy purposes.

Comment 1

[Osmose [:osmose, :mkelly]]

Attachment: Main Dashboard Screenshot

Comment 2

[Osmose [:osmose, :mkelly]]

Attachment: Category Page Screenshot

Comment 3

[Osmose [:osmose, :mkelly]]

Attachment: Banner Page Screenshot

Comment 4

[Osmose [:osmose, :mkelly]]

josorio: Beyond normal feedback, could you also provide the copy for this? (We don't necessarily need well-polished stuff from like matej's team, but I'm 95% certain you can do better than me :D)

mathjaz: When we add new pages like this going forward that aren't linked to some milestone or release, how do you want to be notified of new strings? Is just an email or something fine?

Comment 5

[ekariv]

Hey Mike and Matt - great talk today. 

Here's the list of copy and design changes we have for the screenshots highlighted above. Let me know if there's any confusion or additional blockers that we can help with. 

Copy / Design Changes for Statistics

(I'll also upload sketches that illustrate these edits)

Main Dashboard:

1) Nav Bar title “Statistics" changed to Impact
2) Headline Statistics changed to Impact
3) Subheader (View stats about the affiliates service and how it is performing) changed to “View the results our affiliates are driving”.

“Service Wide Metrics” changed to "Key Metrics"

Clicks/Banners/Affiliates changed to AFfiliates/Banners/Clicks (reverse order)

Category Page:

Same as main dashboard: Nav Bar title “Statistics" changed to Impact
Headline Statistics changed to Impact
Subheader (View stats about the affiliates service and how it is performing) changed to “View the results our affiliates are driving”.

Remove ‘parent category firefox’ and make clicks/banners each 1/2 of the page

Move banners into ‘list’ format where it shows the image, name to the right, and then # of clicks, and # of buttons'

Banner Page:

No longer needed (important info moved to bottom of category page)

Comment 6

[ekariv]

Attachment: Category Page Sketch

Comment 7

[ekariv]

Attachment: Main Dashboard Sketch

Comment 8

[Osmose [:osmose, :mkelly]]

(In reply to ekariv from comment #5)
I'll go ahead and make all these changes, but I have a few suggestions (and one question):

> 1) Nav Bar title “Statistics" changed to Impact

I suggest we use a more obvious word than Impact. IMO it's not obvious to a normal person that the word "Impact" means "a page with stats on how the service is doing". It wasn't obvious to me and I work on engagement sites. :P

> 3) Subheader (View stats about the affiliates service and how it is
> performing) changed to “View the results our affiliates are driving”.

Some of the stats being shown aren't driven by users, and I dunno if I'd call link clicks a result (the real goal isn't more clicks, the real goal is awareness of what Mozilla is doing and usage of our other products).

> Move banners into ‘list’ format where it shows the image, name to the right,
> and then # of clicks, and # of buttons'

This requires your input before I implement: The image we use to preview banners is 150x150 pixels, which is too large to be able to make a (readable) table as you suggest. While we could shrink down the imag to fite, I would suggest instead we keep the grid view as it is and instead of just showing the banner title, also show the number of clicks and number of buttons as well. That also significantly reduces the work since we then don't have to make the table display properly on mobile devices since that work has already been done for the grid of banners. Thoughts?

Comment 9

[Jessica Osorio [:josorio]]

(In reply to Michael Kelly [:mkelly,:Osmose] from comment #8)
> (In reply to ekariv from comment #5)
> I'll go ahead and make all these changes, but I have a few suggestions (and
> one question):

Please see responses below:

> > 1) Nav Bar title “Statistics" changed to Impact
> 
> I suggest we use a more obvious word than Impact. IMO it's not obvious to a
> normal person that the word "Impact" means "a page with stats on how the
> service is doing". It wasn't obvious to me and I work on engagement sites. :P

OK, I understand where you're coming from - thanks for playing devils advocate! :) 
How do you feel about these other options:
- Performance
- Results
- Statistics (this is my last option, but if you totally disagree with the others I'm open to sticking with it) :) 


> > 3) Subheader (View stats about the affiliates service and how it is
> > performing) changed to “View the results our affiliates are driving”.
> 
> Some of the stats being shown aren't driven by users, and I dunno if I'd
> call link clicks a result (the real goal isn't more clicks, the real goal is
> awareness of what Mozilla is doing and usage of our other products).

New Option: 
Take a look at the impact our Affiliates make on increasing awareness of Mozilla and it products. 
(Please keep in mind that copy is not my forte but I'm just trying to finesse it a little - please feel free to hack at this latest option and maybe help me to get it at a better place, if needed)


> > Move banners into ‘list’ format where it shows the image, name to the right,
> > and then # of clicks, and # of buttons'
> 
> This requires your input before I implement: The image we use to preview
> banners is 150x150 pixels, which is too large to be able to make a
> (readable) table as you suggest. While we could shrink down the imag to
> fite, I would suggest instead we keep the grid view as it is and instead of
> just showing the banner title, also show the number of clicks and number of
> buttons as well. That also significantly reduces the work since we then
> don't have to make the table display properly on mobile devices since that
> work has already been done for the grid of banners. Thoughts?

This sounds great! Love it! :) 


Thank you very much Mike Kelly!

Comment 10

[Osmose [:osmose, :mkelly]]

> How do you feel about these other options:
> - Performance
> - Results
> - Statistics (this is my last option, but if you totally disagree with the
> others I'm open to sticking with it) :) 

Performance is a good balance, I like it. :D

> New Option: 
> Take a look at the impact our Affiliates make on increasing awareness of
> Mozilla and it products. 
> (Please keep in mind that copy is not my forte but I'm just trying to
> finesse it a little - please feel free to hack at this latest option and
> maybe help me to get it at a better place, if needed)

Actually that sounds great, I like how it subtly empowers users.

I've made the rest of the changes and will be working on writing tests to get a PR in. I'll let you know when it's on dev to test.

We'll probably have to do some performance tweaks afterwards to get it suitable for public consumption, so I'd guess this would go out sometime the week after the offsite.

Comment 11

[Matjaz Horvat [:mathjazz]]

(In reply to Michael Kelly [:mkelly,:Osmose] from comment #4)
> mathjaz: When we add new pages like this going forward that aren't linked to
> some milestone or release, how do you want to be notified of new strings? Is
> just an email or something fine?

Michael,

An email is fine. If possible, please do that before you actaully merge new strings into SVN.

Comment 12

[ekariv]

Are we still moving forward with this bug?

Comment 13

[Osmose [:osmose, :mkelly]]

Yeah, the code's still awaiting code review. I am attempting to make that happen faster.

Comment 14

[[github robot]]

Commit pushed to master at https://github.com/mozilla/affiliates

https://github.com/mozilla/affiliates/commit/2feffa418fd9041fa26ade26d6b1476a0df93a6b
Fix bug 1027176: Add public statistics section to site.

Comment 15

[Osmose [:osmose, :mkelly]]

Will update this bug once the dashboard lands on dev and is ready to test.

Comment 16

[Osmose [:osmose, :mkelly]]

This is up on the dev server, and I've run the denormilization command so the click counts should be up-to-date.

Comment 17

[Osmose [:osmose, :mkelly]]

To clarify, by "click counts should be up-to-date", I mean they match the expected click counts for the dev server, not that the data on the dev server matches the counts for prod data.

Comment 18

[Osmose [:osmose, :mkelly]]

Jessica and Eli: Can you both check this out at https://affiliates-dev.allizom.org/en-US/statistics/ and check to make sure it looks and feels the way you expect it to? That's the dev server, so the numbers are just test data, so any feedback on things you think need to change before we push this to prod would be appreciated.

If it looks good, please mark this bug as VERIFIED FIXED in the status field. Thanks!

Comment 19

[ekariv]

Hey - this is awesome, but two quick fixes:

1) Copy change: “Take a look at the impact our Affiliates make on increasing awareness of Mozilla and it products.” - changed to “its” products
2) On the categories page (i.e. https://affiliates-dev.allizom.org/en-US/statistics/category/5/) does it make sense to squeeze in the “Banners” and “Clicks” closer towards the middle line? (The ones that are under “Category Metrics”).

Comment 20

[[github robot]]

Commit pushed to master at https://github.com/mozilla/affiliates

https://github.com/mozilla/affiliates/commit/3da0f759fe04764e470fa4c3d84a1a64356fccac
Bug 1027176: Fix spelling error and centering of stats on public stats.

Comment 21

[Osmose [:osmose, :mkelly]]

affiliates-dev has been updated to move the stats closer to the middle line and to fix the grammar error.

Comment 22

[ekariv]

Awesome, looks great!

Comment 23

[Osmose [:osmose, :mkelly]]

Marking as verified. We're blocked from deployment by an issues with Google Analytics that garethc is investigating, but once that is resolved we'll be ready to get this on production.