Closed Bug 1125217 Opened 9 years ago Closed 6 years ago

Dashboard for Hello interactions

Categories

(Websites :: Web Analytics, task)

x86
macOS
task
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ckprice, Assigned: garethc)

References

Details

This bug is opened for the creation of a Hello analytics dashboard in an attempt to create a single view for multiple Hello interactions.
Gareth: can you meet with Cory next week and Cory will do a knowledge transfer of what metrics he's been providing to Arcadio and others around the page interactions and outstanding items. You can probably create a dashboard like you have done with other mozilla.org pages with a screenshot of metrics of key interactions. Also, this page has a few different states depending if you are Firefox or non-Firefox.

Cory: can you send out a meeting next week for you and Gareth?

Thanks everyone!
Assignee: nobody → garethcull.bugs
Flags: needinfo?(garethcull.bugs)
Flags: needinfo?(cprice)
Thanks Chris - invite sent.
Flags: needinfo?(garethcull.bugs)
Flags: needinfo?(cprice)
Thanks for setting up the meeting Cory.
Thanks for the meeting Gareth.

Here are the notes, and requirements: https://hello-onboarding.etherpad.mozilla.org/metrics-dashboard

UX for reference
Snippet - bug 1099320 comment 22
FTU - bug 1084090 comment 1
/whatsnew, /firstrun - bug 1084199 comment 5

Questions for Romain:

> # of users reaching the non supported platform page
> # of users reaching the non supported browser page 
What operating systems/versions and browser/versions qualify as "non-supported"?

> # of users trying to join conversations
> # of users joining conversations
Please clarify. Is this the difference between someone just landing on the link clicker page (in a state which is eligible to start a conversation), vs. clicking "Join conversation"?
Flags: needinfo?(rtestard)
(In reply to Cory Price [:ckprice] from comment #4)
> Thanks for the meeting Gareth.
> 
> Here are the notes, and requirements:
> https://hello-onboarding.etherpad.mozilla.org/metrics-dashboard
> 
> UX for reference
> Snippet - bug 1099320 comment 22
> FTU - bug 1084090 comment 1
> /whatsnew, /firstrun - bug 1084199 comment 5
> 
> Questions for Romain:
> 
> > # of users reaching the non supported platform page
> > # of users reaching the non supported browser page 
> What operating systems/versions and browser/versions qualify as
> "non-supported"?
> 
"Non supported platforms" are everything bug Windows, Mac, Linux and Android - i.e most non supported platforms are iOS, Windows phone and Blackberry. Such users are pointed to a page advising to change their device.

"Non supported browsers on supported platforms" are everything but Firefox, Chrome and Opera on a supported platform. i.e most non supported browsers on supported platforms are IE and Safari. Such users are advised to download Firefox or Firefox for Android depending on their device.

> > # of users trying to join conversations
> > # of users joining conversations
> Please clarify. Is this the difference between someone just landing on the
> link clicker page (in a state which is eligible to start a conversation),
> vs. clicking "Join conversation"?
1 A user trying to join a conversation is a user who clicks the "Join" button.
2 A user joining a conversation is a user who clicked the "Join" button and then joined the conversation room.

The difference between 1 and 2 can be that the user did not accept the dialogue prompting him to share his mic and cam or a technical issue preventing him to join.
Flags: needinfo?(rtestard)
Good meeting Cory. Thanks for walking me through the current GA set up and providing me with a user experience background. I'm going to file some bugs for interactions we are not currently tracking and will begin working on a v1 of a hello dashboard. I'll let you know if I have any questions as I begin to pull all of this data together. Thanks again!

Gareth
Depends on: 1130174
I think it is safe to close this bug.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.