Closed Bug 1473017 Opened 2 years ago Closed 2 years ago
Change datasets to reflect "stub" desktop attribution from OSX installations
In bug 1468680, we're looking to use stub attribution to understand when a user has installed Firefox from a specific property. The change for Windows is fairly straightforward, and merely uses the existing parameters, having no net effect on either the telemetry activation ping or stub attribution overall. Mixedpuppy has a patch in review for bug 1344771 to allow us to do the same for OSX clients -- it's a different methodology, but the net result is that OSX clients would have the same kind data for the telemetry activation ping that currently exists on Windows. Which means that when this lands, we will begin collecting "stub attribution" data from OSX clients. So, Marketing and Product metrics will want to know this is coming and we should adjust our datasets/reporting to accommodate it. (CCing the world so they know about this, because this is probably the most impactful part of this change right now.)  AMO, in this case, though in the future others could use this same technique.  This approach has been vetted with pmac and agibson via https://docs.google.com/document/d/1w2YnGSemYViJ2Cn5_i67BHSpNoRy1TwUMOW62GS0Fik/edit.
As long as the attribution information is recorded the same way in Telemetry (in the "environment.settings" field), it will flow through to the datasets that currently include attribution information - like main_summary, churn and clients_daily - without any further change. Is there a specific dataset or report that needs to be updated?
Not sure -- I didn't know who or what uses this or what format it takes (or who would need to say so).
The patch for osx doesn't make any changes to the data for this, it simply makes the data available from osx. I think that this bug is about whether the backend reporting will account for data from osx.
A sign-off on this bug is blocking landing bug 1344771. The change here is that telemetry for attribution will change from windows-only to windows and osx.
I'm good with landing this - I haven't identified any blockers in terms of reporting, and we'll have enough information in the data to differentiate osx data, so we can adjust reports and datasets if any problems arise. Thanks for the heads up!
I think this bug has done it's job to bring attention to this change. If there's anything specific that falls out from this, let's file new bugs.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Can you please add some STRs to this bug or mark it as "qe-verify-" ?
hrm, there are no qe flags on this bug when I edit. In any case, qe-verify-
You need to log in before you can comment on or make changes to this bug.