Right now because of how we deploy what's new panel / fxa badges through the same `cfr` provider, these are showing up in the `messaging_system.cfr ` and making it difficult to compute overall click through rate etc. This is really important for us to automate analysis and estimate baselines. We don't have necessarily change the bucket, but could we update the `group` so they show up elsewhere?
Bug 1638891 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Right now because of how we deploy what's new panel / fxa badges through the same `cfr` provider, these are showing up in the `messaging_system.cfr ` and making it difficult to compute overall click through rate etc. This is really important for us to automate analysis and estimate baselines. We don't have necessarily change the bucket/provider, but could we update the `group` so they show up elsewhere?
Right now because of how we deploy what's new panel / fxa badges through the same `cfr` provider, these are showing up in the `messaging_system.cfr ` table and making it difficult to compute overall click through rate etc. This is really important for us to automate analysis and estimate baselines. We don't have necessarily change the bucket/provider, but could we update the `group` so they show up elsewhere?
Right now because of how we deploy what's new panel / fxa badges through the same `cfr` provider, these are showing up in the `messaging_system.cfr ` table and making it difficult to compute overall click through rate etc. This is really important for us to automate analysis and estimate baselines. We don't have to necessarily change the bucket/provider, but could we update the `group` so they show up elsewhere?