Closed Bug 1248571 Opened 8 years ago Closed 8 years ago

Add "Shared" to the room funnel data

Categories

(Hello (Loop) :: Client, defect, P2)

Product:
Hello (Loop)
Component:
Client
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: RT, Unassigned)

References

Details

(Whiteboard: [btpp-active][akita])

User Story

The room funnel data is currently missing an important indicator which is "Room shared". This bug is about adding this data to the current room funnel in order to have the full funnel view. This will also allow better understand relative use of the different share buttons.

"Room shared": indicated that a user pressed any of the 3 buttons showing an intention to share ("Copy", "Email", "Facebook").
Current room funnel data: https://metrics.services.mozilla.com/loop-server-dashboard/data/loop_room_funnel.json

Acceptance criteria:
- Log on the loop server "Room shared" events (value can be "Copy", "Email" or "Facebook")
- Add to the room funnel JSON the "Number of rooms shared" indicator
- Create a new JSON document reporting daily the relative share of rooms shared with the "Copy" action VS "Email" action VS "Facebook" action


The user value we are providing through this data collection is the ability for the Hello team to understand engagement with the product, and use that information to make the product more useful or engaging, or determine if the product doesn't have sufficient value to users.

The data we propose collecting: we want to measure if and how people share with the Hello room when created.  People can share the Hello room by hitting one of the 2 "Copy", "Email", or "Facebook" buttons
We'd like to be able to create reports with counts of the general categories (over 30 day periods):

1. Daily unique number of rooms created (data already available on the loop server) VS daily unique number of rooms shared (the data we want to collect) VS daily unique number of room URLs clicked  (data already available on the loop server)
2. Share of rooms shared with the "Copy" action VS "Email" action VS "Facebook" action
The room funnel data is currently missing an important indicator which is "Room shared". This bug is about adding this data to the current room funnel in order to have the full funnel view.

"Room shared": indicated that a user pressed any of the 3 buttons showing an intention to share ("Copy", "Email", "Facebook").
Current room funnel data: https://metrics.services.mozilla.com/loop-server-dashboard/data/loop_room_funnel.json

Acceptance criteria:
- Log on the loop server "Room shared" events (value can be "Copy", "Email" or "Facebook")
- Add to the room funnel JSON the "Number of rooms shared" indicator
User Story: (updated)
Blocks: 1248602
Rank: 19
Priority: -- → P1
Blocks: 1249646
No longer blocks: 1248602
Whiteboard: [btpp-active]
Assigning to Mark for bug break-down
Assignee: nobody → standard8
RT to ask Marshall about our ability to log this event
Flags: needinfo?(rtestard)
User Story: (updated)
Flags: needinfo?(rtestard)
Benjamin, we reviewed this with Marshall and this looks acceptable to him.
He although recommended we seek your approval regarding this in order to proceed (this is a request for approval to log "Room shared" events on the loop server directly) - all details are on the user story field.
Flags: needinfo?(benjamin)
In *general*, data-review=me 

In specific, I'd really like all this to be documented somewhere in the code. Typically I try to do my data reviews at the level of reviewing the changes to data documentation. Is there an existing set of docs checked in which describe the data we're collecting? If not how hard would it be to add that to a github repo and hook those docs up to readthedocs.org ?
Flags: needinfo?(benjamin)
Mark, do we have this documented somewhere in the code?
Flags: needinfo?(standard8)
We don't have documents for these at the moment.

We do have the Loop repo - so we could easily hook up documents there.

Benjamin:

Would markdown format be alright? Then they could just be displayed on github, or is there a specific reason for readthedocs.org?

Also, do you have examples of other areas of Firefox that have done this already? (looking so that we could set up a similar format).
Flags: needinfo?(standard8) → needinfo?(benjamin)
Decreasing the priority since we want to address this with behavioral metrics.
Rank: 19 → 25
Priority: P1 → P2
Sorry for the delay!

http://gecko.readthedocs.org/en/latest/browser/experiments/experiments/manifest.html is an example generated from http://mxr.mozilla.org/mozilla-central/source/browser/experiments/docs/manifest.rst

readthedocs.org is not necessary as long as the docs are checked into your repo and are readable from a published URL; it just happens to be a thing that much of the Mozilla project is using.

For other examples see http://socorro.readthedocs.org/en/latest/ which is from https://github.com/mozilla/socorro/tree/master/docs
Flags: needinfo?(benjamin)
No longer blocks: 1249646
Blocks: 1258340
Blocks: 1252404
Assignee: standard8 → nobody
Whiteboard: [btpp-active] → [btpp-active][akita]
Support for Hello/Loop has been discontinued.

https://support.mozilla.org/kb/hello-status

Hence closing the old bugs. Thank you for your support.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.