Open
Bug 1357433
Opened 8 years ago
Updated 2 years ago
Expose "Active Hours" (based on Active Ticks) information in UITour.getConfiguration for snippets on about:home
Categories
(Firefox :: Tours, enhancement, P3)
Tracking
()
NEW
People
(Reporter: pdol, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
User Story
As a Firefox Retention team member, I would like to be able to display snippets to users based on their total Active Hours (derived from Active Ticks) in the previous 28 days in order to provide useful information to users based on how heavily they use Firefox. activeHours = activeTicks * (activeSeconds/ActiveTick) * (activeHours/activeSeconds) = activeTicks * activeSecondsPerActiveTick / activeSecondsPerActiveHour with: activeSecondsPerActiveTick = 5.0 activeSecondsPerActiveHour = 60*60 = 3600 Acceptance Criteria: - Snippets are only displayed to users based on the total of Active Hours (in the last 28 days) targeting used -- Examples: ---1. Display snippet to users whose total Active Hours (based on Active Ticks) exceeded 28 hours in the previous 28 days ---2. Display snippet to users whose total Active Hours (based on Active Ticks) was less than 2 hours in the previous 28 days ---3. Display snippet to users whose total Active Hours (based on Active Ticks) was greater than 10 hours but less than 20 hours in the previous 28 days --------- Old story: As a UITour consumer I will have access to the following properties on the result of Mozilla.UITour.getConfiguration("appinfo", …): * Weeks (if < 3 months) since active session hours exceed x hours (in other words: yes or no a user has exceeded x hours of active session hours in the last week)
No description provided.
Reporter | ||
Comment 1•8 years ago
|
||
For reference, analysis of Active Ticks using definition of heavy user: https://gist.github.com/bcolloran/b708b28fe8eb873727c25751dbcb0451
Reporter | ||
Updated•8 years ago
|
Reporter | ||
Updated•8 years ago
|
Reporter | ||
Updated•8 years ago
|
Blocks: photon-onboarding
Priority: -- → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•