Bugzilla

Thanks for the detailed response mark, this should be good documentation for this going forward. A few responses inline:

(In reply to Mark Hammond [:markh] from comment #12)
> (In reply to Leif Oines [:loines] from comment #10)
> If IIUC, it should be "impossible" for these to be null, they should always be true or false. null probably means 71 or 72 builds before the new probes landed. Now 71 is in release, I believe it should be impossible for 71 builds on the release channel to have null. If that's not true, it's worth looking in to.
So we only have 1 day of data so far for the release channel, but I'm still seeing `null` as the dominant value https://sql.telemetry.mozilla.org/queries/66709#169114

> That should be impossible IIUC. However, I'm not at all surprised to find the number of users with FxA but without Sync to be extremely low, because the only sane way of getting into that state is via about:welcome and choosing to opt out of sync even though there's no other obvious thing of value offered by doing so.

Sorry I should have been more clear about this, what I was getting at is that the number of users with FxA = true but Sync = False seems **high** and that the *proportion of FxA clients with Sync configured* seems **low**. I'm just basing this on intuition: that the ability of users to turn sync off but still be signed in is relatively new, so for 10+% of FxA be in this situation seems high. All that said, looking at our single day of release data, its closer to 5% of FxA not having sync, so maybe that's a more reasonable proportion (although, we should figure out the `null` issue before we read into these numbers at all)

Thanks for the detailed response mark, this should be good documentation for this going forward. A few responses inline:

(In reply to Mark Hammond [:markh] from comment #12)
> (In reply to Leif Oines [:loines] from comment #10)
> If IIUC, it should be "impossible" for these to be null, they should always be true or false. null probably means 71 or 72 builds before the new probes landed. Now 71 is in release, I believe it should be impossible for 71 builds on the release channel to have null. If that's not true, it's worth looking in to.

So we only have 1 day of data so far for the release channel, but I'm still seeing `null` as the dominant value https://sql.telemetry.mozilla.org/queries/66709#169114

> That should be impossible IIUC. However, I'm not at all surprised to find the number of users with FxA but without Sync to be extremely low, because the only sane way of getting into that state is via about:welcome and choosing to opt out of sync even though there's no other obvious thing of value offered by doing so.

Sorry I should have been more clear about this, what I was getting at is that the number of users with FxA = true but Sync = False seems **high** and that the *proportion of FxA clients with Sync configured* seems **low**. I'm just basing this on intuition: that the ability of users to turn sync off but still be signed in is relatively new, so for 10+% of FxA be in this situation seems high. All that said, looking at our single day of release data, its closer to 5% of FxA not having sync, so maybe that's a more reasonable proportion (although, we should figure out the `null` issue before we read into these numbers at all)

Thanks for the detailed response mark, this should be good documentation for this going forward. A few responses inline:

(In reply to Mark Hammond [:markh] from comment #12)
> (In reply to Leif Oines [:loines] from comment #10)
> If IIUC, it should be "impossible" for these to be null, they should always be true or false. null probably means 71 or 72 builds before the new probes landed. Now 71 is in release, I believe it should be impossible for 71 builds on the release channel to have null. If that's not true, it's worth looking in to.

So we only have 1 day of data so far for the release channel, but I'm still seeing `null` as the dominant value https://sql.telemetry.mozilla.org/queries/66709#169114

> That should be impossible IIUC. However, I'm not at all surprised to find the number of users with FxA but without Sync to be extremely low, because the only sane way of getting into that state is via about:welcome and choosing to opt out of sync even though there's no other obvious thing of value offered by doing so.

Sorry I should have been more clear about this, what I was getting at is that the number of users with FxA = true but Sync = False seems **high** and that the *proportion of FxA clients with Sync configured* seems **low**. I'm just basing this on intuition: that the ability of users to turn sync off but still be signed in is relatively new, so for 10+% of FxA be in this situation seems high. All that said, looking at our single day of release data, its closer to 5% of FxA not having sync, so maybe that's a more reasonable proportion (although, we should figure out the `null` issue before we read into these numbers at all)

ps i added the charts for the release channel to the dash:
https://sql.telemetry.mozilla.org/dashboard/new-fxa-sync-probe-location (you need to hover on the chart to see the values since there's only one day of data so far)