harrisonsean@chromium.org chrome-privacy-controls@google.com The state of the advanced spellcheck setting, recorded on profile open for regular profiles (not Incognito, Guest, etc.). Expired in M109, re-instated in M118. zalmashni@google.com rainhard@chromium.org chrome-browser-privacy-team@google.com Captures the user interaction with all elements in AI Compose settings page. zalmashni@google.com rainhard@chromium.org chrome-browser-privacy-team@google.com Captures whether the entry point for the {FeatureName} in AI settings page is shown to the user. The metric is recorded when the user navigates to 'chrome://settings/ai'. zalmashni@google.com rainhard@chromium.org chrome-browser-privacy-team@google.com Captures the user interaction with all elements in AI History Search settings page. zalmashni@google.com rainhard@chromium.org chrome-browser-privacy-team@google.com Captures the user interaction with all entrypoints in AI settings page. sophiechang@google.com iwells@chromium.org Captures the user interaction with all elements in AI Suggestions settings page. harrisonsean@chromium.org chrome-privacy-controls@google.com The state of the autocomplete searches setting, recorded on profile open, only for regular profiles (not Incognito, Guest, etc.). rainhard@chromium.org msramek@chromium.org chrome-browser-privacy-team@google.com Records the time period that users cleared from the Clear Browsing Data dialog. Note: The `Advanced` refers to the Advanced tab in Clear Browsing Data, which has become the only available tab after DBD dialog revamp (crbug.com/502885275). gayane@google.com bling-mony-pod@google.com The source surface that requested displaying the default browser system settings. Logged when the user actually opens the iOS system settings (IOS only). alimariam@google.com olesiamarukhno@google.com sauski@google.com Records either the state of first party sets (FPS) or not relevant, depending on the user's cookie settings. This is logged on startup. dullweber@chromium.org chrome-browser-privacy-team@google.com Records the classname of a Fragment when it is attached to a SettingsActivity. For evaluating popularity and priorities for Android settings GUI. The name is hashed using String.hashCode. Notes: SingleCategorySettings powers all permission related pages in SiteSettings (e.g. Location, Camera, ...). For Desktop settings usage check WebUI.Settings.PathVisited. mpearson@chromium.org twellington@chromium.org Whether or not the home page user preference is set to the default NTP value when a regular profile is loaded. This is only logged if the home button is shown. To be explicit: not logged when an Incognito profile is opened because that inherits the settings from its parent profile. As such, it's not necessary to log the Incognito profile's settings. dominicaustria@google.com dpenning@chromium.org Logs whether the glass frame setting is enabled or disabled when it is toggled in chrome://settings/appearance. Record for mac only. jthiesen@chromium.org twellington@chromium.org wenyufu@chromium.org The status of the home button, whether turned on or off, and by who. Is affected by several homepage related policies, as well as user and potentially partner actions. Recorded on deferred startup. Android only. bttk@chromium.org twellington@chromium.org wenyufu@chromium.org The location type for the homepage if the homepage is enabled. Recorded on deferred startup iff the homepage is enabled. Android only. mpearson@chromium.org csharp@chromium.org Tries to pretend the home page URL is a search URL, and records the search engine type of that URL by comparing the TLD+1 of the home page URL with those of the different known search engines. Recorded when a regular profile is opened, if a home page URL has been set. Note that at least one profile is opened on startup. To be explicit: not logged when an Incognito profile is opened because that inherits the settings from its parent profile. As such, it's not necessary to log the Incognito profile's settings. charlesmeng@chromium.org estalin@chromium.org Logged whether the hover card preview images setting is enabled or disabled when it is toggled in chrome://settings/appearance. dominicaustria@chromium.org emshack@chromium.org Logged whether the hover card memory usage bar is enabled or disabled when it is toggled in chrome://settings/appearance. Record for desktop only. hidehiko@chromium.org nya@chromium.org Records the classname of a Fragment when it is attached to a SettingsActivity but not implements SettingsFragment interface. The name is hashed using String.hashCode. All fragment attached to SettingsActivity should implement SettingsFragment and this helps to identify missing ones. adelm@google.com jinsukkim@chromium.org User opened settings UI. Recorded when the main Settings preference fragment is opened via 3-dot menu. Android only. roagarwal@chromium.org chrome-incognito@google.com Records the profile type for opening the Settings page from menu. charlesmeng@chromium.org estalin@chromium.org Logs whether the overscroll history navigation setting is enabled or disabled when it is toggled in chrome://settings/accessibility. Compare to the histogram "ChromeOS.Settings.OverscrollHistoryNavigation.Enabled" on Chrome OS. antrim@chromium.org teresachow@google.com cros-lurs@google.com The users progress through the pin unlock setup wizard. Each type corresponds to the user completing a different stage of the setup wizard. Warning: this histogram was expired from 2025-08-31 to 2025-11-25; data may be missing. rainhard@chromium.org msramek@chromium.org chrome-browser-privacy-team@google.com The status of the preload setting, recorded on regular profile open (not Incognito, Guest, etc.). Not recorded for iOS where the setting does not exist. harrisonsean@chromium.org msramek@chromium.org sauski@chromium.org chrome-browser-privacy-team@google.com Which privacy related settings elements a user interacted with. Recorded every time a user interacts with an element of interest. harrisonsean@chromium.org rainhard@chromium.org chrome-browser-privacy-team@google.com How the users navigated into the Privacy guide as well as links out of the privacy guide. rainhard@chromium.org aisulu@google.com chrome-browser-privacy-team@google.com The number of settings steps that can be shown in the Privacy Guide flow. This number varies based on the users' setting states. Recorded when the user clicks 'Next' in the Privacy Guide welcome card. harrisonsean@chromium.org rainhard@chromium.org chrome-browser-privacy-team@google.com The step in the Privacy guide from which a user clicked the 'next' button. harrisonsean@chromium.org rainhard@chromium.org chrome-browser-privacy-team@google.com Records whether or not the user kept the same settings or changed it, and the corresponding value, on every |Next| or |Back| button click inside of Privacy guide. rainhard@chromium.org aisulu@google.com chrome-browser-privacy-team@google.com Records which steps were set to be eligible to be shown when user clicks 'Next' button in the Welcome step. Records which steps were reached when user reaches the individual step in the flow. rainhard@chromium.org msramek@chromium.org anaudrey@chromium.org chrome-browser-privacy-team@google.com Which user actions were taken in safety check. Recorded every time a user does an interaction in safety check. Value 5 and 6 got added with M86, 7-9 with M87, 10 with M88, and 11 with M89. rainhard@chromium.org msramek@chromium.org Resulting state of the safety check password check. Replaced Settings.SafetyCheck.PasswordsResult in M116 after fixing a bug on Safety Check on iOS that was recording password results multiple times for the same password check. andzaytsev@google.com msramek@chromium.org Resulting state of the safety check Safe Browsing check. sideyilmaz@chromium.org msramek@chromium.org The number of days between the revocation of the permissions for an unused site and when the user reverts this revocation through the unused site permissions module of safety check in Chrome settings. Emitted when the user clicks regrants permissions through the permissions review interface in Chrome settings. alimariam@google.com sideyilmaz@chromium.org msramek@chromium.org The number of the failed type which could not be migrated to the SafetyCheck new unused site permissions module with string name IDs. Recorded on profile startup if the integer value ID in prefs doesn't match any ContentSettingsType. sideyilmaz@chromium.org msramek@chromium.org chrome-browser-privacy-team@google.com The user actions taken on the unused site permissions module in safety check in Chrome settings. Recorded every time the user interacts with the respective UI element. sideyilmaz@chromium.org tov@chromium.org msramek@chromium.org Captures the number of days since the permission was revoked for any permission type, up until the cleanup threshold for revoked permissions has been reached. The metric is recorded when the user regrants a permission that was previously revoked by the unused site permission module of SafetyCheck. sideyilmaz@chromium.org tov@chromium.org msramek@chromium.org Captures the number of days since the permission was revoked for the {PermissionType} permission type, up until the cleanup threshold for revoked permissions has been reached. The metric is recorded when the user regrants a permission that was previously revoked by the unused site permission module of SafetyCheck. andzaytsev@google.com msramek@chromium.org Resulting state of the safety check updates check. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com The number of times the blocklist was checked when running the abusive notification revocation feature in the revoked permissions module of the Safety Hub. Recorded during the auto-revocation run. thefrog@chromium.org chrome-counter-abuse-alerts@google.com Records the result of the Safe Browsing social engineering blocklist check for abusive notification permissions in Safety Hub. Logged each time a URL check completes (safe, phishing, or timeout). skrakowi@chromium.org chrome-counter-abuse-alerts@google.com The user actions taken on revoked abusive notifications in the revoked permissions module of the Safety Hub page in settings. Recorded every time the user interacts with the respective UI element for abusive notifications - this does not include interactions with revoked unused permissions. skrakowi@chromium.org chrome-counter-abuse-alerts@google.com Recorded when the user changes notification permission outside of Safety Hub for sites previously {RevokedStatus} due to abusive notification with reason {NotificationRevocationSource}. This detects occurrence of false positive abusive auto-revocations. zalmashni@google.com chrome-browser-privacy-team@google.com Captures the state of the unused site permissions auto-revocation pref. Recorded when the user changes the preference via the toggle on the Site Settings page. fsenra@google.com chrome-browser-privacy-team@google.com Captures whether auto-revocation is enabled for unused site permissions. Recorded when the SafetyHubFetchService is created on browser start up. Android-only. zalmashni@google.com chrome-browser-privacy-team@google.com Captures actions taken on the Safety Hub dashboard, except those taken on the notifications review and revoked permissions module. Emitted for all relevant click events on the Safety Hub dashboard. sideyilmaz@chromium.org chrome-browser-privacy-team@google.com Captures the impressions of the different modules that have some warnings in Safety Check page. Recorded whenever Safety Check page is loaded. olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Records the site engagement for revoked disruptive notification sites. Recorded on every run of the disruptive notification sites Safety Hub check. olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Records the number of days since revocation for revoked disruptive notification sites, and their current state and site engagement. Recorded on every run of the disruptive notification sites Safety Hub check. For proposed revocation, days are computed since the proposal. olesiamarukhnno@google.com antoniosartori@chromium.org Tracks the distribution of the average daily notification volume for detected false positive sites that were previously marked for revocation of disruptive notifications. The metric is only reported if all false positive conditions are satified (the interaction happened within min, max days since the revocation, site engagement score has increased by min delta). olesiamarukhnno@google.com antoniosartori@chromium.org Tracks the distribution of the days since proposed revocation for detected false positive sites that were previously marked for revocation of disruptive notifications. The metric is only reported if all false positive conditions are satified (the interaction happened within min, max days since the revocation, site engagement score has increased by min delta). olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Tracks the distribution of the number of notification clicks that occured during the cooldown period for detected false positive sites that were previously marked for revocation of disruptive notifications. The metric is only reported if all false positive conditions are satified (the interaction happened within min, max days since the revocation, site engagement score has increased by min delta). olesiamarukhnno@google.com antoniosartori@chromium.org Tracks the distribution of the number of page visits that occured during the cooldown period for detected false positive sites that were previously marked for revocation of disruptive notifications. The metric is only reported if all false positive conditions are satified (the interaction happened within min, max days since the revocation, site engagement score has increased by min delta). olesiamarukhnno@google.com antoniosartori@chromium.org Tracks the distribution of the site engagement score for detected false positive sites that were previously marked for revocation of disruptive notifications. The metric is only reported if all false positive conditions are satified (the interaction happened within min, max days since the revocation, site engagement score has increased by min delta). olesiamarukhnno@google.com antoniosartori@chromium.org Tracks how often a disruptive notification is revoked without reporting a proposed disruptive notification UKM beforehand. The UKM can only be reported on a notification interaction or a page visit. The revocation is delayed to report the proposed metric when a notification is shown. After the cooldown runs out, the revocation will happen even without reporting metrics. olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Tracks the distribution of the days since proposed revocation for sites that were previously marked for revocation of disruptive notifications but are not classified as disruptive anymore (due to site engagement score increase or decline in the daily average notification count). olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Tracks the distribution of the new daily average notification count (over the last 7 days) for sites that were previously marked for revocation of disruptive notifications but are not classified as disruptive anymore, due to the notification count decrease. olesiamarukhnno@google.com antoniosartori@chromium.org Tracks the distribution of the new site engagement score for sites that were previously marked for revocation of disruptive notifications but are not classified as disruptive anymore, due to the site engagement score increase. olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Tracks the distribution of the average daily notification count for proposed revocation of disruptive notifications. olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Tracks results of the disruptive notification feature. Recorded every time the safety hub check runs (once a day). The metric is recorded per each notification content setting. It indicates whether the notification should be revoked, or the reason why it shouldn't be revoked. olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Tracks how many days has passed since a disruptive notification revocation was proposed to when it was actually revoked. The delay is caused by waiting for metrics to be reported when a notification for a site is shown. olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Records the number of revoked disruptive notification sites per a Safety Hub run. Note that this are actually proposed revocations, which will potentially become effective only in successive runs. olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Recorded when users regrant notification permissions after a disruptive notification revocation. Measures how many days passed since the proposed revocation. olesiamarukhnno@google.com antoniosartori@chromium.org Recorded when users regrant notification permissions after a disruptive notification revocation. Measures how many days passed since the proposed revocation. olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Recorded when users regrant notification permissions after a disruptive notification revocation. Reports the average daily notification count when the revocation was proposed. olesiamarukhnno@google.com antoniosartori@chromium.org chrome-browser-privacy-team@google.com Tracks the distribution of the interactions with sites that were previously marked for revocation of disruptive notifications. The metric is reported when the interaction with the site occurs. sideyilmaz@chromium.org tov@chromium.org msramek@chromium.org chrome-browser-privacy-team@google.com Captures the impressions of the different entry points of Safety Hub. sideyilmaz@chromium.org tov@chromium.org msramek@chromium.org Captures the interaction with an entry point of Safety Hub, that will eventually lead to the Safety Check page, password manager checkup page or the extensions page. zalmashni@google.com chrome-browser-privacy-team@google.com Captures the interaction with an entry point of Safety Hub. Emitted when the user click on the entry point. sideyilmaz@chromium.org chrome-privacy-controls@google.com Captures whether the Safety Check dashboard has any warning. Recorded whenever Safety Check page is loaded. sideyilmaz@chromium.org tov@chromium.org msramek@chromium.org Captures Safety Hub page visits and three dot menu impressions for any Safety Hub module. sideyilmaz@chromium.org tov@chromium.org msramek@chromium.org chrome-browser-privacy-team@google.com Captures Safety Hub page visits and three dot menu clicks for any Safety Hub module. fsenra@google.com chrome-browser-privacy-team@google.com Captures the user preference for whether the Safety Hub Magic Stack module is enabled. Recorded when the SafetyHubMagicStackBuilder is created on browser start up. Android-only. sideyilmaz@chromium.org tov@chromium.org msramek@chromium.org Captures the Safety Hub module of which the three-dot menu notification was clicked. sideyilmaz@chromium.org tov@chromium.org msramek@chromium.org Captures the Safety Hub module for which a notification was shown in the three-dot menu. sideyilmaz@chromium.org aisulu@google.com chrome-privacy-controls@google.com The user actions taken on the notification permissions module in Safety Check page in settings. Recorded every time the user interacts with the respective UI element. sideyilmaz@chromium.org aisulu@google.com chrome-privacy-controls@google.com The number of notification permissions suggested to be removed. Recorded when Safety Check page in Settings is opened. sideyilmaz@chromium.org aisulu@google.com chrome-browser-privacy-team@google.com Passwords Card is located on Safety Check page in settings and can be in one of the multiple states. This is the Passwords Card state recorded on click. sideyilmaz@chromium.org aisulu@google.com chrome-browser-privacy-team@google.com Safe Browsing Card is located on Safety Check page in settings and can be in one of the multiple states. This is the Safe Browsing Card state recorded on click. sideyilmaz@chromium.org aisulu@google.com chrome-browser-privacy-team@google.com The type of permission auto-revoked by the unused site permissions module of Safety Hub. Recorded during the auto-revocation run. Updated to use the default content settings enum in M128. aisulu@google.com fsenra@google.com chrome-browser-privacy-team@google.com Records on startup whether the user previously went through backfill or not. The backfill here is a process of adding `last_visited` timestamp to all granted permissions of the user that do not have it yet. aisulu@google.com fsenra@google.com chrome-browser-privacy-team@google.com The number of permissions that a successfull backfill run timestamped with `last_visited` field. aisulu@google.com fsenra@google.com chrome-browser-privacy-team@google.com Records whenever the backfill was started or completed. The backfill here adds `last_visited` timestamp to all granted permissions of the user that do not have it yet. sideyilmaz@chromium.org aisulu@google.com chrome-browser-privacy-team@google.com The user actions taken on the unused site permissions module in Safety Check page in settings. Recorded every time the user interacts with the respective UI element. sideyilmaz@chromium.org aisulu@google.com chrome-browser-privacy-team@google.com The number of unused site permissions suggested to be removed. Recorded when Safety Check page in Settings is opened. sideyilmaz@chromium.org aisulu@google.com chrome-browser-privacy-team@google.com Version Card is located on Safety Check page in settings and can be in one of the multiple states. This is the Version Card state recorded on click. zalmashni@google.com chrome-browser-privacy-team@google.com Captures the state of Safety Hub dashboard modules on impression or exit. adelm@google.com jinsukkim@chromium.org How search in settings was used i.e. user clicked the search results, abandoned them without clicking, or abandoned due to getting no results at all, etc. Recorded when users does something to the results after receiving them or when user invokes OS back to go back to the search results and do something again. Also recorded when search UI/Settings Activity is exited. Android only. adelm@google.com jinsukkim@chromium.org User entered the search in settings. Recorded when the user clicks the search box UI. Android only. adelm@google.com jinsukkim@chromium.org Same as Settings.Search.UiOpened, but recorded only once since the user opens Settings. Android only. alsan@chromium.org chrome-desktop-ui-waterloo@google.com Records the number of times a Google Search icon was loaded for a non-Google search engine on the settings page. The boolean value indicates whether the search engine is the current default. yoangela@chromium.org amelies@google.com chrome-omnibox-team@google.com Which Search Engines and Search settings page elements a user interacted with (e.g. section expand/collapse, subpage navigation, and engine editing). Recorded every time a user interacts with an element of interest. Buckets 4-13 were added in M150. bcl@google.com chrome-omnibox-team@google.com Records whether the Safe Browsing traffic-based search hijacking heuristic had been calculated whenever a user visits chrome://settings/search. As of M149, this only expected to be true for Enhanced Safe Browsing users who run extension telemetry, and may still be false for ESB users if the detector hasn't yet had opportunity and sufficent data to run. Recorded once each time chrome://settings/search is loaded. bcl@google.com chrome-omnibox-team@google.com Records whether the Safe Browsing traffic-based search hijacking heuristic matched in the last 7 days. Recorded once each time chrome://settings/search page is loaded, if and only if the heuristic is available. adelm@google.com jinsukkim@chromium.org The amount of time in ms the user spent in the Settings menu. Recorded when user quits Settings Activity. A session lasts across the activities being exited and re-created due to configuration change or memory pressure, till the user actually quits the Settings. Only the Activity started for the main settings is considered, and those starting sub-settings are ignored. Android only. pmonette@chromium.org robliao@chromium.org The user clicked "Make Google Chrome the default browser" on the settings page. mpearson@chromium.org wfh@chromium.org Tries to pretend the startup page URLs are search URLs, and records the search engine types of those URLs by comparing the TLD+1s of the URLs with those of the different known search engines. Recorded when a regular profile is opened, if startup page URLs have been set. Note that at least one profile is opened on startup. To be explicit: not logged when an Incognito profile is opened because that inherits the settings from its parent profile. As such, it's not necessary to log the Incognito profile's settings. mpearson@chromium.org tiborg@chromium.org chrome-desktop-ntp@google.com The startup page settings when a regular profile is loaded. To be explicit: not logged when an Incognito profile is opened because that inherits the settings from its parent profile. As such, it's not necessary to log the Incognito profile's settings. zackhan@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference whose value has been changed since the last time Chrome set it. This histogram is emitted after a validation check using the encrypted hash stored in the JSON pref files. zackhan@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference whose value has been changed since the last time Chrome set it. Only emitted if the encrypted hash verification is not available causing the verification to fallback to HMAC-based verification. zackhan@chromium.org anunoy@chromium.org junhao.huang@microsoft.com The id of a tracked preference whose value has been changed since the last time Chrome set it. Without a suffix, this histogram stands for preference validation using MACs in the JSON pref files. {TrackedPreferencesExternalValidators} zackhan@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference whose value has been cleared since the last time Chrome set it. This histogram is emitted after a validation check using the encrypted hash stored in the JSON pref files. zackhan@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference whose value has been cleared since the last time Chrome set it. Only emitted if the encrypted hash verification is not available causing the verification to fallback to HMAC-based verification. zackhan@chromium.org anunoy@chromium.org junhao.huang@microsoft.com The id of a tracked preference whose value has been cleared since the last time Chrome set it. Without a suffix, this histogram stands for preference validation using MACs in the JSON pref files. Warning: This histogram was expired from 2022-12 to 2025-03; data may be missing. {TrackedPreferencesExternalValidators} zackhan@chromium.org anunoy@chromium.org junhao.huang@microsoft.com The id of a tracked preference whose last value isn't known. We may be just starting to track the preference, or local state may have been changed outside of Chrome. This should only happen once per pref per profile. Without a suffix, this histogram stands for preference validation using MACs in the JSON pref files. Warning: This histogram was expired from 2022-12 to 2025-03; data may be missing. {TrackedPreferencesExternalValidators} zackhan@chromium.org anunoy@chromium.org junhao.huang@microsoft.com The id of a tracked preference which was initialized despite the absence of a MAC as its value was NULL. Without a suffix, this histogram stands for preference validation using MACs in the JSON pref files. Warning: This histogram was expired from 2022-12 to 2025-03; data may be missing. {TrackedPreferencesExternalValidators} zackhan@chromium.org anunoy@chromium.org junhao.huang@microsoft.com The id of a tracked preference which was reset by Chrome. zackhan@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference which was reset by Chrome via the encrypted hash verification. zackhan@google.com chrome-counter-abuse-alerts@google.com The number of preferences that were reset by the TrackedPreference validation system during startup. This is recorded when the PrefHashFilter is initialized. zackhan@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference which was reset by Chrome via the old HMAC fallback verification. Only emitted if the encrypted hash verification is not available causing the verification to fallback to HMAC-based verification. zackhan@chromium.org chrome-counter-abuse-alerts@google.com Records the TrackedPreference ID of a preference that had a type mismatch between the registered type ({RegisteredType}) and the loaded type ({LoadedType}). zackhan@chromium.org wfh@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference which was determined during decryption to be using a weak algorithm, and was thus treated as invalid. zackhan@chromium.org chrome-counter-abuse-alerts@google.com The result of verifying the file-level SuperEncryptedHash during preference load. zackhan@chromium.org anunoy@chromium.org junhao.huang@microsoft.com The id of a tracked preference which was initialized despite the absence of a MAC as the current MACs are trusted, inferring that this is a newly tracked pref. Without a suffix, this histogram stands for preference validation using MACs in the JSON pref files. Warning: This histogram was expired from 2022-12 to 2025-03; data may be missing. {TrackedPreferencesExternalValidators} zackhan@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference whose value has not changed since the last time Chrome set it. This histogram is emitted after preference validation using the encrypted hash stored in the JSON pref files. zackhan@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference whose value has not changed since the last time Chrome set it. Only emitted if the encrypted hash verification is not available causing the verification to fallback to HMAC-based verification. zackhan@chromium.org anunoy@chromium.org junhao.huang@microsoft.com The id of a tracked preference whose value has not changed since the last time Chrome set it. Without a suffix, this histogram stands for preference validation using MACs in the JSON pref files. Warning: This histogram was expired from 2022-12 to 2025-03; data may be missing. {TrackedPreferencesExternalValidators} zackhan@chromium.org anunoy@chromium.org junhao.huang@microsoft.com The id of a tracked preference which Chrome would have reset had the config allowed it. zackhan@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference which Chrome would have reset via the encrypted hash reset flow had the config allowed it. zackhan@chromium.org chrome-counter-abuse-alerts@google.com The id of a tracked preference which Chrome would have reset via the old HMAC fallback reset flow had the config allowed it. Only emitted if the encrypted hash verification is not available causing the verification to fallback to HMAC-based verification.