Closed
Bug 1638891
Opened 5 years ago
Closed 5 years ago
messaging_system.cfr table should only include actual CFRs
Categories
(Firefox :: Messaging System, enhancement, P1)
Firefox
Messaging System
Tracking
()
Tracking | Status | |
---|---|---|
firefox77 | --- | unaffected |
firefox78 | --- | fixed |
People
(Reporter: k88hudson, Assigned: andreio)
References
Details
Attachments
(1 file)
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?
![]() |
||
Updated•5 years ago
|
Assignee: nobody → andrei.br92
Severity: -- → S3
Iteration: --- → 78.2 - May 18 - May 31
status-firefox77:
--- → unaffected
status-firefox78:
--- → affected
Priority: -- → P1
Assignee | ||
Comment 1•5 years ago
|
||
Pushed by aoprea@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/234ea58aa683
Create specific pingTypes for moments and what's new r=nanj
Comment 3•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 78
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•