Send individual components for message impression telemetry
Categories
(Firefox :: Messaging System, task, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox123 | --- | fixed |
People
(Reporter: Mardak, Assigned: nsauermann)
References
(Blocks 1 open bug)
Details
(Whiteboard: [omc])
Attachments
(1 file)
Currently the message id is a concatenation of various components: ${props.message_id}_${order}_${screen.id}_${screenInitials}
:
https://searchfox.org/mozilla-central/rev/d84469b005106c5ab0f65e283f71c1415ce76c54/browser/components/aboutwelcome/content-src/components/MultiStageAboutWelcome.jsx#67-71
We can keep backwards compatibility (if desired) by also sending the individual components. These various parts were added for different requests, e.g., treat message showing on screen 1 vs 2 differently, but made it trickier to query without, e.g., treat same screen independent of index. See bug 1619694, bug 1719707, bug 1790655, etc.
Kinda related but could be split out are related telemetry that happen to be separate call sites, e.g., for actions, that might want some cleanup so that each place consistently passes in the components:
https://searchfox.org/mozilla-central/rev/d84469b005106c5ab0f65e283f71c1415ce76c54/browser/components/aboutwelcome/content-src/components/MultiStageAboutWelcome.jsx#377-378,430-434
Reporter | ||
Comment 1•10 months ago
|
||
Now with glean bug 1825863, it should hopefully be relatively straightforward to add additional fields for each component:
Updated•10 months ago
|
Updated•10 months ago
|
Updated•9 months ago
|
Updated•9 months ago
|
Comment 4•9 months ago
|
||
bugherder |
Updated•6 months ago
|
Description
•