1251058 - Add telemetry for screenshot items in Bookmarks panel view

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: Metrics, defect)

Description

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

We should add some probes here to track this prototype.

Barbara, thoughts on what to track?

Comment 1

[Barbara Bermes [:barbara] - NI please!]

Probe to track a screenshot bookmark as different type of bookmark, so we can say at the end e.g.
x% of bookmarks are URLs
y% are RV items
z% are screenshots

Once we categorize RV, screenshot, PDF bookmarks etc., we can even create a ratio of each type saved vs. loaded e.g. for every screenshot saved, only x% were being opened etc. This will help us figure out which types are most successful and should be further promoted and enhanced.

By categorizing the bookmarks in types, we can see which ones are most used, loaded, saved, deleted etc.

Makes sense?
Makes sense?

Comment 2

[Anthony Lam (:antlam) Find me, @antlam on Slack!]

Also track how many times these items are pressed/ loaded from Bookmarks?

Comment 3

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to Barbara Bermes [:barbara] from comment #1)
> Probe to track a screenshot bookmark as different type of bookmark, so we
> can say at the end e.g.
> x% of bookmarks are URLs
> y% are RV items
> z% are screenshots
> 
> Once we categorize RV, screenshot, PDF bookmarks etc., we can even create a
> ratio of each type saved vs. loaded e.g. for every screenshot saved, only x%
> were being opened etc. This will help us figure out which types are most
> successful and should be further promoted and enhanced.
> 
> By categorizing the bookmarks in types, we can see which ones are most used,
> loaded, saved, deleted etc.

I'll counterpoint. Why do screenshots need to be bookmarks to be successful? I think we should not care about how many screenshots are RV or bookmarks. We are not tracking screenshots in order to make more bookmarks. We are tracking screenshots to use as a signal that the URL was important in some way.

(In reply to Anthony Lam (:antlam) from comment #2)
> Also track how many times these items are pressed/ loaded from Bookmarks?

Yes, we should track when the screenshot URL is reopened _and_ when the sceenshot image is opened. There are two different events.

Also, not a bookmark.

Comment 4

[Barbara Bermes [:barbara] - NI please!]

I believe screenshots, RV and bookmarks are stored differently behind the scenes, in the DB -- I'm not talking about that.

> I think we should not care about how many screenshots are RV or bookmarks.
I'm not super keen on knowing if a screenshot of a page was saved in RV.

We will save screenshots in the bookmarks panel, no? Why would we not keep track of the different types in the bookmark panel?

> We are not tracking screenshots in order to make more bookmarks. 
Please elaborate.

All I want is to understand what types of content (RV, URL, screenshot, PDF etc.) are saved in the bookmark panel and if/how often their types are being saved/loaded/deleted. This will tell us what types are being used more often to revisit content.

Comment 5

[Mark Finkle (:mfinkle) (use needinfo?)]

(In reply to Barbara Bermes [:barbara] from comment #4)
 
> > We are not tracking screenshots in order to make more bookmarks. 
> Please elaborate.
> 
> All I want is to understand what types of content (RV, URL, screenshot, PDF
> etc.) are saved in the bookmark panel and if/how often their types are being
> saved/loaded/deleted. This will tell us what types are being used more often
> to revisit content.

If you want to understand what types of content are saved in the bookmark panel, just track what types of content are saved. We already do that. If you want to track what types of content are being loaded from the bookmark panel, we already do that.

In either case, making sure we have event data probes in place (we do) is enough to answer "are these things being used" because we can roll up the event data per day, week, month.

Comment 6

[BMO Automation]

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.