Skip to content

Add engine toggled telemetry for PDS - #7813

Open
lougeniaC64 wants to merge 1 commit into
mainfrom
add-pds-metrics
Open

lougeniaC64 wants to merge 1 commit into
mainfrom
add-pds-metrics

Conversation

@lougeniaC64

@lougeniaC64 lougeniaC64 commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Fixes SYNC-5532

Adding metrics for per-device sync of when a user enables or disables an engine.

Pull Request checklist

  • Breaking changes: This PR follows our breaking change policy
    • This PR follows the breaking change policy:
      • This PR has no breaking API changes, or
      • There are corresponding PRs for our consumer applications that resolve the breaking changes and have been approved
  • Quality: This PR builds and tests run cleanly
    • Note:
      • For changes that need extra cross-platform testing, consider adding [ci full] to the PR title.
      • If this pull request includes a breaking change, consider cutting a new release after merging.
  • Tests: This PR includes thorough tests or an explanation of why it does not
  • Changelog: This PR includes a changelog entry in CHANGELOG.md or an explanation of why it does not need one
    • Any breaking changes to Swift or Kotlin binding APIs are noted explicitly
  • Dependencies: This PR follows our dependency management guidelines
    • Any new dependencies are accompanied by a summary of the due diligence applied in selecting them.

@lougeniaC64

lougeniaC64 commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor Author

Data Request

  1. What questions will you answer with this data?
    When data about when a user enables or disables a sync engine after per-device sync is released.

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

  • Provide information essential for advancing a business objective such as supporting OKRs: To know more about Sync customers, their behavior, and their experience.
  1. What alternative methods did you consider to answer these questions? Why were they not sufficient?
    No alternatives.

  2. Can current instrumentation answer these questions?
    No.

  3. 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 the user enables or disables a per-device sync engine and how many other engines are enabled. interaction https://mozilla-hub.atlassian.net/browse/SYNC-5532
  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.
  • Often the Privacy Notice for your product will link to where the documentation is expected to be.
  • Common examples for Mozilla products/services:
    • If this collection is Telemetry you can state "This collection is documented in its definitions files Histograms.json, Scalars.yaml, and/or Events.yaml and in the Probe Dictionary at https://probes.telemetry.mozilla.org."
    • If this data is collected using the Glean SDK you can state “This collection is documented in the Glean Dictionary at https://dictionary.telemetry.mozilla.org/"
  • In some cases, documentation is included in the project’s repository.

This collection is documented in the Glean Dictionary at https://dictionary.telemetry.mozilla.org/

  1. How long will this data be collected? Choose one of the following:
  • I want to permanently monitor this data.
  1. What populations will you measure?

All channels in all countries in all locales, for Firefox iOS and Fenix

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

  2. Please provide a general description of how you will analyze this data.
    Via graphs in Looker/Redash.

  3. Where do you intend to share the results of your analysis?
    Internally to drive future product decisions.

  4. Is there a third-party tool (i.e. not Glean or Telemetry) that you are proposing to use for this data collection? If so:

No.

@lougeniaC64
lougeniaC64 force-pushed the add-pds-metrics branch 3 times, most recently from b6b9dc3 to 5077694 Compare November 19, 2026 23:41
@lougeniaC64
lougeniaC64 marked this pull request as ready for review November 20, 2026 00:04

@travis79 travis79 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Data Request

1. What questions will you answer with this data?
   When data about when a user enables or disables a sync engine after per-device sync is released.

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


* Provide information essential for advancing a business objective such as supporting OKRs: To know more about Sync customers, their behavior, and their experience.


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

4. Can current instrumentation answer these questions?
   No.

5. List all proposed measurements and indicate the category of data collection for each measurement, using the [Firefox data collection categories](https://wiki.mozilla.org/Data_Collection) 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 the user enables or disables a per-device sync engine and how many other engines are enabled. interaction https://mozilla-hub.atlassian.net/browse/SYNC-5532

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


* Often the Privacy Notice for your product will link to where the documentation is expected to be.

* Common examples for Mozilla products/services:
  
  * If this collection is Telemetry you can state "This collection is documented in its definitions files Histograms.json, Scalars.yaml, and/or Events.yaml and in the Probe Dictionary at https://probes.telemetry.mozilla.org."
  * If this data is collected using the Glean SDK you can state “This collection is documented in the Glean Dictionary at https://dictionary.telemetry.mozilla.org/"

* In some cases, documentation is included in the project’s repository.

This collection is documented in the Glean Dictionary at https://dictionary.telemetry.mozilla.org/

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


* I want to permanently monitor this data.


8. What populations will you measure?

All channels in all countries in all locales, for Firefox iOS and Fenix

9. If this data collection is default on, what is the opt-out mechanism for users?
   Standard Firefox telemetry controls

10. Please provide a general description of how you will analyze this data.
    Via graphs in Looker/Redash.

11. Where do you intend to share the results of your analysis?
    Internally to drive future product decisions.

12. Is there a third-party tool (i.e. not Glean or Telemetry) that you are proposing to use for this data collection? If so:

No.

Data Review Form (to be filled by Data Stewards)

  1. Is there or will there be documentation that describes the schema for the ultimate data set in a public, complete, and accurate way?
  1. Is there a control mechanism that allows the user to turn the data collection on and off?
  • Yes, the application settings provide data collection opt-out choices.
  1. If the request is for permanent data collection, is there someone who will monitor the data over time?
  • Permanent collection to be monitored by @lougeniaC64 backed up by the A-S team.
  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
  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 (whether anonymous or otherwise; e.g., username, random IDs, etc.
  • 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+

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants