# Feedback: Improvements for Proposal #### Contextualize when we want to use a new profile definition [Comment](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAADCGzkRA) We might want to include use cases for "new profile" definition - a time series of profile flux - observing differences in the behaviors of new-profile cohorts who started using Firefox at different times - targeting profiles for experiments - classifying profiles who appear in an experiment Be clear about what use cases this covers, and what it doesn't. Note that this won't cover targeting profiles in experiments. Thought: maybe include this in appendix? #### Background info on PCD (and First Use Date) [Comment](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAACthdNko) Add descriptions of what PCD and firstUseDate actually physically measure. Include summary and documentation for known issues with PCD. Include any analysis (dependent on [this bug](https://www.google.com/url?q=https://bugzilla.mozilla.org/show_bug.cgi?id%3D1529012&sa=D&ust=1559056941514000&usg=AFQjCNH9IWGFpq3SNH3T50YUqZGf7RjeIQ)) comparing the two. #### Add analysis comparison for more new profile definitions [Comment1](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAADCGzkUs) - PCD == 1 (no reset) - recieve new profile ping Explicit about why these are being rejected #### Footnotes: Explaing PCD Windowing and Technical/Performance Comparison Add footnote why we're defining PCD based definitions with a window. Add footnote on technical / performacne search - space tradeoffs for each definition. Or in it's own section.
Bug 1539762 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
# Feedback: Improvements for Proposal #### Contextualize when we want to use a new profile definition [Comment](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAADCGzkRA) We might want to include use cases for "new profile" definition - a time series of profile flux - observing differences in the behaviors of new-profile cohorts who started using Firefox at different times - targeting profiles for experiments - classifying profiles who appear in an experiment Be clear about what use cases this covers, and what it doesn't. Note that this won't cover targeting profiles in experiments. Thought: maybe include this in appendix? #### Background info on PCD (and First Use Date) [Comment](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAACthdNko) Add descriptions of what PCD and firstUseDate actually physically measure. Include summary and documentation for known issues with PCD. Include any analysis (dependent on [this bug](https://www.google.com/url?q=https://bugzilla.mozilla.org/show_bug.cgi?id%3D1529012&sa=D&ust=1559056941514000&usg=AFQjCNH9IWGFpq3SNH3T50YUqZGf7RjeIQ)) comparing the two. #### Add analysis comparison for more new profile definitions [Comment1](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAADCGzkUs) - PCD == 1 (no reset) - recieve new profile ping Explicit about why these are being rejected #### Footnotes: Explaing PCD Windowing and Technical/Performance Comparison Add footnote why we're defining PCD based definitions with a window. Add footnote on technical / performacne search - space tradeoffs for each definition. Or in it's own section. #### [Important!] Investigate client_id rolling Tim brought this up, apparently, when a profile turns on and turns off Telemetry, their client_id gets reset. This could have major impact on the interpretation of the proposed definition (FA). #### Additional Analysis between included and excluded PCD_7 Group To strengthen the case that these populations are similar and their usage patterns overlap, maybe include some comparisons of distributions for different the groups (for different metrics).
# Feedback: Improvements for Proposal #### Contextualize when we want to use a new profile definition [Comment](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAADCGzkRA) We might want to include use cases for "new profile" definition - a time series of profile flux - observing differences in the behaviors of new-profile cohorts who started using Firefox at different times - targeting profiles for experiments - classifying profiles who appear in an experiment Be clear about what use cases this covers, and what it doesn't. Note that this won't cover targeting profiles in experiments. Thought: maybe include this in appendix? #### Background info on PCD (and First Use Date) [Comment](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAACthdNko) Add descriptions of what PCD and firstUseDate actually physically measure. Include summary and documentation for known issues with PCD. Include any analysis (dependent on [this bug](https://www.google.com/url?q=https://bugzilla.mozilla.org/show_bug.cgi?id%3D1529012&sa=D&ust=1559056941514000&usg=AFQjCNH9IWGFpq3SNH3T50YUqZGf7RjeIQ)) comparing the two. #### Add analysis comparison for more new profile definitions [Comment1](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAADCGzkUs) - PCD == 1 (no reset) - recieve new profile ping Explicit about why these are being rejected #### Footnotes: Explaing PCD Windowing and Technical/Performance Comparison Add footnote why we're defining PCD based definitions with a window. Add footnote on technical / performacne search - space tradeoffs for each definition. Or in it's own section. #### Additional Analysis between included and excluded PCD_7 Group To strengthen the case that these populations are similar and their usage patterns overlap, maybe include some comparisons of distributions for different the groups (for different metrics). #### [Important!] Investigate client_id rolling Tim brought this up, apparently, when a profile turns on and turns off Telemetry, their client_id gets reset. This could have major impact on the interpretation of the proposed definition (FA). References: * [Telemetry scalar for Telemetry re-enable](https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/Scalars.yaml#2112-2115,2117-2124) * [Fix "optout" ping](https://bugzilla.mozilla.org/show_bug.cgi?id=1445921) - Check comment 3 (Chutten) * [code which resets subsession and profile subsession counter](https://phabricator.services.mozilla.com/D1948) * Check opt-out pings Actions: * Test behavior locally
# Feedback: Improvements for Proposal #### Contextualize when we want to use a new profile definition [Comment](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAADCGzkRA) We might want to include use cases for "new profile" definition - a time series of profile flux - observing differences in the behaviors of new-profile cohorts who started using Firefox at different times - targeting profiles for experiments - classifying profiles who appear in an experiment Be clear about what use cases this covers, and what it doesn't. Note that this won't cover targeting profiles in experiments. Thought: maybe include this in appendix? #### Background info on PCD (and First Use Date) [Comment](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAACthdNko) Add descriptions of what PCD and firstUseDate actually physically measure. Include summary and documentation for known issues with PCD. Include any analysis (dependent on [this bug](https://www.google.com/url?q=https://bugzilla.mozilla.org/show_bug.cgi?id%3D1529012&sa=D&ust=1559056941514000&usg=AFQjCNH9IWGFpq3SNH3T50YUqZGf7RjeIQ)) comparing the two. #### Add analysis comparison for more new profile definitions [Comment1](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAADCGzkUs) - PCD == 1 (no reset) - recieve new profile ping Explicit about why these are being rejected #### Footnotes: Explaing PCD Windowing and Technical/Performance Comparison Add footnote why we're defining PCD based definitions with a window. Add footnote on technical / performacne search - space tradeoffs for each definition. Or in it's own section. #### Additional Analysis between included and excluded PCD_7 Group To strengthen the case that these populations are similar and their usage patterns overlap, maybe include some comparisons of distributions for different the groups (for different metrics). #### [Important!] Investigate client_id rolling Tim brought this up, apparently, when a profile turns on and turns off Telemetry, their client_id gets reset. This could have major impact on the interpretation of the proposed definition (FA). References: * [Telemetry scalar for Telemetry re-enable](https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/Scalars.yaml#2112-2115,2117-2124) * [Fix "optout" ping](https://bugzilla.mozilla.org/show_bug.cgi?id=1445921) - Check comment 3 by Chutten * [code which resets subsession and profile subsession counter](https://phabricator.services.mozilla.com/D1948) * Check opt-out pings Actions: * Test behavior locally
# Feedback: Improvements for Proposal #### Contextualize when we want to use a new profile definition [Comment](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAADCGzkRA) We might want to include use cases for "new profile" definition - a time series of profile flux - observing differences in the behaviors of new-profile cohorts who started using Firefox at different times - targeting profiles for experiments - classifying profiles who appear in an experiment Be clear about what use cases this covers, and what it doesn't. Note that this won't cover targeting profiles in experiments. Thought: maybe include this in appendix? #### Background info on PCD (and First Use Date) [Comment](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAACthdNko) Add descriptions of what PCD and firstUseDate actually physically measure. Include summary and documentation for known issues with PCD. Include any analysis (dependent on [this bug](https://www.google.com/url?q=https://bugzilla.mozilla.org/show_bug.cgi?id%3D1529012&sa=D&ust=1559056941514000&usg=AFQjCNH9IWGFpq3SNH3T50YUqZGf7RjeIQ)) comparing the two. #### Add analysis comparison for more new profile definitions [Comment1](https://docs.google.com/a/mozilla.com/document/d/19hz1flKTc8J27aahx9rePIOEm6LOJpj0ttUpnL5cYOI/edit?disco=AAAADCGzkUs) - PCD == 1 (no reset) - recieve new profile ping Explicit about why these are being rejected #### Footnotes: Explaing PCD Windowing and Technical/Performance Comparison Add footnote why we're defining PCD based definitions with a window. Add footnote on technical / performacne search - space tradeoffs for each definition. Or in it's own section. #### Additional Analysis between included and excluded PCD_7 Group To strengthen the case that these populations are similar and their usage patterns overlap, maybe include some comparisons of distributions for different the groups (for different metrics). #### [Important!] Investigate client_id rolling Tim brought this up, apparently, when a profile turns on and turns off Telemetry, their client_id gets reset. This could have major impact on the interpretation of the proposed definition (FA). References: * [Telemetry scalar for Telemetry re-enable](https://searchfox.org/mozilla-central/source/toolkit/components/telemetry/Scalars.yaml#2112-2115,2117-2124) * [Fix "optout" ping](https://bugzilla.mozilla.org/show_bug.cgi?id=1445921) - Check comment 3 by Chutten * [code which resets subsession and profile subsession counter](https://phabricator.services.mozilla.com/D1948) * Look into opt-out pings, and any other data around this behavior Actions: * Test behavior locally