Richard Newman [:rnewman] Reporter
	Description • 11 years ago

Early days for scoping this.

	Richard Newman [:rnewman] Reporter
	Comment 1 • 11 years ago

See discussion in Bug 958561 -- this needs to track both old and FxA Sync, and needs to get out ASAP.

	Richard Newman [:rnewman] Reporter
	Comment 2 • 11 years ago

Tracking 30, but if this could make 29 it would be great.

	Nick Alexander :nalexander [he/him] (PTO until Montreallhands August 21, 2023)
	Comment 3 • 10 years ago

This is valuable for engineering, but FHR data is not currently being surfaced in an actionable manner to the mobile team, so tacking this on is not a priority.

	Mark Finkle (:mfinkle) (use needinfo?)
	Comment 4 • 10 years ago

What is this bug about? Comment 0 is not helping.

	Nick Alexander :nalexander [he/him] (PTO until Montreallhands August 21, 2023)
	Comment 5 • 10 years ago

(In reply to Mark Finkle (:mfinkle) from comment #4)
> What is this bug about? Comment 0 is not helping.

This ticket is the Android equivalent of Bug 958561, which adds FHR data about whether Sync is configured, what versions are in use and defaulted to, and how many syncs have succeeded/failed.

We haven't moved on this because it's technically tricky and requires co-ordination with metrics to actually define a data format that's useful for Android.

	Benjamin Smedberg
	Comment 6 • 10 years ago

This was part of the Firefox Q1 goal for desktop to measure whether sync usage is actually driving Firefox adoption and retention. I own the analysis bits of that for now. If this is not important for the mobile team, then we can postpone or drop it, but I thought it was considered a high priority.

	Deb Richardson [:dria] (plz NEEDINFO)
	Comment 7 • 10 years ago

If we have this data for desktop I very much think we should also have it for Mobile. We absolutely do want to measure whether sync usage is driving adoption & retention.

	Richard Newman [:rnewman] Reporter
	Comment 8 • 10 years ago

This is unlikely to happen for 30 or 31, so being realistic and bumping to 32. We can uplift if it magically gets done sooner.

Nick, please update assigned status.

	Mark Finkle (:mfinkle) (use needinfo?)
	Comment 9 • 10 years ago

Are we getting data form other sources on Sync usage? Otherwise, we need to do something or close this bug.

	Nick Alexander :nalexander [he/him] (PTO until Montreallhands August 21, 2023)
	Comment 10 • 10 years ago

(In reply to Mark Finkle (:mfinkle) from comment #9)
> Are we getting data form other sources on Sync usage? Otherwise, we need to
> do something or close this bug.

We've been getting along with FxA data from the FxA backend team and ditto with legacy Sync data.  That tells us about everything except self-hosted legacy Sync usage.

That's been enough to understand rough user counts, sync frequency for most clients, some metrics about collection sizes, number of devices per user, etc.

	Richard Newman [:rnewman] Reporter
	Comment 11 • 10 years ago

Absent Nick => bumping.

	Hamilton
	Comment 12 • 10 years ago

I've been asked to check back on whether FxA has been integrated into FHR. :rnewman and I had an email thread a few months ago about this, and at that point he mentioned that it may get into 35 or 36.

Is there any update on this?

	Nick Alexander :nalexander [he/him] (PTO until Montreallhands August 21, 2023)
	Comment 13 • 10 years ago

(In reply to Hamilton from comment #12)
> I've been asked to check back on whether FxA has been integrated into FHR.
> :rnewman and I had an email thread a few months ago about this, and at that
> point he mentioned that it may get into 35 or 36.
> 
> Is there any update on this?

No, sorry.

	Hamilton
	Comment 14 • 9 years ago

Hello again - I've gotten a few more questions from mobile stakeholders whether or not this has made it into FHR for fennec. Any updates at this point?

	Richard Newman [:rnewman] Reporter
	Comment 15 • 9 years ago

Hamilton: this isn't assigned to an engineer, nor is it tracking a particular release. As you know, FHR is mostly on ice, replaced by unified telemetry, but Fennec isn't really an active participant in that yet.

If this really needs to happen for a particular release, this needs to be retriaged and assigned, or an alternative approach chosen.

Presumably mobile stakeholders are already at the Fennec funnel meeting and/or triage; could you ask them to bring this up for prioritization, or ask them to contact me?

	Hamilton
	Comment 16 • 9 years ago

Totally understood - due diligence and all that. I'll have them contact you if it is absolutely important. This is an ask from the growth team, so I'm not sure which meetings they're at.

	:Grisha Kruglov
	Comment 17 • 7 years ago

Superseded by Bug 1308337 and friends.