Closed Bug 1064948 Opened 7 years ago Closed 7 years ago

Use campaign ID to track 'Firefox Privacy Coach' usage


(Firefox for Android Graveyard :: General, defect)

35 Branch
Not set



Tracking Status
fennec + ---


(Reporter: krudnitski, Unassigned)



Because we're turning all tracking off, the thought here is that we could use the campaign ID system to track the installs of this add-on? (related to turning FHR off by default)
tracking-fennec: ? → 33+
tracking-fennec: 33+ → +
If I'm understanding this bug correctly, you're saying that we should have some code in the add-on to set a distribution campaign?

I believe the campaign tracking we use for distributions is reported through FHR, so I don't know that we would be able to report things from the product if FHR is disabled.

Also, I feel like an add-on shouldn't go mucking around in the distribution logic, since that may break actual Fennec install campaign data.

AMO lets us know how many people installed the add-on and how many active users there are, so could we just use that data to solve this problem?
Flags: needinfo?(krudnitski)
AMO could tell us how many times the add-on was downloaded, but I don't think it tells us how many times it has been installed. How would we know if people are still using it? ie what if it got downloaded 100,000 times but then 90% of those folks uninstalled it?  I'd want to know that, I suspect.

Can blocklist ping be used to add an ID when the add-on is installed?
Flags: needinfo?(krudnitski)
(In reply to Karen Rudnitski [:kar] from comment #2)
> How would we know if
> people are still using it?

AMO gives us weekly downloads, total installs, active daily users (via update pings), and full graphing, broken down by version/locale/etc.
Summary: Use campaign ID to track 'Firefox Confidential' usage → Use campaign ID to track 'Firefox Privacy Coach' usage
We can get detailed stats on usage from AMO.
Closed: 7 years ago
Resolution: --- → WONTFIX
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.