Closed Bug 1438311 Opened 7 years ago Closed 7 years ago

Reevaluate whether AS_ENABLED ping is desired

Categories

(Firefox :: New Tab Page, enhancement, P2)

Product:
Firefox
Component:
New Tab Page
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
Firefox 61
Iteration:
61.2 - Apr 9
Tracking Flags:
Tracking Status
firefox60 --- wontfix
firefox61 --- fixed

People

(Reporter: Mardak, Assigned: nanj)

References

(Blocks 1 open bug)

Details

From bug 1433324 comment 3 and followup on irc: > it was originally put in to debug issues with shield not enabling a-s when expected... > I think it's fine to keep sending it with just "true"... might be a follow up issue to entirely get rid of that ping altogether? Though it might be something to discuss with the rest of the team...
let's try to get rid of this
Iteration: --- → 61.1 - Mar 26
Priority: -- → P3
Iteration: 61.1 - Mar 26 → ---
Iteration: --- → 61.2 - Apr 9
Priority: P3 → P2
Blocks: 1445083
Severity: normal → enhancement
Assignee: nobody → najiang
status-firefox61: --- → affected
As emtwo mentioned earlier that we used to send out this ping to verify if shield successfully flipped the pref "browser.newtabpage.activity-stream.enabled" in the experiments. Over time it evolved as the heartbeat ping of activity stream, and being used in various dashboards, such as https://sql.telemetry.mozilla.org/queries/51909#table. It makes sense to hardcode this value to be true since bug 1433324 already removed "browser.newtabpage.activity-stream.enabled". We can still treat it as the AS heartbeat, and leverage it to understand the adoption ratio of AS.
Sounds like the reevaluation is that we want to keep it around, so marking fixed. ;)
status-firefox61: wontfix → fixed
Target Milestone: --- → Firefox 61
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Component: Activity Streams: Newtab → New Tab Page
You need to log in before you can comment on or make changes to this bug.