Given that all pingcentre telemetry (including Activity Stream) will be removed by EoY, we will need to rely on Glean pings instead. My understanding is that Firefox Desktop already emits the following Glean pings: - [pocket.click](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_click) - [pocket.impression](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_impression) - [pocket.save](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_save) Currently these pings do not include a content identifier. 1. Could you add both the `tileId` and the (not-yet-existing) `recommendId` fields from the Pocket recommendation to each of the corresponding Glean pings? 2. Should we disable Activity Stream, to prevent double-counting engagement? This would need some discussion with @kirill
Bug 1854245 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.
Given that all pingcentre telemetry (including Activity Stream) will be removed by EoY, we will need to rely on Glean pings instead. My understanding is that Firefox Desktop already emits the following Glean pings: - [pocket.click](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_click) - [pocket.impression](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_impression) - [pocket.save](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_save) Currently these pings do not include a content identifier. 1. Could you add both the `tileId` and the (not-yet-existing) `recommendId` fields from the Pocket recommendation to each of the corresponding Glean pings? 2. Disable Activity Stream, to prevent double-counting engagement. Kirill and I agreed this would be good to prevent double-counting engagement, and that there is no reason to keep the Activity Stream data around.
Given that all pingcentre telemetry (including Activity Stream) will be removed by EoY, we will need to rely on Glean pings instead. My understanding is that Firefox Desktop already emits the following Glean pings: - [pocket.click](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_click) - [pocket.impression](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_impression) - [pocket.save](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_save) Currently these pings do not include a content identifier. 1. Could you add both the `tileId` and the (not-yet-existing) `recommendId` fields from the Pocket recommendation to each of the corresponding Glean pings? 2. Stop Pocket New Tab Activity Stream events from being emitted, to prevent double-counting engagement.
Given that all pingcentre telemetry (including Activity Stream) will be removed by EoY, we will need to rely on Glean pings instead. My understanding is that Firefox Desktop already emits the following Glean pings: - [pocket.click](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_click) - [pocket.impression](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_impression) - [pocket.save](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_save) Currently these pings do not include a content identifier. 1. ~Could you add both the `tileId` and the (not-yet-existing) `recommendId` fields from the Pocket recommendation to each of the corresponding Glean pings?~ Add new recommendation `id` field to Glean, and stop using the deprecated `tileId` field. (Changed based on [feedback in #63](https://github.com/Pocket/firefox-api-proxy/pull/63/files#r1340352483).) 2. Stop Pocket New Tab Activity Stream events from being emitted, to prevent double-counting engagement.
Given that all pingcentre telemetry (including Activity Stream) will be removed by EoY, we will need to rely on Glean pings instead. My understanding is that Firefox Desktop already emits the following Glean pings: - [pocket.click](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_click) - [pocket.impression](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_impression) - [pocket.save](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_save) Currently these pings do not include a content identifier. 1. Add new recommendation `id` field to Glean, and stop using the deprecated `tileId` field. (Changed based on [feedback in #63](https://github.com/Pocket/firefox-api-proxy/pull/63/files#r1340352483). ~Could you add both the `tileId` and the (not-yet-existing) `recommendId` fields from the Pocket recommendation to each of the corresponding Glean pings?~ ) 2. Stop Pocket New Tab Activity Stream events from being emitted, to prevent double-counting engagement.
Given that all pingcentre telemetry (including Activity Stream) will be removed by EoY, we will need to rely on Glean pings instead. My understanding is that Firefox Desktop already emits the following Glean pings: - [pocket.click](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_click) - [pocket.impression](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_impression) - [pocket.save](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_save) Currently these pings do not include a content identifier. 1. Add new recommendation `id` field to Glean, and stop using the deprecated `tileId` field. (Changed based on [feedback in #63](https://github.com/Pocket/firefox-api-proxy/pull/63/files#r1340352483). ~Could you add both the `tileId` and the (not-yet-existing) `recommendId` fields from the Pocket recommendation to each of the corresponding Glean pings?~) 2. Stop Pocket New Tab Activity Stream events from being emitted, to prevent double-counting engagement.
Given that all pingcentre telemetry (including Activity Stream) will be removed by EoY, we will need to rely on Glean pings instead. My understanding is that Firefox Desktop already emits the following Glean pings: - [pocket.click](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_click) - [pocket.impression](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_impression) - [pocket.save](https://dictionary.telemetry.mozilla.org/apps/firefox_desktop/metrics/pocket_save) Currently these pings do not include a content identifier. 1. Add new recommendation `id` field to Glean, and stop using the deprecated `tileId` field. (Changed based on [feedback in #63](https://github.com/Pocket/firefox-api-proxy/pull/63/files#r1340352483). ~Could you add both the `tileId` and the (not-yet-existing) `recommendId` fields from the Pocket recommendation to each of the corresponding Glean pings?~) 2. ~Stop Pocket New Tab Activity Stream events from being emitted, to prevent double-counting engagement.~ Because the newtab Glean ping has been around for a while (as chutten mentioned), the new/additional Prefect data pulls (using Glean data) will need to filter to Firefox >= 121.