Closed
Bug 1003932
Opened 10 years ago
Closed 10 years ago
MVP referrer dashboard front-end
Categories
(Webmaker Graveyard :: Metrics, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: adam, Assigned: adam)
References
Details
(Whiteboard: [metrics][dec12])
Build a dashboard to make use of the referrer tracking stats. Use over time, with filter options by code, plus a leaderboard.
Assignee | ||
Updated•10 years ago
|
Priority: -- → P2
Assignee | ||
Comment 1•10 years ago
|
||
Ship this before Maker Party, but in the meantime the tracking is in place and we can see the results in "jbucks whimsical dashboard" http://jbuck.github.io/rid-high-scores/
Whiteboard: [July11]
Assignee | ||
Comment 2•10 years ago
|
||
This could be good: http://dc-js.github.io/dc.js/
Assignee | ||
Updated•10 years ago
|
Status: NEW → ASSIGNED
Comment 3•10 years ago
|
||
* Adam: is this still in scope for [July11]? * I suggest this could move to [July25]
Whiteboard: [July11] → [metrics] [July11]
Updated•10 years ago
|
Whiteboard: [metrics] [July11] → [metrics] [July25]
Comment 4•10 years ago
|
||
* Adam: I question the need for actually building this out futher. Do you have a customer? Does Engagement Team want it? Not convinced this will actually motivate partners, or that this is an effective use of our limited time. * If there's a real customer, then happy to be wrong. :) I just know you and jbuck are slammed already, and this seems like something we could drop
Flags: needinfo?(adam)
Whiteboard: [metrics] [July25] → [metrics]
Assignee | ||
Comment 5•10 years ago
|
||
(In reply to Matt Thompson (@OpenMatt :OpenMatt) from comment #4) > * Adam: I question the need for actually building this out futher. Do you > have a customer? Does Engagement Team want it? Not convinced this will > actually motivate partners, or that this is an effective use of our limited > time. > > * If there's a real customer, then happy to be wrong. :) I just know you and > jbuck are slammed already, and this seems like something we could drop Yes, working with partners to scope this in Bug 1021042. There's real interest in this, and it's one of my priorities for Q3.
Flags: needinfo?(adam)
Whiteboard: [metrics] → [metrics][July25]
Updated•10 years ago
|
Whiteboard: [metrics][July25] → [metrics][aug8]
Assignee | ||
Updated•10 years ago
|
Whiteboard: [metrics][aug22] → [metrics][Sep5]
Assignee | ||
Updated•10 years ago
|
Whiteboard: [metrics][Sep5] → [metrics][Sep19]
Comment 7•10 years ago
|
||
* Adam: please assign to [oct3] or [oct17] train
Flags: needinfo?(adam)
Whiteboard: [metrics][Sep19] → [metrics][oct3]
Assignee | ||
Comment 8•10 years ago
|
||
Thanks. I'm pushing this one back a bit.
Flags: needinfo?(adam)
Whiteboard: [metrics][oct3] → [metrics][oct17]
Comment 9•10 years ago
|
||
* the [oct17] train has now left the station * so please update with [oct31], [nov14], [nov28], etc.
Comment 10•10 years ago
|
||
* [oct17] has passed. Please update the whiteboard.
Assignee | ||
Comment 11•10 years ago
|
||
MVP is taking shape here: http://webmaker-metrics.herokuapp.com/
Whiteboard: [metrics][oct17] → [metrics][Oct31]
Comment 12•10 years ago
|
||
* [oct31] is now past. Please update whiteboard to [nov14] or future train.
Assignee | ||
Updated•10 years ago
|
Whiteboard: [metrics][Oct31] → [metrics][Nov14]
Comment 13•10 years ago
|
||
* [nov14] is past -- please update to [nov28] train or later
Comment 14•10 years ago
|
||
* Do we still need this?
Flags: needinfo?(adam)
Whiteboard: [metrics][Nov14] → [metrics][dec14]
Updated•10 years ago
|
Whiteboard: [metrics][dec14] → [metrics][dec12]
Assignee | ||
Comment 15•10 years ago
|
||
This will be used to evaluate the "ROI" on various marketing campaigns planned for 2015. It will mostly be a tool for the engagement team. The MVP demo is available here: https://webmaker-metrics.herokuapp.com/ There's further work to do socializing this, and making it more user friendly, but I'm closing the MVP ticket at this stage :)
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(adam)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•