juanmojica@google.com schechter@google.com stanfield@google.com lens-chrome-eng@google.com Records ambient search queries enumerated by the entry point used to make the query. This is recorded every time the user makes a query regardless of whether the query succeeds. hanxi@chromium.org ender@google.com clank-start@google.com Records whether a favicon is fetched successfully. The histogram is logged when Chrome is paused and a favicon is fetched for a Tab for the auxiliary search. Android-only. hanxi@chromium.org clank-start@google.com Records the number of entries returned from fetching history database which was initiated by a Custom Tab for auxiliary search. The histogram is logged when the Custom Tab is paused and the fetching from history database is completed. Android-only. ender@google.com chrome-mobile-search@google.com Time taken for deleting contents from the auxiliary search. ender@google.com chrome-mobile-search@google.com Records the count of failed deletions from the auxiliary search. ender@google.com chrome-mobile-search@google.com Records the status of the request of the Auxiliary Search content deletion. Recorded twice for every deletion request: once to capture the request sent, and once to capture the consumer's response. ender@google.com chrome-mobile-search@google.com Time taken for donating contents to the auxiliary search. hanxi@chromium.org ender@google.com clank-start@google.com Records the count of contents which are sent to the auxiliary search. The histogram is logged when Chrome is paused and a set of data are donated to the auxiliary search. Android-only. ender@google.com chrome-mobile-search@google.com Records the count of failed donations from the auxiliary search. ender@google.com chrome-mobile-search@google.com Records the status of the request of the Auxiliary Search content donation. Recorded twice for every donation request: once to capture the request sent, and once to capture the consumer's response. hanxi@chromium.org ender@google.com clank-start@google.com Records the total count of the available favicons for the first donation. The histogram is logged when Chrome is paused and a small set of favicon fetching is completed for the auxiliary search. Android-only. hanxi@chromium.org ender@google.com clank-start@google.com Records the type and the position of a donated data when it is clicked by users from the external app. The histogram is logged when Chrome is launched via an View Intent from the external app. Android only. hanxi@chromium.org ender@google.com clank-start@google.com Records the type of the button that the user clicked on the auxiliary search module which is shown on the magic stack. The histogram is logged when the user clicks a button on the module. Android-only. hanxi@chromium.org ender@google.com clank-start@google.com Records the time taken for query contents for the auxiliary search. The histogram is logged when Chrome is on paused and the query of a set of data is completed for the auxiliary search. Android only. hanxi@chromium.org ender@google.com clank-start@google.com Records the duration between a background task is created and executed for tab donation. The histogram is logged when the background task is started, Android-only. hanxi@chromium.org ender@google.com clank-start@google.com Records the time taken between all of the favicons are fetched and the donation to the auxiliary search is completed. The histogram is logged when the donation is completed from a scheduled background task. Android-only. hanxi@chromium.org ender@google.com clank-start@google.com Records the number of favicons that a background task donated for auxiliary search. The histogram is logged when all of the favicons are fetched. Android-only. hanxi@chromium.org ender@google.com clank-start@google.com Time taken for fetching up to 100 favicons for the auxiliary search from a scheduled background task. The histogram is logged when all of the favicons are fetched. Android-only. hanxi@chromium.org ender@google.com clank-start@google.com Records the result of a background task for tab donation. The histogram is logged when a donation is completed, or when all of the favicon fetches are completed but there isn't any favicon available. Android-only. hanxi@chromium.org ender@google.com clank-start@google.com Records the whether the sharing Tabs with OS config is enabled. The histogram is logged when the user changes the config on Tabs settings. Android-only. hanxi@chromium.org clank-start@google.com Records the time from CustomTabActivity is created until the AuxiliarySearchController is created in the deferred startup. The histogram is logged when the AuxiliarySearchController is created in the CustomTabActivity. Android-only. hanxi@chromium.org ender@google.com clank-start@google.com Records the expiration duration of the lastest fetch results of the most visited sites. The histogram is logged when Chrome is paused and a set of documents are built to donate for the auxiliary search. Android-only. dgn@google.com tju@google.com chrome-regionalcapabilities@google.com Recorded on each profile load (tied to service construction), indicates the last engine choice timestamp formatted as YYYYMM integer. For convenience, the enum maps these to user readable `YYYY-MM` labels. To avoid the histogram exceeding 1000 buckets (limit for sparse histograms), the range is capped to [`2022-01`, `2050-12`], dates prior to 2022 being recorded as `1000-01`, and dates after 2050 being recorded as `3000-01`. The value is serialized as a sparse histogram with integer values. Since each client can record the same value multiple times, it might be more interesting to look at unique clients. {Profile} dgn@google.com chrome-regionalcapabilities@google.com Recorded on Android whenever a new Play API search engine is set (e.g., via the EEA Choice Screen). Records the total count of pre-existing regulatory program tagged search engines (Android EEA) found in the TemplateURLService's loaded engines list and removed prior to adding the new engine. Identifies how many stale regulatory entries were accumulated and successfully cleaned up. dgn@chromium.org chrome-regionalcapabilities@google.com Records the outcome of attempting to propagate the search engine choice data from an existing profile to a newly created one. Recorded each time a profile forks or creates a new profile while capturing preferences. dgn@chromium.org chrome-regionalcapabilities@google.com Records an enum that represents the search engine choice page scroll state when the "More" button is clicked. In some cases, the page doesn't scroll to the exact bottom when the button is clicked. Recorded only when the "More" button is clicked. dgn@chromium.org chrome-regionalcapabilities@google.com At the moment re-entry into MaybeRecordChoiceScreenDisplayState from user choice moment is detected, records whether we already have valid completion metadata written stored in prefs. This is intended to monitor the ongoing prevalence of https://crbug.com/390272573, to allow detection if the rate increases significantly. dgn@chromium.org chrome-regionalcapabilities@google.com When the "static" choice screen eligibility is evaluated at profile load time, only a subset of the choice screen status count towards ineligibility. This histogram is added to monitor the ignored conditions for which we consider the profile "eligible", but that would count as "ineligible" when checked at triggering time. Recorded at profile load, for a subset of the statuses leading to reporting "Eligible" to the "RegionalCapabilities.FunnelStage.Eligibility" histogram. cschlosser@chromium.org chromeos-privacyhub@google.com chrome-regionalcapabilities@google.com Records if the pref storing the current country ID of the device is invalid. Through some code paths it's possible that a placeholder value could be persisted in the prefs. Earlier there were less checks in place for valid country IDs which makes it possible that old profiles still have the invalid values stored in prefs. As the prefs take precedence over other mechanisms when determining the country for the device an invalid value can lead to the actual country not being assigned correctly. This histogram is emitted when trying to read the pref for the profile and iff the pref exists. dgn@chromium.org chrome-regionalcapabilities@google.com Records the outcome of attempting to upload the pending choice screen display state metrics. The display state data is cached when there is a country or program mismatch at the moment the search engine choice is completed (see "Search.ChoiceScreenShowedEngineAt.CountryMismatch"). Recorded on profile load. Until a terminal state is reached and for a fixed duration after the choice is made, Chrome will re-check on each profile load whether we still are in mismatch, and submit the "Search.ChoiceScreenShowedEngineAt.Index*" histograms if not. Once the data is recorded, the profile should not log this histogram again. Is it also not logged when the histograms can be emitted at the choice moment. dgn@chromium.org chrome-regionalcapabilities@google.com Records whether the search engine choice preferences would be wiped due to the missing default search engine pref. Checked on profile load, and recorded when we both have choice metadata and no default search engine pref. The recorded value indicates whether the feature to wipe this value is enabled. droger@chromium.org chrome-regionalcapabilities@google.com Records the outcome of the search engine reprompt check, when the profile is opened, based on remote experiment parameters. Reported for {Category}. dgn@chromium.org chrome-regionalcapabilities@google.com Records the type of the default search engine that was chosen by the user. Recorded the first time a user in the EEA region changes their default search engine in the search engine choice screen. Unlike Search.ChoiceScreenDefaultSearchEngineType, it does not record choices made in the settings page. The enum is shared with Search.DefaultSearchProviderType2. {Profile} dgn@chromium.org chrome-regionalcapabilities@google.com Records the type of the default search engine that was chosen by the user. Recorded the first time a user in the EEA region changes their default search engine in the search engine choice screen or in the settings page. The enum is shared with Search.DefaultSearchProviderType2. {Profile} dgn@chromium.org samarchehade@chromium.org chrome-regionalcapabilities@google.com Records that the search engine choice screen was displayed, and whether this happened as part of the FRE. Also records when the user clicks/taps the 'Set as Default' button and if this selection was in the FRE or not. On Desktop, if the choice screen is shown simultaneously in multiple browsers that all have the same profile, the display event is only recorded once. {Context} {Profile} dgn@chromium.org ljjlee@chromium.org chrome-regionalcapabilities@google.com Records the conditon state at page navigation for whether to display the search engine choice screen. This is recorded every time the eligibility state is being checked, which might be as often as every page navigation. The enum is shared with ChoiceScreenProfileInitConditions, and individual enum members might appear in only one histogram. {Context} {Profile} dgn@chromium.org ljjlee@chromium.org chrome-regionalcapabilities@google.com Records the conditon state at profile initialization for displaying the search engine choice screen that the profile is in. The enum is shared with ChoiceScreenNavigationConditions, and individual enum members might appear in only one histogram. {Context} {Profile} dgn@chromium.org chrome-regionalcapabilities@google.com Records the index among the options listed on the choice screen for the search engine that was chosen by the user. Gets recorded when a search engine choice is made on the choice screen. dgn@chromium.org chrome-regionalcapabilities@google.com Records whether Search.ChoiceScreenShowedEngineAt.Index{Index} had to be skipped due to a mismatch between the Variations/UMA country and the profile/choice country. If there is a mismatch, `true` ("Skipped") is recorded, `false` ("Not Skipped") otherwise. dgn@chromium.org chrome-regionalcapabilities@google.com With its other per-index variants, records information about the positions of all search engines on the choice screen. Specifically, this one records that a given search engine was shown at index {Index} of the choice screen. This set of histograms is recorded at the moment a choice is made, which is expected to happen at most once per profile. To avoid adversely impacting pseudonymity property of UMA logs, this will not be logged if the country associated with the current metrics session does not match the country used to determine the list of options to show on the screen. This metric is inteded to be consumed via raw histogram analysis instead of via the UMA dashboard. See http://go/chrome-choice-screen-positions-histogram-design for more info. {Profile} droger@chromium.org chrome-regionalcapabilities@google.com Records the reason for wiping the search engine choice preferences, forcing a reprompt at the next startup. Recorded every time the wiping occurs. ender@google.com chrome-analysis-team@google.com chrome-mobile-search@google.com Records whether the user opened the panel when it was shown. Recorded for all gestures for all users when the UX is hidden. Implemented for Android. The user action Search.ContextualSearch.All.ResultsSeen.true is also logged in the case that true is logged to this histogram. This histogram is of special interest to the chrome-analysis-team@. Do not change its semantics or retire it without talking to them first. ender@google.com related-searches-vteam@google.com chrome-mobile-search@google.com Records that a Search Result page was shown in a bottom sheet for either Contextual Search or Related Searches. Each entry corresponds to exactly one search of the indicated kind. Related Searches are recorded when the SERP is shown to the user, and Contextual Searches are recorded when the panel is closed. Implemented for Android. ender@google.com chrome-mobile-search@google.com The type of card returned in the Search Term Resolution Response from the server when a search is resolved in response to a Tap gesture that uses surrounding text to determine the best search. This characterises what we'll show in the Bar. Recorded when the panel is closed. Implemented for Android. ender@google.com chrome-mobile-search@google.com The type of card shown in the Bar when the panel has been opened. Recorded when the panel is closed. Implemented for Android. ender@google.com chrome-mobile-search@google.com Records that a Search was done and whether the search was unintelligent or intelligent, and whether it was likely counted by Rasta. Recorded for all users when the panel is closed after being opened. Implemented for Android. (Expired in 2023-04-16. Revived in 2024-11-03.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com Records that a Contextual Search was initiated by the user, and whether that search should be counted as a real user-viewed search or not. The true bucket is designed to match what Rasta counts in its queries(event) metric as a real user search. The false bucket includes all the other cases where the Contextual Search was started but not counted by Rasta because the user has not been able to view the Search Result Page. Usually this is because the user did not expand the panel beyond the peeking state, but occasionally because it did not render. Recorded when the panel is closed for all users. Implemented for Android. (Expired in 2023-04-16. Revived in 2024-11-03.) Note: There is a recording gap between: 2025.11-2026.08. basiaz@google.com ender@google.com chrome-mobile-search@google.com Network status codes recorded for each Contextual Search request after the url loader calls the completion callback. Recorded value is the absolute value of the received net::Error value. Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com Records that a resolve response was received from the server, and whether that was due to a Tap gesture or not (vs longpress). Recorded when the user triggers the feature and the server responds. Implemented for Android. (Expired in M94. Revived in M120.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com Records that a resolve request was sent to the server, and whether that was due to a Tap or not (vs longpress). Recorded when the user triggers the feature. Implemented for Android. (Expired in 2023-02-12. Revived in 2024-11-03.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com Records that a resolve request from the server caused the selection to be expanded, and whether that original selection was due to a Tap or not (vs longpress). Recorded when the qualifying server response is received. Implemented for Android.(Expired in 2024-07-21. Revived in 2024-09-16.) Note: There is a recording gap between: 2025.11-2026.08. donnd@chromium.org ender@google.com chrome-mobile-search@google.com Records whether triggering the Touch To Search feature was suppressed due to the base page view being too small. This may happen in landscape mode, on very small phones, when a Partial Height Custom Tab is being displayed, or when muliwindow is in use with a small window. The intent is to capture in the log how many searches we lose when the gating Feature is enabled. Recorded when a gesture that would normally trigger TTS suppresses the bottom sheet from showing. Android only. Note: There is a recording gap between: M106-2026.08. ender@google.com chrome-mobile-search@google.com Records whether the user opened the panel when it was shown in response to a tap gesture, for all users. Recorded when the UX is hidden. Implemented for Android. (Expired in M77. Revived in M120.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com Records the previous state of the user's enabled preference to indicate whether they were decided or undecided about fully enabling this feature. Recorded during the rollout of Unified Consent when the Contextual Search preference is changed. Implemented for Android. (Expired after 2019-01-30. Revived in M120.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com Records whether throttling for Unified Consent was done for all requests. Recorded when the user taps on text and the system would like the server to suggest what to search for using page context, regardless of feature-enabled state. Recorded multiple times for each request. Supports the rollout of Unified Consent for Contextual Search. Implemented for Android. (Expired after 2019-01-30. Revived in M120.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com Records whether this user had a request throttled or not when needed. Recorded when the user taps on text and the system would like the server to suggest what to search for using page context, and throttling is in effect for this user. Supports the rollout of Unified Consent for Contextual Search. Implemented for Android. (Expired after 2019-01-30. Revived in M120.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com Whether Contextual Cards data was shown in the Contextual Search Bar. Contextual Cards data is included with the search term resolution response. Implemented for Android. ender@google.com chrome-mobile-search@google.com The state of the Contextual Search Preference. Can be logged multiple times. Used to determine the population size (user view). Logged whenever the Chrome application is paused. Implemented for Android. ender@google.com chrome-mobile-search@google.com The Contextual Search preference state after a modification from the preference menu. Implemented for Android. ender@google.com chrome-mobile-search@google.com The Contextual Search privacy opt-in preference state after a modification from the preference menu. Recorded when the opt-in switch in Settings page is toggled. Implemented for Android. (Expired in 2023-10-15. Revived in 2024-11-03.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com The user's choice in the Contextual Search promo card. Recorded when the 'No thanks' or 'Turn on' button on the Contextual Search Promo Card is chosen. Implemented for Android. (Expired in 2023-05-07. Revived in 2024-11-03.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com The total count of times that the revised promo has been shown. Once the user decides, this counter is no longer updated. Logged for each show of the promo card. Implemented for Android. (Expired in 2023-06-26. Revived in 2024-11-03.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com The category of quick actions shown in the Contextual Search bar. Recorded when the quick action is set. Implemented for Android. (Expired in 2023-10-22. Revived in 2024-11-03.) Note: There is a recording gap between: 2026.06-2026.08. ender@google.com chrome-mobile-search@google.com Whether a quick action in the Contextual Search bar was clicked, which activates the associated intent. Recorded when Contextual Search is dismissed due to a click on a QuickAction in the Bar. Implemented for Android. {ContextualSearchQuickActionCategory} ender@google.com chrome-mobile-search@google.com Whether a Contextual Search quick action intent resolved to zero, one, or many apps. Recorded when the quick action intent URI is resolved. Implemented for Android. (Expired in M81. Revived in M120.) {ContextualSearchQuickActionCategory} Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com Whether search results were seen as part of a Contextual Search when a quick action was shown. Recorded when Contextual Search is dismissed. Implemented for Android. (Expired in M81. Revived in M120.) {ContextualSearchQuickActionCategory} Note: There is a recording gap between: 2025.11-2026.08. ender@google.com chrome-mobile-search@google.com Whether search results were seen as part of a contextual search. Implemented for Android. ender@google.com chrome-mobile-search@google.com Whether search results were seen, broken down by original triggering gesture. Only includes users that have enabled. Implemented for Android. fikremengistu@chromium.org chrome-counter-abuse-alerts@google.com Records the outcome of default search engine (DSE) tampering detection done at profile startup. The detection is done by comparing the DSE pref with its mirror; a mismatch indicates tampering. This metric is recorded exclusively on MacOS and Windows devices. It is recorded each time a DefaultSearchManager is created, after the default search engine is loaded from prefs. davidbienvenu@chromium.org wfh@chromium.org True if the default search engine pref is the same as the mirrored pref, "default_search_provider_data.mirrored_template_url_data", false otherwise. If the default search engine pref is changed externally, this would be false. Recorded each time a DefaultSearchManager is created, after the default search engine is loaded from prefs. fikremengistu@chromium.org chrome-counter-abuse-alerts@google.com Records if the Default Search Engine (DSE) reset notification dialog is shown to a user. It is recorded once, at the moment the notification dialog is created. This occurs on the first omnibox search query that a user performs after their DSE has been automatically reset for security. The dialog will NOT be shown if, following a security reset, the user changes the DSE before the dialog is shown. This metric is recorded exclusively on macOS and Windows operating systems. mpearson@chromium.org ftirelo@chromium.org The type of the default search engine that is loaded when a regular, guest, or ChromeOS sign-in screen profile is opened or after a profile reset. (A profile reset can only happen to a regular profile.) 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. The fact that this is logged when the ChromeOS sign-on screen profile is opened means this is recorded when the ChromeOS sign-in screen is initially shown. The value recorded is the default value for the ChromeOS install; the default search engine used in this profile cannot be changed. Also note that people cannot search / browse the web using this profile. As such, the default search engine setting for this profile does not have any practical meaning. {Population} juanmojica@google.com schechter@google.com stanfield@google.com lens-chrome-eng@google.com Records all intents fired to open the Lens viewfinder enumerated by entry point, regardless of whether the intent was successful. juanmojica@google.com schechter@google.com stanfield@google.com hujasonx@google.com lens-chrome-eng@google.com Records camera results such as successful image capture, user exited, etc. This is recorded every time the user opens the Lens viewfinder camera. yeroshkin@chromium.org musalmaan@chromium.org chrome-desktop-ui-waterloo@google.com Records whether there is a site search with a URL-like keyword whose target URL has a different domain. yeroshkin@chromium.org musalmaan@chromium.org chrome-desktop-ui-waterloo@google.com Records whether there is a site search with a URL-like keyword whose target URL has a different eTLD, but the same domain otherwise. musalmaan@chromium.org iclelland@chromium.org chrome-desktop-ui-waterloo@google.com Records whether the default search engine is a custom search engine but has a non-zero `prepopulate_id`. This helps identify engines that are not part of the standard prepopulated list but are appearing in the default search list. Recorded once per profile at startup when the search engine allowlist is initialized and the configuration is checked. musalmaan@chromium.org iclelland@chromium.org chrome-desktop-ui-waterloo@google.com Records whether the user's default search engine is a custom one that is similar the name of an official, policy-enforced engine but uses a different URL on a managed profile. Recorded once per profile at startup when the search engine allowlist is initialized and the configuration is checked. musalmaan@chromium.org iclelland@chromium.org chrome-desktop-ui-waterloo@google.com Records whether the default search engine has the enforced_by_policy flag set to True, but the DefaultSearchProviderEnabled policy is not active for a managed profile. This helps detect cases where search settings might be incorrectly claiming policy enforcement. Recorded once per profile at startup when the search engine allowlist is initialized and the configuration is checked. musalmaan@chromium.org iclelland@chromium.org chrome-desktop-ui-waterloo@google.com Records which referral parameter is found in the URL of a custom search engine that is not on the allowlist on a managed profile. Recorded once per profile at startup if a custom search engine is present on a managed profile. yeroshkin@chromium.org musalmaan@chromium.org chrome-desktop-ui-waterloo@google.com Records whether there is a site search with a URL-like keyword whose target is an extension. musalmaan@chromium.org iclelland@chromium.org chrome-desktop-ui-waterloo@google.com Records whether a custom or non-standard search engine (one not present in the official Chromium prepopulated list) is available in the user's configured search engines list. Recorded once per profile at startup when the prepopulated search engine list is initialized and the configuration is checked. musalmaan@chromium.org iclelland@chromium.org chrome-desktop-ui-waterloo@google.com Records whether the user's default search engine is a custom one that mimics the name of an official, policy-enforced engine but uses a different URL. This is used to detect potential patterns where third-party software attempts to impersonate legitimate engines. Recorded once per profile at startup when the search engine allowlist is initialized and the configuration is checked. Only recorded if a custom engine is set as the default. musalmaan@chromium.org iclelland@chromium.org chrome-desktop-ui-waterloo@google.com Records whether the default search engine has the enforced_by_policy flag set to True, but the DefaultSearchProviderEnabled policy is not active. This helps detect cases where search settings might be incorrectly claiming policy enforcement. Recorded once per profile at startup when the search engine allowlist is initialized and the configuration is checked. musalmaan@chromium.org iclelland@chromium.org chrome-desktop-ui-waterloo@google.com Records whether the user's currently active default search engine is a custom or non-standard one (not in official Chromium prepopulated list). Recorded once per profile at startup when the search engine allowlist is initialized and the configuration is checked. yeroshkin@chromium.org musalmaan@chromium.org chrome-desktop-ui-waterloo@google.com Records whether there is a site search with a URL-like keyword whose target URL is obfuscated using multiple escaped characters in a row. musalmaan@chromium.org iclelland@chromium.org chrome-desktop-ui-waterloo@google.com Records which referral parameter is found in the URL of a custom search engine that is not on the allowlist. This helps identify common sources of custom search engines. Recorded once per profile at startup if a custom search engine with a referral ID is present. yeroshkin@chromium.org musalmaan@chromium.org chrome-desktop-ui-waterloo@google.com Records whether there are duplicate keywords among the installed search engines{Enterprise} Recorded once per profile on profile load. gambard@chromium.org When an iOS user changes the default search engine in chrome Settings, records the search engine's type. wfh@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Records the hash validation status for a row in the keywords table in the Web Data sqlite database. This metric is recorded for each row read from the keywords table for a v137 table and above, when the keywords table is loaded, which happens at profile load. If the validation is not successful for any reason, then the row will be dropped from the database. wfh@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Records whether or not the migration of the keywords table in the Web Data sqlite database successfully completed without dropping any rows. This metric is recorded when a Web Data database before v152 is loaded, which happens at profile load. A failure here means one or more rows have been dropped, but the table was migrated to v152 anyway. dgn@chromium.org triploblastic@google.com chrome-regionalcapabilities@google.com Measures latency for the dialog that blocks Chrome usage to require the Android OS default apps choice to be completed. [Android only] This value represents the time between when we showed the dialog and when we received a response from the backend. The backend has the most accurate information about whether the dialog needs to be shown, but we may show the dialog based on less accurate signals to avoid surprising the user after some potentially long delay into the task they started with Chrome. Recorded for each browser session eligible to show the dialog, on startup. If the status is received before the dialog is shown then 0 is recorded. dgn@chromium.org triploblastic@google.com chrome-regionalcapabilities@google.com This value represents the time between when Chrome starts waiting on the backend for a response and when the UI actually gets a response from the backend. [Android only] Recorded for each browser session that attempted to show the dialog and got a backend response, on startup. If the status is received before Chrome starts observing then 0 is recorded. dgn@chromium.org triploblastic@google.com chrome-regionalcapabilities@google.com Records the triggering attempt number of the dialog that blocks Chrome usage to require the Android OS default apps choice to be completed. [Android only] This value represents for a given client how many times that dialog was shown and blocked a session. It is recorded when the dialog is shown, and the count gets cleared when Chrome gets the signal that the OS choices have been completed or the feature is entirely disabled. It would restart to 0 if a similar blocking campaign is restarted. Recording timing: on startups where we actually show the dialog. dgn@chromium.org triploblastic@google.com chrome-regionalcapabilities@google.com State of the dialog that blocks Chrome usage to require the Android OS default apps choice to be completed, logged every time it changes. [Android only] The dialog itself is triggered shortly after startup when it is determined that blocking the user is needed. Some status changes might be happening while the dialog is not visible, for example when the feature is in the "dark launch" mode. The "Unknown" value is logged when the dialog is dismissed. dgn@chromium.org triploblastic@google.com chrome-regionalcapabilities@google.com Logs the status of the choice dialog (if it's shown) when Chrome is brought to the foreground. [Android only]. dgn@chromium.org triploblastic@google.com chrome-regionalcapabilities@google.com Outcome of the logic determining whether to suppress the dialog that blocks Chrome usage to require the Android OS default apps choice to be completed. [Android only] At the moment of showing the dialog on startup, some additional checks can suppress it, and whether these conditions are met is reported in this histogram. The user then does not see the dialog, and Chrome drops the connection to the backend until another attempt on next startup. Recording timing: on startup, when we attempt to show the dialog. dgn@chromium.org triploblastic@google.com chrome-regionalcapabilities@google.com Indicates how a user tap on the blocking dialog's action button was processed. This dialog blocks Chrome usage to require the Android OS default apps choice to be completed. [Android only] The status is recorded at the moment of the button tap. We use some heuristic to estimate whether the choice screen has actually been launched since the last button tap. This status indicates whether we identified the current tap as the initial one, or whether for a repeated tap we decided to avoid requesting the choice screen to be launched again. shaktisahu@chromium.org chrome-upboarding-eng@google.com Indicates whether or not a bitmap could be shown for a tile. {TileUiSurface} shaktisahu@chromium.org chrome-upboarding-eng@google.com Records the index of the tile that was clicked. The index refers to the position of the tile in the carousel. {TileUiSurface} shaktisahu@chromium.org chrome-upboarding-eng@google.com Indicates whether the tile clicked was a top level tile. {TileUiSurface} shaktisahu@chromium.org chrome-upboarding-eng@google.com Indicates the number of tiles displayed in the UI after the backend was loaded. {TileUiSurface} juanmojica@google.com benwgold@google.com stanfield@google.com lens-chrome-eng@google.com Records an enum representing the aspect ratio of the region selected after using the Lens Region Search feature. juanmojica@google.com benwgold@google.com stanfield@google.com lens-chrome-eng@google.com Records a percentage to represent the proportion of the selected region to the screen after selecting a region with the Lens Region Search feature. juanmojica@google.com benwgold@google.com stanfield@google.com lens-chrome-eng@google.com Records an enum representing the result of the capture of the region for Lens Region Search feature. ender@google.com related-searches-vteam@google.com Enumerates all users by the permissions needed in order to use the Related Searches feature. This tells us the potential user pool if we were to remove one of the current requirements (which are sending page content and sending the URL to Google). Logged whenever the Chrome application is paused. NOTE: Use the Count unique clients option to count users since multiple events are logged for each user. Implemented for Android. (Expired in 2022-12-11. Revived in 2024-11-03.) ender@google.com related-searches-vteam@google.com The last visible position index for a chip in the carousel. the index is 0 based. Ex. There are 10 chips, and only 2 chips are shown completely, and 1 chip is shown half, in this case, 2 will be reported. Recorded every time the carousel is shown, or the carousel content is updated. Implemented for Android. Note: There is a recording gap between: 2026.05-2026.08. ender@google.com related-searches-vteam@google.com Records whether and how the user interacted with the carousel. Recorded when the presentation UI is dismissed while the carousel is shown. Implemented for Android. Note: There is a recording gap between: 2025.11-2026.08. ender@google.com related-searches-vteam@google.com Records whether the user scrolled the carousel when it was shown, this can help us to find users who discover carousel scroll gesture. Recorded when the presentation UI is dismissed while the carousel is shown. Implemented for Android. Note: There is a recording gap between: 2025.11-2026.08. ender@google.com related-searches-vteam@google.com Records the click through rate for Related Searches. This is the rate that at least one suggestion was chosen by the user when any were shown. Records false whenever Related Searches suggestions were shown to the user but none were selected, and true whenever the user has clicked on any suggestion to view the suggested query. Only records one entry per botton-sheet session. Recorded when the presentation UI is dismissed. Implemented for Android. (Expired in 2022-08-07. Revived in 2024-11-03.) Note: There is a recording gap between: 2025.11-2026.08. ender@google.com related-searches-vteam@google.com The number of suggestions that were chosen by the user in a bottom-sheet session when the user chose any Related Searches. Written when the suggestions UI is closed. Implemented for Android. Note: There is a recording gap between: 2026.01-2026.08. ender@google.com related-searches-vteam@google.com Records true for every user that is qualified for the Related Searches experiment regardless of whether that feature is enabled or not. Never logs false. Used to validate that population sizes are relatively equal (since only a subset is actually qualified). Logged whenever a user triggers Contextual Search in way that could activate Related Searches (i.e. sends context). NOTE: Use the Count unique clients option to count users since multiple events are logged for each user. Implemented for Android. ender@google.com related-searches-vteam@google.com The display position index for a chip in the carousel when it was selected by the user. Written when a Related Searches suggestion chip is clicked. Implemented for Android. (Expired in 2023-10-22. Revived in 2024-11-03.) Note: There is a recording gap between: 2026.05-2026.08. ender@google.com related-searches-vteam@google.com The display position index for a suggestion when it was selected by the user. The suggestion at location 0 is always the default selection search, which may not be a possible position in some implementations. All indecies from 1 on are true Related Searches suggestions. Written when a Related Searches suggestion in the UI is selected. Implemented for Android. (Expired in 2023-02-12. Revived in 2024-11-03.) Note: There is a recording gap between: 2025.11-2026.08. dullweber@chromium.org dgn@chromium.org chrome-regionalcapabilities@google.com Records whether users chose to save the Guest search engine. Recorded for profiles that are eligible for saving the guest search engine when the search engine choice dialog is confirmed. triploblastic@chromium.org dgn@chromium.org chrome-regionalcapabilities@google.com When users change search engine in os settings and come back to Chrome a snackbar is shown with a button to take them to the chrome settings page. This histogram is recorded when users click on that button. The snackbar is only shown if Chrome was in the background during the search engine update in os settings and then Chrome is foregrounded again. Because we depend on broadcast events to show the snackbar. On cold starts we simply import the settings from os on Chrome update and don't show the snackbar. Android only. triploblastic@chromium.org dgn@chromium.org Time taken to connect to the country code providing Play Service. Only includes {Result} connection attempts. Recorded every time Chrome tries to obtain the country code for the search choice screen, which happens on every startup. Android only. triploblastic@chromium.org dgn@chromium.org Time taken to fetch the country code from the country code providing Play Service. Only includes {Result} fetch attempts. Recorded every time Chrome tries to obtain the country code for the search choice screen after successfully connecting to the Play Service, which happens on every startup. Android only. triploblastic@chromium.org dgn@chromium.org Boolean status marking the beginning of connection request to country code provider service from Play and also the completion of the request. Recorded every time Chrome tries to obtain the country code for the search choice screen, which happens on every startup. Android only. yusufo@chromium.org dgn@chromium.org The search engines listed in the options for search engine promo. This is an Android specific dialog prompting the user to pick a default search engine. The dialog was shown on a device that had Chrome before it was first introduced. Warning: this histogram was expired from M81 to M124; data may be missing. {SearchEnginePromoDeviceAndOrdering} yusufo@chromium.org dgn@chromium.org The search engine selected by the user from the search engine promo. This is an Android specific dialog prompting the user to pick a default search engine. The dialog was shown on a device that had Chrome before it was first introduced. Warning: this histogram was expired from M81 to M124; data may be missing. {SearchEnginePromoDeviceType} qlucyk@chromium.org iclelland@chromium.org top-chrome-desktop-ui@google.com Records the user's default browser state. Recorded when the user visits a Google Search URL and is evaluated for the search promotion. Recorded asynchronously to avoid blocking the UI thread. Only recorded on Windows. qlucyk@chromium.org iclelland@chromium.org top-chrome-desktop-ui@google.com Records the user's default browser type (Chrome, Edge, Safari, Firefox, etc.). Recorded when the user {Interaction} the search promotion IPH for {Action}. Recorded asynchronously on a background task thread. Only recorded on Windows. qlucyk@chromium.org iclelland@chromium.org Records the task-specific exit code returned by Platform Experience Helper when executing the RegisterSearchPromotion delegated task. Recorded when the delegated task finishes execution and returns its result to Chrome. Only recorded on Windows. qlucyk@chromium.org iclelland@chromium.org Records the roundtrip execution duration taken for the RegisterSearchPromotion delegated task when the outcome is {Outcome}. Recorded when the delegated task finishes execution and returns a task-specific exit code to Chrome. Only recorded on Windows. qlucyk@chromium.org iclelland@chromium.org top-chrome-desktop-ui@google.com Records when a user visits a Google Search URL and is evaluated for the search promotion feature, across all active experiment arms and the control group. Recorded on navigation to a target URL. Only recorded on Windows. dgn@chromium.org droger@chromium.org The status of the preference where the search engine overrides provided by the Chrome distribution channel are loaded. It is recorded every time we put together a list of built-in search engines providers, which can happen multiple times per run, when initially loading search engines for the omnibox, showing a search engine choice screen or settings screen, etc.