Closed
Bug 1318550
Opened 8 years ago
Closed 7 years ago
[AS] [Telemetry] Track sync status of highlight and top site items
Categories
(Firefox for Android Graveyard :: General, defect, P2)
Firefox for Android Graveyard
General
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: Grisha, Assigned: Grisha)
References
Details
(Whiteboard: [MobileAS])
Attachments
(1 file)
We'd like to know what percentage of interactions with "highlights" are happenings with items that were already synced. If user doesn't have Sync enabled, none of the items in highlights would have been synced - unless user had sync enabled and then disabled it. If user has Sync enabled, and they're syncing history/bookmarks, items in highlights will have been synced, unless they haven't been synced yet (new visits, or sync didn't run in a while for some reason). Either way, it seems that to make sense of "synced/not synced" data point, we also need an additional "sync is enabled for history" or "sync is enabled for bookmarks" flags.
Assignee | ||
Updated•8 years ago
|
Priority: -- → P2
Summary: [Highlights] [AS] When tracking clicks on highlight items, include whether or not item has been synced → [AS] [Highlights] When tracking clicks on highlight items, include whether or not item has been synced
Assignee | ||
Updated•8 years ago
|
Summary: [AS] [Highlights] When tracking clicks on highlight items, include whether or not item has been synced → [AS] [Telemetry] Track sync status of highlight and top site items
Updated•7 years ago
|
Iteration: --- → 1.13
Priority: P2 → P1
Updated•7 years ago
|
Iteration: 1.13 → 1.14
Assignee | ||
Comment 1•7 years ago
|
||
After actually considering our schema, I'm not sure this is feasible as described without changes to sync. At best, we can say that a history item in highlights has only been visited locally, or it has only been visited remotely, or it's been visited both locally and remotely. For top sites, we currently excluded "only visited remotely" items, so it'll be just "visited only locally, or visited both locally and remotely". Interacting with items that haven't been visited locally up to this point could be pretty interesting when considering highlights. We'll be able to see if people are interacting with pages they've visited on a desktop and that algorithm surfaced up, and perhaps compare that with those that were also visited locally. Engineering-wise, it should not be difficult to implement as described: - add additional telemetry flag for highlight interactions to indicate if highlight is 1) local, 2) remote, 3) mixed.
Comment hidden (mozreview-request) |
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → gkruglov
Status: NEW → ASSIGNED
Comment 3•7 years ago
|
||
mozreview-review |
Comment on attachment 8832257 [details] Bug 1318550 - Track "visits state" for all highlight interactions https://reviewboard.mozilla.org/r/108600/#review110242 LGTM. We just need to adapt it to the changes in bug 1312016. :) ::: mobile/android/base/java/org/mozilla/gecko/db/BrowserProvider.java:1196 (Diff revision 1) > + "CASE " + > + "WHEN " + DBUtils.qualifyColumn(History.TABLE_NAME, History.VISITS) + " IS NULL THEN " + Highlights.VISITS_NONE + " " + > + "WHEN " + DBUtils.qualifyColumn(History.TABLE_NAME, History.REMOTE_VISITS) + " = 0 THEN " + Highlights.VISITS_LOCAL_ONLY + " " + > + "WHEN " + DBUtils.qualifyColumn(History.TABLE_NAME, History.LOCAL_VISITS) + " = 0 THEN " + Highlights.VISITS_REMOTE_ONLY + " " + > + "ELSE " + Highlights.VISITS_MIXED + " END " + > + "AS " + Highlights.VISITS_STATE + ", " + This query doesn't exist anymore once bug 1312016 lands. We need to move this to the new query for picking highlights candidates.
Attachment #8832257 -
Flags: review?(s.kaspari) → review+
Updated•7 years ago
|
Iteration: 1.14 → 1.15
Updated•7 years ago
|
Iteration: 1.15 → 1.16
Assignee | ||
Comment 4•7 years ago
|
||
Now that Bug 1312016 landed, this can be re-addressed.
Updated•7 years ago
|
Iteration: 1.16 → 1.17
Updated•7 years ago
|
Iteration: 1.17 → 1.18
Updated•7 years ago
|
Iteration: 1.18 → 1.19
Updated•7 years ago
|
Iteration: 1.19 → 1.20
Updated•7 years ago
|
Iteration: 1.20 → ---
Priority: P1 → P2
Updated•7 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Updated•3 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•