Bug 1867627 split up the long about:welcome message id telemetry components for IMPRESSIONs. It didn't, however, split them up for other telemetry events: here's a [look](https://mozilla.cloud.looker.com/looks/2033?toggle=det,fil,pik&qid=NyQCoc0TQf1mBXrDM6D0Tm) that shows how things currently look. I think the key is that [that patch](https://phabricator.services.mozilla.com/D196496#change-mDO3gEkXA9Mz) changed the call to `sendImpressionTelemetry`, but did not deal with the users of the [WelcomeScreen messageId prop](https://searchfox.org/mozilla-central/rev/48eb17ba6bb3ce3198ee136785487c26cb64a025/browser/components/aboutwelcome/content-src/components/MultiStageAboutWelcome.jsx#249) The value in doing this is that it makes the data meaningfully easier to work with in both Looker and BigQuery, saving time for PMs, Engineers, and Data Scientists.
Bug 1890073 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.
Bug 1867627 split up the long about:welcome message id telemetry components for IMPRESSIONs. It didn't, however, split them up for other telemetry events: here's a [look](https://mozilla.cloud.looker.com/looks/2033?toggle=det,fil,pik&qid=NyQCoc0TQf1mBXrDM6D0Tm) that shows the current state. I think the key is that [that patch](https://phabricator.services.mozilla.com/D196496#change-mDO3gEkXA9Mz) changed the call to `sendImpressionTelemetry`, but did not deal with the users of the [WelcomeScreen messageId prop](https://searchfox.org/mozilla-central/rev/48eb17ba6bb3ce3198ee136785487c26cb64a025/browser/components/aboutwelcome/content-src/components/MultiStageAboutWelcome.jsx#249) The value in doing this is that it makes the data meaningfully easier to work with in both Looker and BigQuery, saving time for PMs, Engineers, and Data Scientists.
Bug 1867627 split up the long about:welcome message id telemetry components for IMPRESSIONs. It didn't, however, split them up for other telemetry events: here's a [look](https://mozilla.cloud.looker.com/looks/2033?toggle=det,fil,pik&qid=NyQCoc0TQf1mBXrDM6D0Tm) that shows the current state. I think the key is that [that patch](https://phabricator.services.mozilla.com/D196496#change-mDO3gEkXA9Mz) changed the call to `sendImpressionTelemetry`, but did not deal with the users of the [WelcomeScreen messageId prop](https://searchfox.org/mozilla-central/rev/48eb17ba6bb3ce3198ee136785487c26cb64a025/browser/components/aboutwelcome/content-src/components/MultiStageAboutWelcome.jsx#249). The value in doing this is that it makes the data meaningfully easier to work with in both Looker and BigQuery, saving time for PMs, Engineers, and Data Scientists.
Bug 1867627 split up the long about:welcome message id telemetry components for IMPRESSIONs. It didn't, however, split them up for other telemetry events: here's a [look](https://mozilla.cloud.looker.com/looks/2033?toggle=det,fil,pik&qid=NyQCoc0TQf1mBXrDM6D0Tm) that shows the current state. Fixing this will make it notably more efficient and practical for PMs, Engineers, and Data Scientists to work with `about:welcome` telemetry in both Looker and BigQuery. I think the key is that [that patch](https://phabricator.services.mozilla.com/D196496#change-mDO3gEkXA9Mz) changed the call to `sendImpressionTelemetry`, but did not deal with the users of the [WelcomeScreen messageId prop](https://searchfox.org/mozilla-central/rev/48eb17ba6bb3ce3198ee136785487c26cb64a025/browser/components/aboutwelcome/content-src/components/MultiStageAboutWelcome.jsx#249). Acceptance criteria: * get CLICK_BUTTON, SESSION_END, SELECT_CHECKBOX working * check and see if there are any other ping types / code paths where this should be fixed * after this lands, file a bug in DO asking the Data Org to expose the various new fields in the Event Count Look (maybe needs onboarding table change?) like they are already exposed in the Messaging System Look.