trishalfonso@google.com src/chrome/browser/tpcd/OWNERS Records the relationship between profile and client eligibility for 3PCD Experiments. All profiles on the same client share a single eligibility value for experiment purposes, but it is possible that an individual profile on the client has a different eligibility than the client value used. This histogram records how often a profile's eligibility matches and mismatches with the client eligibility used for the experiment. Recorded each time a profile is first loaded in a browser session. Deprecated as of 12/2022. dullweber@chromium.org eokoyomon@chromium.org The interaction performed on the accuracy tip UI. Recorded when UI is closed. Deprecated as of 12/2022. dullweber@chromium.org eokoyomon@chromium.org The amount of time the accuracy tip UI was shown. Recorded when UI is closed. Deprecated as of 12/2022. dullweber@chromium.org eokoyomon@chromium.org The number of accuracy tip dialogs that have been shown to the user. Recorded when UI is closed. Deprecated as of 12/2022. dullweber@chromium.org eokoyomon@chromium.org The accuracy status of a page. Recorded on each page load. sauski@google.com chrome-privacy-controls@google.com Interactions between sync and the cookies clear on exit setting. Only recorded when the user has cookies clear on exit enabled. Recorded on all profiles, including for profiles such as guest profiles that do not allow modification of this setting. (This value logged on those cases is the default value for the setting.) markusheintz@google.com msramek@google.com Logged each time the user grants a consent for a feature integrated with the consent auditor. The value indicates which feature. markusheintz@google.com msramek@google.com Logged each time the user denies or revokes a consent for a feature integrated with the consent auditor. The value indicates which feature. olesiamarukhno@google.com sauski@google.com kmg@google.com How many times the page was refreshed in the last 30 seconds, recorded when third-party party cookies are allowed using cookie controls UI. olesiamarukhno@google.com sauski@google.com kmg@google.com Whether storage access API was granted or blocked for the site, recorded when third-party party cookies are allowed using cookie controls UI. olesiamarukhno@google.com sauski@google.com kmg@google.com Represents if site data was accessed by any third-party sites and if any of those accesses were blocked, recorded when third-party party cookies are allowed using cookie controls UI. olesiamarukhno@google.com sauski@google.com kmg@google.com The site engagement score, recorded when third-party party cookies are allowed using cookie controls UI. dullweber@chromium.org huanzhong@chromium.org Whether third-party cookies are blocked in incognito mode or completely. Recorded at the Profile startup. In case that "Block all cookies" is selected in settings, this metric records BlockThirdParty. This histogram is only recorded {RegularProfileFiltered}. Deprecated in M109. Used to include data from both regular and irregular profiles, such as incognito profiles. Consult the new histograms with the RegularProfile tag instead. alimariam@google.com olesiamarukhno@google.com sauski@google.com Logging actions done by the user while interacting with the "Cookies in use" dialog. arabm@chromium.org dullweber@chromium.org Horizontal metric to show CBD usage across various surfaces. Recorded when the user deletes browsing data from one of these surfaces or when the browser automatically deletes cookies because the user enabled "ClearOnExit". rtarpine@chromium.org src/chrome/browser/dips/OWNERS Whether a {DIPSRedirectType} redirect accessed cookies and whether its origin previously had user engagement. Recorded when redirecting between different sites, {DIPSCookieMode}. In M-109, the DIPS Service was updated to explicitly not collect metrics for non-user profiles, such as system profiles and ChromeOS Signin, LockScreen, and LockScreenApp profiles. wanderview@chromium.org src/chrome/browser/dips/OWNERS The number of sites that may have had their storage cleared by DIPS. If DIPS deletion is on, third-party cookies are blocked, and there are no url-specific exemptions by the user for the latter, then, this is the number of sites that have had storage cleared by DIPS. Otherwise, this number is the sites that would've had their storage cleared if the above conditions were met for all the sites. This is recorded every time the DIPS timer is fired, which is determined by the `timer_delay` parameter of the DIPS feature. This is only logged for site-data clearing that occurs as a result of DIPS. If a site contributes to this count then it has performed a potential tracking action (e.g. writing to storage, bouncing the user, or both) without the user interacting with that site before, or soon after, the action. wanderview@chromium.org src/chrome/browser/dips/OWNERS Number of entries present in the `bounces` table of the user's DIPS database (where there is 1 entry per eTLD+1). For each user profile, reported at profile open (which usually happens at startup). Also reported approximately once every 24 hours thereafter, while the profile remains open and active. If the database is new and therefore empty at startup, such as when a Guest or other OTR profile is opened, a count of 0 will be reported. wanderview@chromium.org src/chrome/browser/dips/OWNERS Errors reported by SQLite while initializing or using the DIPS database. wanderview@chromium.org src/chrome/browser/dips/OWNERS The time taken to gather DIPS database health metrics. For each user profile, these metrics are reported at profile open (which usually happens at startup). They are also reported approximately once every 24 hours thereafter, while the profile remains open and active. Note that Guest and other OTR profiles (e.g. Incognito) will always startup with empty databases, so that may explain why some databases collect health metrics so quickly. wanderview@chromium.org src/chrome/browser/dips/OWNERS Logs how many attempts it took to initialize the DIPS database. Logs a value of 0 if all attempts failed. wanderview@chromium.org src/chrome/browser/dips/OWNERS The size of the DIPS database file. For each user profile, reported at profile open (which usually happens at startup). Also reported approximately once every 24 hours thereafter, while the profile remains open and active. Note that Guest and other OTR profiles (e.g. Incognito) will always startup with empty databases, so that may explain why some database files are very small. wanderview@chromium.org src/chrome/browser/dips/OWNERS The amount of time it takes to complete the DIPS deletion process. This is recorded each time the deletion of DIPS-eligible sites begins. For the case where the deletion is posted to the UI thread, this is the creation time of the StateClearer; otherwise, it is before the call to DIPSStorage::RemoveRows. This metric will be the result of |time when DIPS deletion completed - time when DIPS deletion begins|. njeunje@chromium.org src/chrome/browser/dips/OWNERS This is recorded each time we initiate a possible deletion of state on DIPS-eligible (incidental) sites. This metric will represents the action taken based on multiple conditions gating the actual deletion. This is recorded with {DIPSCookieMode} profiles. wanderview@chromium.org src/chrome/browser/dips/OWNERS Tracks certain errors that DIPS may encounter when running on a client. This is currently recorded when expected invariants are violated, such as there being an open-ended time range in the database. See `DIPSErrorCode` for all possible codes this histogram can output. Since these error codes can be recorded several times by a client, using per-client aggregation when analyzing this metric is recommended. jdh@chromium.org rtarpine@chromium.org src/chrome/browser/dips/OWNERS The amount of time after a user interacts with a site until the site persists state (e.g. cookies), {DIPSCookieMode} (where site = eTLD+1). Not recorded if state is written before interaction takes place (see analogous histogram below). In M-109, the DIPS Service was updated to explicitly not collect metrics for non-user profiles, such as system profiles and ChromeOS Signin, LockScreen, and LockScreenApp profiles. jdh@chromium.org rtarpine@chromium.org src/chrome/browser/dips/OWNERS The amount of time after a navigation to a site commits until a renderer initiated navigation (without user activation) is started to a different site. Not recorded if the redirecting site does not access state (e.g. cookies) or takes longer than 10 seconds to initiate the redirect (bounce). In M-109, the DIPS Service was updated to explicitly not collect metrics for non-user profiles, such as system profiles and ChromeOS Signin, LockScreen, and LockScreenApp profiles. jdh@chromium.org rtarpine@chromium.org src/chrome/browser/dips/OWNERS The amount of time after a site persists state (e.g. cookies) until the user interacts with the site, {DIPSCookieMode} (where site = eTLD+1). Not recorded if interaction takes place before state is written (see analogous histogram above). In M-109, the DIPS Service was updated to explicitly not collect metrics for non-user profiles, such as system profiles and ChromeOS Signin, LockScreen, and LockScreenApp profiles. Logged on profile open, including for profiles such as guest profiles that do not allow modification of this setting. (This value logged on those cases is the default value for the setting.) Replaced in M-110 with the histogram Privacy.DoNotTrackSetting2, which is similar but only emitted on regular profiles. mkwst@chromium.org msramek@chromium.org Whether the Do Not Track setting is enabled. Recorded at the profile open. mkwst@chromium.org msramek@chromium.org Whether the Do Not Track setting is enabled. Recorded at the profile open, only for regular profiles (not Incognito, Guest, etc.). roagarwal@chromium.org eokoyomon@chromium.org fsenra@google.com Tracks interactions with the Quick Delete feature, including the entry points and the dialog. Removed in M96. Replaced by Navigation.MainFrame.ThirdPartyCookieBlockingEnabled. dullweber@chromium.org huanzhong@chromium.org Records whether third party cookie blocking was enabled for a site on page load. Only recorded for users who enabled the cookie controls ui. mkwst@chromium.org msramek@chromium.org dullweber@chromium.org Whether the third party cookie blocking setting is enabled. Recorded at the Profile startup. Previously recorded as the "ThirdPartyCookieBlockingEnabled" and "ThirdPartyCookieBlockingDisabled" actions. This histogram is only recorded {RegularProfileFiltered}. Deprecated in M109. Used to include data from both regular and irregular profiles, such as incognito profiles. Consult the new histograms with the RegularProfile tag instead. alexmt@chromium.org linnan@chromium.org Error info for fetching public keys from the processing server. Recorded for each fetch request. The HTTP response code is recorded if there is no net error code for the request. Replaced with PrivacySandbox.AggregationService.KeyFetcher.Status2, 06/2022. alexmt@chromium.org linnan@chromium.org Records the high level status of each key network fetch request. alexmt@chromium.org linnan@chromium.org Records the high level status of each key network fetch request. alexmt@chromium.org linnan@chromium.org Records the high level status of each aggregatable report assembly request. Recorded for reports requested from any API (e.g. Attribution Reporting API). alexmt@chromium.org linnan@chromium.org Error info for sending an aggregatable report to a reporting endpoint, recorded for every aggregatable report sent. The HTTP response code is recorded if there is no net error code for the request. alexmt@chromium.org linnan@chromium.org Records the high level request status for each aggregatable report being sent to a reporting endpoint. Recorded for reports requested from any API (e.g. Attribution Reporting API). Recorded for every aggregatable report sent. It might retry in case of failure but only the final status will be counted for each report. Replaced with PrivacySandbox.AggregationService.ReportSender.Status, 02/2022. alexmt@chromium.org linnan@chromium.org Records the high level request status of each aggregatable report. These reports are requested by APIs that rely on private, secure aggregation (e.g. Attribution Reporting API). Recorded for every aggregatable report sent. It might retry in case of failure but only the final status will be counted for each report. alexmt@chromium.org linnan@chromium.org Among scheduled report requests that succeeded (eventually), records the number of retries needed, i.e. how many send attempts failed. For example, 2 if the attempts were: fail, fail, success. alexmt@chromium.org linnan@chromium.org Records the final status of a scheduled report request, i.e. whether it succeeded eventually, including after retries (if any). In case of failure, records the type of failure in the final retry attempt. PrivacySandbox.AggregationService.Storage.Sql.CreationTime2 which only records when Threadticks is supported, 10/2022. alexmt@chromium.org linnan@chromium.org Records the time it took to initialize a new aggregation service database from scratch. Recorded when the aggregation service database finishes initialization. Note that 0 is recorded if `ThreadTicks` is not supported. alexmt@chromium.org linnan@chromium.org Records the time it took to initialize a new aggregation service database from scratch. Recorded when the aggregation service database finishes initialization. Note that no event is recorded if `ThreadTicks` is not supported. alexmt@chromium.org linnan@chromium.org Records initialization statuses of AggregationServiceStorageSql. Note: currently AggregationServiceStorageSql is initialized lazily. alexmt@chromium.org linnan@chromium.org Records whether there was sufficient capacity to store the request, i.e. that the per-reporting origin limit had not been reached. Recorded for each StoreRequest attempt. alexmt@chromium.org linnan@chromium.org Records the final status of an *unscheduled* report request, i.e. whether it was successfully sent and, if not, the type of failure. These are typically debug reports. shivanisha@chromium.org xiaochenzh@chromium.org Records the estimated dynamic memory usage by the parsed attestations map. shivanisha@chromium.org xiaochenzh@chromium.org Records the amount of time taken for the downloaded attestations file to be detected from application starts. The measurement ends when `ComponentReady` is invoked with valid inputs. shivanisha@chromium.org xiaochenzh@chromium.org Records the amount of time taken for the downloaded attestations file to be detected from application starts with interruption during startup. For example, if the user has multiple profiles, a profile picker will appear during the startup. This is a non-browser UI that interrupts the startup process. The measurement ends when `ComponentReady` is invoked with valid inputs. shivanisha@chromium.org xiaochenzh@chromium.org Records the amount of time taken for the downloaded attestations file to be detected from first browser window paint. The measurement ends when `ComponentReady` is invoked with valid inputs. shivanisha@chromium.org xiaochenzh@chromium.org Records the amount of time taken to parse the attestations file from disk. The parsing is done on a thread pool thread, not on the main UI thread. The measurement starts from the invocation of the protobuf parsing function and ends when the function returns. Note this metric is recorded only if the parsing succeeds. anthonygarant@chromium.org linan@chromium.org measurement-api-dev+metrics@google.com Records the profile eligibility to cookie deprecation facilitated testing. The metric is only recorded when the client eligibility has not been determined and then the profile eligibility is computed. anthonygarant@chromium.org alexmt@chromium.org measurement-api-dev+metrics@google.com Records the validity of budget entries read from disk. Recorded once every time that budget is attempted to be consumed to reflect the state of stored budget data for the requested origin and API. If multiple errors are found, only the first encountered/detected is reported. As a result, reported errors will be skewed in favor of checks performed first, but we expect multiple instances of corruption for budget entries on disk to be rare. alexmt@chromium.org linnan@chromium.org measurement-api-dev+metrics@google.com Records the number of reporting origins stored per site in budget storage. Recorded once every time that budget is attempted to be consumed to reflect the state of stored budget data for the requested site and API. Not recorded in the case of certain errors that fail before the storage is actually queried. alexmt@chromium.org linnan@chromium.org Records the result of a request to consume budget for the Private Aggregation API. Recorded for each individual aggregatable report request (but not each individual histogram contribution). anthonygarant@chromium.org alexmt@chromium.org Count the number of times the budget storage begins initialization. This metric is intended to be used in conjunction with the "PrivacySandbox.PrivateAggregation.BudgetStorage.ShutdownBeforeFinishingInitialization" metric, which does not measure cases where the browser is shut down abruptly. To get the actual number of times the browser is shut down before finishing initialization, including cases where shut down abruptly, subtract the number of true events for "ShutdownBeforeFinishingInitialization"; from this metric's total count. alexmt@chromium.org linnan@chromium.org Records the initialization statuses of PrivateAggregationBudgetStorage, indicating whether it was successful and, if not, why it failed. Recorded when the initialization reply callback is run on the main sequence. alexmt@chromium.org linnan@chromium.org Records whether PrivateAggregationBudgetStorage has already been shut down when the initialization finishes (i.e. the reply callback is run on the main sequence). Recorded when that callback is run. alexmt@chromium.org linnan@chromium.org On browser or profile shutdown, records the length of time that each mojo pipe still open has been open for. Recorded for every mojo pipe that is still open during shutdown. This is intended to provide a signal if mojo pipes are not being closed. alexmt@chromium.org linnan@chromium.org Records whether a PrivateAggregationHost mojo pipe successfully resulted in a report request being forwarded to the manager and, if not, the reason for failure or no report. Further, breaks out the case of too many contributions, where the request is forwarded but is truncated. Note that, even if successfully forwarded, the report may still be rejected by the budgeter, manager or in the aggregation_service layer. Recorded for every mojo pipe on disconnection. alexmt@chromium.org linnan@chromium.org Some PrivateAggregation operations have an associated timeout after which a report will be sent unconditionally. This metric records, for every mojo pipe which specifies a timeout, the outcome of the timeout. Recorded at the timeout or disconnection time whichever occurs first, or when it's canceled due to error, or on browser shutdown if it's still scheduled with pipe open. alexmt@chromium.org linnan@chromium.org measurement-api-dev+metrics@google.com Records the outcome of a report request sent through the Private Aggregation manager, i.e. whether the report was sent and whether its contributions were cleared due to budget denial. Also breaks out the case of a report that started with no contributions. Recorded for each individual report request (but not each individual histogram contribution). linnan@chromium.org johnidel@chromium.org sauski@chromium.org Whether or not the {ApiType} operation was allowed by Privacy Sandbox settings and why. Recorded at the time settings are checked when performing the operation.