Closed Bug 1166490 Opened 11 years ago Closed 10 years ago

Pull website launch data from GA into Monolith for popularity and trending sorting

Categories

(Marketplace Graveyard :: General, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: ddurst, Unassigned)

References

Details

(Whiteboard: [marketplace-transition])

In order to inform website popularity in MP, we need to pull data from GA into Monolith -- this should be identical (in process) to apps, even though the data is about "launch" rather than "install." Trending was worked on previously, but was not launched.
The difference between apps and websites is that apps you install once and then it is on your device and you launch it multiple times. But, from what I can tell from the UI mocks, websites you launch from Marketplace and would be launched multiple times. I'm not sure the resulting numbers would be equivalent.
I wonder if we only care about the initial launch, then?
Flags: needinfo?(ehunt)
Created this doc for conversation with Product, Design, and Engineering: https://docs.google.com/document/d/18iZ3m8YIs22f8f8pAAcfmEMcDROAEznB4HKTzZ1_Lwc
Flags: needinfo?(ehunt)
Flags: needinfo?(dbialer)
To summarize the Google doc for historical purposes, UX propose to record each launch for popularity/trending calculations. The other options being record one launch per user per <time interval>, and record one launch per user period. Not limiting launch tracking is the easiest as far as backend code is concerned so I'll go with that and we can tweak later if need be.
Assignee: nobody → robhudson.mozbugs
Status: NEW → ASSIGNED
Blocks: 1162135
No longer blocks: 1158165
Depends on: 1179463
Assignee: robhudson.mozbugs → nobody
Status: ASSIGNED → NEW
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Whiteboard: [marketplace-transition]
Flags: needinfo?(dbialer)
You need to log in before you can comment on or make changes to this bug.