Skip to content
This repository has been archived by the owner on Feb 20, 2023. It is now read-only.

For #22147 - New search term groups telemetry #22368

Merged
merged 2 commits into from
Nov 16, 2021
Merged

For #22147 - New search term groups telemetry #22368

merged 2 commits into from
Nov 16, 2021

Conversation

Mugurell
Copy link
Contributor

@Mugurell Mugurell commented Nov 8, 2021

3 new events added for when the user opens a tab, closes one or closes all from a search group.
Kimmy to confirm if the current https://dictionary.telemetry.mozilla.org/apps/fenix/metrics/history_search_term_group_tapped is okay to be considered the 4th we needed.

Pull Request checklist

  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not
  • Accessibility: The code in this PR follows accessibility best practices or does not include any user facing features. In addition, it includes a screenshot of a successful accessibility scan to ensure no new defects are added to the product.

To download an APK when reviewing a PR:

  1. click on Show All Checks,
  2. click Details next to "Taskcluster (pull_request)" after it appears and then finishes with a green checkmark,
  3. click on the "Fenix - assemble" task, then click "Run Artifacts".
  4. the APK links should be on the left side of the screen, named for each CPU architecture

@Mugurell Mugurell requested review from a team as code owners November 8, 2021 15:43
@Mugurell
Copy link
Contributor Author

Mugurell commented Nov 8, 2021

Request for data collection review form

All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.

  1. What questions will you answer with this data?
  • This data will help us understand how users interact with new search groups from history.
  1. Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?
  • Better asses feature importance.

  1. What alternative methods did you consider to answer these questions? Why were they not sufficient?
  • There are no other alternatives.

  1. Can current instrumentation answer these questions?
  • No.

  1. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories found on the Mozilla wiki.

    Note that the data steward reviewing your request will characterize your data collection based on the highest (and most sensitive) category.
Measurement Description Data Collection Category Tracking Bug #
When a tab from the search term group is opened Category 2 - interaction data #22147
When a tab from the search term group is closed Category 2 - interaction data #22147
When all tabs from the search term group are closed Category 2 - interaction data #22147
  1. Please provide a link to the documentation for this data collection which describes the ultimate data set in a public, complete, and accurate way.
  1. How long will this data be collected? Choose one of the following:
  • One year (ending on November 1st, 2022), with the option to renew at that point.

  1. What populations will you measure?
  • All channels, all locales, all countries

  1. If this data collection is default on, what is the opt-out mechanism for users?
  • Default Glean SDK opt-out mechanism.

  1. Please provide a general description of how you will analyze this data.
  • Glean and Amplitude.

  1. Where do you intend to share the results of your analysis?
  • 
Only on Glean, Amplitude, and with mobile teams.

  1. Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection?
  • No third-party tools.

@Mugurell Mugurell added needs:data-review PR is awaiting a data review needs:review PRs that need to be reviewed labels Nov 8, 2021
Copy link
Contributor

@jonalmeida jonalmeida left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

eng r+

app/metrics.yaml Outdated
bugs:
- https://github.com/mozilla-mobile/fenix/issues/22147
data_reviews:
- ????????????
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

raw

app/metrics.yaml Outdated
search_term_group_open_tab:
type: event
description: |
A user opens a tab from the search term group.
Copy link
Contributor

@jonalmeida jonalmeida Nov 8, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

From reading these descriptions, I thought these were probes for the tabs tray itself. Might be good to clarify the location where these probes are being added. For example..

Suggested change
A user opens a tab from the search term group.
A user opens a tab from the search term group from the history list.

(same for the other two probes)

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. Looks like these are for History. FYI, I recently add one telemetry for this requirement #22300

Copy link
Contributor

@rocketsroger rocketsroger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please move these to the history category. Also double check the PR I linked. Thanks,

app/metrics.yaml Outdated
search_term_group_open_tab:
type: event
description: |
A user opens a tab from the search term group.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. Looks like these are for History. FYI, I recently add one telemetry for this requirement #22300

@Mugurell
Copy link
Contributor Author

Mugurell commented Nov 9, 2021

Please move these to the history category. Also double check the PR I linked. Thanks,

These new probes are already in the history category and use the naming scheme from #22300, them being recorded as

        {
          "timestamp": 10862,
          "category": "history",
          "name": "search_term_group_tapped"
        },
        {
          "timestamp": 14257,
          "category": "history",
          "name": "search_term_group_open_tab"
        },
                {
          "timestamp": 20389,
          "category": "history",
          "name": "search_term_group_remove_tab"
        },
        {
          "timestamp": 21755,
          "category": "history",
          "name": "search_term_group_remove_all"
        }

so in Glean similarly to https://dictionary.telemetry.mozilla.org/apps/fenix/metrics/history_search_term_group_tapped the 3 events will actually be:

- history.search_term_group_open_tab
- history.search_term_group_remove_tab
- history.search_term_group_remove_all

Will add the history reference in the probe description and also add some tests.

@rocketsroger
Copy link
Contributor

Request for data collection review form

All questions are mandatory. You must receive review from a data steward peer on your responses to these questions before shipping new data collection.

1. What questions will you answer with this data?


* This data will help us understand how users interact with new search groups from history.


1. Why does Mozilla need to answer these questions? Are there benefits for users? Do we need this information to address product or business requirements?


* Better asses feature importance.


1. What alternative methods did you consider to answer these questions? Why were they not sufficient?


* There are no other alternatives.


1. Can current instrumentation answer these questions?


* No.


1. List all proposed measurements and indicate the category of data collection for each measurement, using the Firefox data collection categories found on the Mozilla wiki.
   
   Note that the data steward reviewing your request will characterize your data collection based on the highest (and most sensitive) category.

Measurement Description Data Collection Category Tracking Bug #
When a tab from the search term group is opened Category 2 - interaction data #22147
When a tab from the search term group is closed Category 2 - interaction data #22147
When all tabs from the search term group are closed Category 2 - interaction data #22147

1. Please provide a link to the documentation for this data collection which describes the ultimate data set in a public, complete, and accurate way.


* [https://dictionary.telemetry.mozilla.org/apps/fenix
  ](https://dictionary.telemetry.mozilla.org/apps/fenix%E2%80%A8)


1. How long will this data be collected? Choose one of the following:


* One year (ending on November 1st, 2022), with the option to renew at that point.


1. What populations will you measure?


* All channels, all locales, all countries


1. If this data collection is default on, what is the opt-out mechanism for users?


* Default Glean SDK opt-out mechanism.


1. Please provide a general description of how you will analyze this data.


* Glean and Amplitude.


1. Where do you intend to share the results of your analysis?


* Only on Glean, Amplitude, and with mobile teams.


1. Is there a third-party tool (i.e. not Telemetry) that you are proposing to use for this data collection?


* No third-party tools.

Data Review

  1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?

Yes, through the metrics.yaml file and the Glean Dictionary

  1. Is there a control mechanism that allows the user to turn the data collection on and off?

Yes, through the "Send Usage Data" preference in the application settings

  1. If the request is for permanent data collection, is there someone who will monitor the data over time?

N/A, collection set to end or be renewed by 2022-11-01

  1. Using the category system of data types on the Mozilla wiki, what collection type of data do the requested measurements fall under?

Category 2, Interaction data

  1. Is the data collection request for default-on or default-off?

default-on

  1. Does the instrumentation include the addition of any new identifiers?

No

  1. Is the data collection covered by the existing Firefox privacy notice?

Yes

  1. Does the data collection use a third-party collection tool?

No

Result

data-review+

@rocketsroger rocketsroger removed the needs:data-review PR is awaiting a data review label Nov 9, 2021
@rocketsroger
Copy link
Contributor

Looks good. I've data reviewed. Please update the data-review link in metrics.yml. Thanks

@Mugurell
Copy link
Contributor Author

Mugurell commented Nov 9, 2021

Thank you Roger!
Since I've also added some tests and updated that documentation I'll wait a bit for @jonalmeida to maybe have a second quick look, if everything seems okay.

@Mugurell
Copy link
Contributor Author

Mugurell commented Nov 9, 2021

Kimmy said will also leave a comment on whether these events look right or not.
Adding the do-not-land label in the interim.

@Mugurell Mugurell added pr:do-not-land and removed needs:review PRs that need to be reviewed labels Nov 9, 2021
@rocketsroger rocketsroger self-requested a review November 10, 2021 17:15
@Mugurell
Copy link
Contributor Author

Kimmy confirmed these events look good.

@Mugurell Mugurell added pr:needs-landing PRs that are ready to land [Will be merged by Mergify] and removed pr:do-not-land labels Nov 16, 2021
@Mugurell
Copy link
Contributor Author

Ohh I see @rocketsroger requested changes and the merge is blocked.
Asking for a re-review.

@Mugurell Mugurell added needs:review PRs that need to be reviewed and removed pr:needs-landing PRs that are ready to land [Will be merged by Mergify] labels Nov 16, 2021
@rocketsroger rocketsroger removed the needs:review PRs that need to be reviewed label Nov 16, 2021
@Mugurell Mugurell added the pr:needs-landing PRs that are ready to land [Will be merged by Mergify] label Nov 16, 2021
@mergify mergify bot merged commit 17865bd into mozilla-mobile:main Nov 16, 2021
@Mugurell Mugurell deleted the searchTermGroupsTelemetry branch November 16, 2021 16:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pr:needs-landing PRs that are ready to land [Will be merged by Mergify]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants