> Mathijs, what datasets is the recommendation_id identifier permitted to join to? Its inclusion in the "newtab" ping gives it access to client_id. Does this answer from the review request answer this sufficiently, or should I add some more detail? > 10. Please provide a general description of how you will analyze this data. > We will join the above Firefox events with metadata for the content and server response. > As stated above, large groups of users receive the same recommendation_id, and therefore it cannot be associated with any personal information. Examples of content metadata are: the curator's name, topic, curator tags. The main server metadata is the response time. These backend events are emitted using Snowplow. Eventually they will be migrated to Glean as well, but we don't have a concrete timeline for that yet.
Bug 1854245 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> Mathijs, what datasets is the recommendation_id identifier permitted to join to? Its inclusion in the "newtab" ping gives it access to client_id. Does this answer from the review request answer this sufficiently, or should I add some more detail? > 10. Please provide a general description of how you will analyze this data. > > We will join the above Firefox events with metadata for the content and server response. > > As stated above, large groups of users receive the same recommendation_id, and therefore it cannot be associated with any personal information. Examples of content metadata are: the curator's name, topic, curator tags. The main server metadata is the response time. These backend events are emitted using Snowplow. Eventually they will be migrated to Glean as well, but we don't have a concrete timeline for that yet.