ender@google.com jdonnelly@chromium.org mpearson@chromium.org When a user presses an omnibox suggestion based on the content of the clipboard, this histograms records how long ago Chrome detected a change in the clipboard. Intended to be compared to Omnibox.ClipboardSuggestionShownAge. If Chrome never detected a change to the clipboard, no clipboard suggestion is shown, meaning this histogram will never be emitted to. {ClipboardSuggestionType} yoangela@chromium.org chrome-desktop-search@google.com Records number of accepted keyword searches enumerated by how the user entered the keyword mode. See also Omnibox.EnteredKeywordMode2 for the total number of times a user enters keyword mode whether or not the keyword suggestion was accepted. Note that this only records when a user accepts a search suggestion for the keyword search engine and does not record for URL suggestions even if the user is in keyword mode. ender@google.com chrome-mobile-search@google.com For action of type "{Type}", captures whether the user interacted with this action to complete the interaction with the omnibox. The histogram is captured only if the action "{Type}" was presented to the user when the interaction with the omnibox completed. The sum of "Used" and "Not Used" indicates the sum of all impressions of a given action. Action in Suggest are the Omnibox Action chips attached to a search suggestion. Starting with Chrome/Android M142 this histogram is recorded whenever the Omnibox is used to navigate somewhere, closely matching how other Omnibox histograms are recorded. Before M142 this histogram would be recorded any time the Omnibox interaction has completed, whether the user initiated navigation or not. ender@google.com chrome-mobile-search@google.com Counts how often Omnibox Action in Suggest are {ShownOrUsed} and records the type (Omnibox Action in Suggest Type) of every {ShownOrUsed} action. Recorded once at the end of the interaction with the Omnibox Suggestions for every Action presented to the user. Not recorded for Suggestions that are annotated with Action in Suggest, where the Action in Suggest row was not shown to the user. Action in Suggest are the Omnibox Action chips attached to a search suggestion. Starting with Chrome/Android M142 this histogram is recorded whenever the Omnibox is used to navigate somewhere, closely matching how other Omnibox histograms are recorded. Before M142 this histogram would be recorded any time the Omnibox interaction has completed, whether the user initiated navigation or not. mahmadi@chromium.org mercerd@google.com chrome-desktop-search@google.com Logs whether the country code returned by variations service was empty. Logged every time the country code is requested by the AIM eligibility service. mahmadi@chromium.org avivkiss@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. This metric logs whether the request was debounced (i.e., a new request is scheduled while a timer for a previous request is already running), sliced by request source. This metric is logged every time a request is attempted. mahmadi@chromium.org avivkiss@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. This metric logs whether the request fell back to cookies because an OAuth token was unavailable, sliced by request source. The metric is logged when a request is attempted and OAuth is not available. mahmadi@chromium.org avivkiss@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. This metric logs the status of the OAuth token fetch, sliced by request source. This metric is logged every time the OAuth token is fetched (happens whenever a request is made). mahmadi@chromium.org avivkiss@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. This metric logs whether an OAuth token was successfully provided for the request, sliced by request source. This metric is logged every time the OAuth token is fetched (happens whenever a request is made). mahmadi@chromium.org manukh@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. The requests are triggered on profile startup, when the primary account changes, or whenever an AIM interception may happen. This metric logs whether the primary account exists when the request was sent, sliced by request source. mahmadi@chromium.org manukh@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. The requests are triggered on profile startup, when the primary account changes, or whenever an AIM interception may happen. This metric logs whether the primary account was found in the cookie jar when the request was sent, sliced by request source. Logged only if the primary account exists. mahmadi@chromium.org manukh@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. The requests are triggered on profile startup, when the primary account changes, or whenever an AIM interception may happen. This metric logs the index of the primary account in the cookie jar when the request was sent, sliced by request source. Logged only if the primary account exists and was found in the cookie jar. mahmadi@chromium.org avivkiss@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. This metric logs the number of retries for failed requests. Retries are triggered on network changes or DNS resolution failures. A count of 0 indicates that the request succeeded or failed on the first attempt (and wasn't within policy for a retry). This metric is logged only when the request completes. mahmadi@chromium.org manukh@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. The requests are triggered on profile startup, when the primary account changes, or whenever an AIM interception may happen. This metric logs the status of the request, sliced by request source. mahmadi@chromium.org avivkiss@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. The requests are triggered on profile startup, when the primary account changes, or whenever an AIM interception may happen. This metric logs whether the account changed in the time between when the eligibility request was sent and when the response was received. This is logged whenever a response is received. mahmadi@chromium.org manukh@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. The requests are triggered on profile startup, when the primary account changes, or whenever an AIM interception may happen. This metric is logged only when the server response changes compared to the previous value (e.g., the value of the "{Feature}" field differs from the last logged response). For the "session_index" variant, this records whether the selected account index changed. If the response fails (e.g. server is down or response is poorly formatted), this metric will not be logged. mahmadi@chromium.org manukh@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. The requests are triggered on profile startup, when the primary account changes, or whenever an AIM interception may happen. This metric logs the HTTP response code, sliced by request source. mahmadi@chromium.org manukh@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. The requests are triggered on profile startup, when the primary account changes, or whenever an AIM interception may happen. This metric logs the source of the eligibility response when the service is queried by its clients for the server eligibility status. It helps determine how often the clients are receiving a fresh response from the server, a stale response stored in the prefs, or the default value. mahmadi@chromium.org manukh@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. The requests are triggered on profile startup, when the primary account changes, or whenever an AIM interception may happen. This metric logs the selected session index (index of the account in the cookie jar selected by the server for authentication), sliced by request source. If the field is missing or false, this metric will log false. If the response fails (e.g. server is down or response is poorly formatted), this metric will not be logged. mahmadi@chromium.org manukh@chromium.org chrome-desktop-search@google.com The AIM Eligibility service makes HTTP requests to determine which AIM features the user is eligible for. The requests are triggered on profile startup, when the primary account changes, or whenever an AIM interception may happen. This metric logs whether the response contained a "{Feature}" field set to true, sliced by request source. If the field is missing or false, this metric will log false. If the response fails (e.g. server is down or response is poorly formatted), this metric will not be logged. khalidpeer@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Recorded when the user activates the AIM entrypoint (page action) in the Omnibox. More specifically, this metric records whether the user had text in the Omnibox at the time they activated the AIM entrypoint. Activation can be achieved via keyboard events (e.g. hitting [ENTER] or [SPACE] while the page action is focused), via mouse/gesture events (e.g. clicking or tapping on the page action), or by adding context (e.g. an open tab). Sliced by {OmniboxPageContext} which represents the page classification at the time of AIM page action activation. {AimEntrypointParty} khalidpeer@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Recorded when the user activates the AIM entrypoint (page action) in the Omnibox. More specifically, this metric records whether the user had text in the Omnibox at the time they activated the AIM entrypoint. Activation can be achieved via keyboard events (e.g. hitting [ENTER] or [SPACE] while the page action is focused), via mouse/gesture events (e.g. clicking or tapping on the page action), or by adding context (e.g. an open tab). {AimEntrypointParty} khalidpeer@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Recorded when the user activates the AIM entrypoint (page action) in the Omnibox. This metric records `true` when the user activates the entrypoint via keyboard (e.g. hitting [ENTER] or [SPACE]) and records `false` when the user activates the entrypoint via mouse/gesture events (e.g. clicking or tapping on the page action) or by adding context (e.g. an open tab). Sliced by {OmniboxPageContext} which represents the page classification at the time of AIM page action activation. {AimEntrypointParty} khalidpeer@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Recorded when the user activates the AIM entrypoint (page action) in the Omnibox. This metric records `true` when the user activates the entrypoint via keyboard (e.g. hitting [ENTER] or [SPACE]) and records `false` when the user activates the entrypoint via mouse/gesture events (e.g. clicking or tapping on the page action) or by adding context (e.g. an open tab). {AimEntrypointParty} khalidpeer@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Recorded whether the AIM entrypoint (page action) was shown at least once during an Omnibox session. This is recorded once per Omnibox navigation or AIM entrypoint activation. The entrypoint will only be shown if the user is eligible for AIM functionality. Showing the AIM entrypoint on focus only won't log true for navigations; it must be shown as the user is typing in order to log true. Showing the AIM entrypoint on focus only and activating the entrypoint will log true. Sliced by {OmniboxPageContext} which represents the page classification when the AIM page action was shown to the user. {AimEntrypointParty} khalidpeer@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Recorded whether the AIM entrypoint (page action) was shown at least once during an Omnibox session. This is recorded once per Omnibox navigation or AIM entrypoint activation. The entrypoint will only be shown if the user is eligible for AIM functionality. Showing the AIM entrypoint on focus only won't log true for navigations; it must be shown as the user is typing in order to log true. Showing the AIM entrypoint on focus only and activating the entrypoint will log true. {AimEntrypointParty} manukh@chromium.org chrome-omnibox-team@google.com The source of the icon for the AI mode page action. Logged exactly once when the icon is updated or hidden. When shown, logs where the icon was sourced from. Logged when the page action is explicitly hidden. Logged when the page action is requested to be shown, but the icon fails to load, and the page action is therefore hidden. Can be logged multiple times if the page action is shown/hidden multiple times, even if caused by a single user action. E.g., focusing the omnibox on the NTP will trigger the show-page-action logic 5 times, and will log this histogram 5 times. This makes this histogram pretty difficult to interpret since the 1st show may log `kNetworkFetch` while the next 4 shows may log `kMemoryFaviconCache`, giving a false impression that most times the icon was cached. When the page action is shown, it'll attempt to update its icon. If google is the DSE, it will use a built-in vector icon. Else if the 3rd party's favicon is in the omnibox's in-memory favicon cache, it will use that cached icon. Else if the favicon is in the on-disk DB favicon cache, it will use that cached icon. Else if a network request to fetch the icon succeeds, it will use that fetched icon. Else it will hide the page action. Each of these cases will log a corresponding value. Exactly 1 of these will be logged when the page action is shown or hidden. jdonnelly@chromium.org chrome-desktop-search@google.com For each answer received in suggest responses, the number that are well-formed and contain all the required elements. jdonnelly@chromium.org chrome-desktop-search@google.com The number of times each omnibox suggestion answer type (e.g., weather, sports score) was received and parsed successfully. Can be normalized with the count of emits to Omnibox.SuggestRequest.Success.GoogleResponseTime, which counts all successful suggest responses from Google, not just those with answers attached. Note that GoogleResponseTime is technically off given that it will still count cases where we fail to extract, deserialize, or parse the response. But these cases are rare to non-existent. manukh@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com When the user focuses or types into the omnibox, the dropdown results can be updated multiple times per input (i.e. when focused, per char typed, backspace, etc). Specifically, the set of events that trigger dropdown updates are: - synchronous suggestions - asynchronous suggestions. Can trigger multiple times per input. These are often generated on different threads. - expiring copied matches - interruptions e.g. additional user input changes or closing the dropdown A sample flow looks like: 1) User types a character. 2) 10ms later, update results with synchronous suggestions. 3) 50ms later, update results with some asynchronous suggestions. 4) 50ms later, update results with more asynchronous suggestions. 5) 400ms later, update results by removing copied matches from the previous input. 6) 50 later, update results with the last batch of asynchronous suggestions. The 'Provider.*' slices measure the time between the input change and the last async update of that provider is done or interrupted. Includes async updates that have no user visible change (i.e. that do not produce async matches or produce only async matches that get deduped, culled, or are the same as the existing match in its position). Only logged for asynchronous providers. Emitted exactly once per input per asynchronous provider; additionally emits to exactly one of the 'Completed' and 'Interrupted' slices per input per asynchronous provider. {Completed} manukh@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com When the user focuses or types into the omnibox, the dropdown results can be updated multiple times per input (i.e. when focused, per char typed, backspace, etc). Specifically, the set of events that trigger dropdown updates are: - synchronous suggestions - asynchronous suggestions. Can trigger multiple times per input. These are often generated on different threads. - expiring copied matches - interruptions e.g. additional user input changes or closing the dropdown A sample flow looks like: 1) User types a character. 2) 10ms later, update results with synchronous suggestions. 3) 50ms later, update results with some asynchronous suggestions. 4) 50ms later, update results with more asynchronous suggestions. 5) 400ms later, update results by removing copied matches from the previous input. 6) 50 later, update results with the last batch of asynchronous suggestions. {Change} {Completed} manukh@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com The time `AutocompleteController::UpdateResult()` took. That method is invoked, and this histogram is recorded: a) Once for the sync autocomplete update that occurs when the omnibox input changes (e.g. the user types a character, pastes text, focuses the omnibox, etc). b) Once for each async autocomplete update that occurs asyncly after the omnibox input changes and the various async providers complete. Usually occurs up to 3 times per input change. But can be less if the updates are interrupted (e.g. the popup is closed or input changed again) or include no new suggestions. c) Once when copied matches from the previous autocomplete pass expire. This happens at most once per input change, but may not occur if all providers complete or the input changes prior to the expiration. Because this encompasses both sync and async omnibox updates, and the number of async updates per sync update is not fixed, it's not a good representative of how a feature effects user experienced latency. E.g., a feature that makes users type slower will bias this metric towards async updates. Besides, this is only a small segment of the user experienced latency. This is only intended to measure changes in the actual implementation of `UpdateResult()`. {Slice} This metric uses SCOPED_UMA_HISTOGRAM_TIMER_MICROS so clients without high-resolution clocks will either a) be dropped, b) report 0 for very short times, or c) be recorded as expected (depending on which comments you believe ¯\_(ツ)_/¯). ender@google.com woa-performance-bugs+jank@google.com Measures the amount of time it takes to call UrlBar.calculateVisibleHint(). Recorded once per call. manukh@chromium.org jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com Records the time taken between a keystroke being typed in the omnibox and the text being painted. If there are multiple keystrokes before a paint, logs the time since the earliest one. This duration is composed of three parts: a) the time spent processing the initial input event b) the time spent for the repaint task to be scheduled on the message loop c) the time spent painting the Omnibox d) (on views platforms) the time until the pixels are actually composited There's a number of breakdown metrics to help diagnose a regression. First, Omnibox.CharTypedToRepaintLatency.ToPaint measures the combined time of (a) and (b). Omnibox.QueryTime2 is a good proxy for just (a). And there's also Omnibox.PaintTime that corresponds to (c). We don't have a direct metric for (d), but if neither Omnibox.CharTypedToRepaintLatency.ToPaint nor Omnibox.PaintTime regressed, then the regression must be in (d). Note #1: The semantics of this metric on views platforms changed in M62, as previously time (d) was not included in the metric. Note #2: The semantics of this metric changed in M130, due to switching over from the `OnCompositingAckDeprecated()` compositor lifecycle function to `OnDidPresentCompositorFrame()`. The new function provides more accurate timings, which also happen to be larger in magnitude than values that were logged prior to M130. For more details, please refer to crbug.com/347322940 and crrev.com/c/5857101. manukh@chromium.org mpearson@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com A refinement of Omnibox.CharTypedToRepaintLatency metric. It measures the time between the first character insertion in a series that happen during a frame, to the time the compositor reports the text was rendered on-screen. Compositor-provided timestamps are used for this version of the metric, so it is expected to be more accurate: the baseline CharTypedToRepaintLatency uses now() from when the subsequent has-processed notification arrives back on the UI thread, which may overestimate user-visible latency. Note: Compositor-provided timestamps are taken using presentation time callbacks. Before M110 the callbacks used for this histogram might be called even if the next submitted frame fails to present which means that the character is not really rendered on-screen yet. From M110 onward, this is fixed by using callbacks that are only called after the first following successful presentation, so a slight change might be noticed in the histogram values. manukh@chromium.org mpearson@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Records the time between when OnPaint() is called to the time the compositor reports pixels were successfully drawn to the screen. This a subset of the time reported in Omnibox.CharTypedToRepaintLatency.InsertToPresent. Note: Compositor-provided timestamps are taken using presentation time callbacks. Before M110 the callbacks used for this histogram might be called even if the next submitted frame fails to present which means that the character is not really rendered on-screen yet. From M110 onward, this is fixed by using callbacks that are only called after the first following successful presentation, so a slight change might be noticed in the histogram values. Warning: this histogram was expired from 2021-06-30 to 2022-12-12; data may be missing. manukh@chromium.org mpearson@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Records the time taken between a keystroke being typed in the omnibox and the time when we're ready to paint the omnibox. This is a breakdown diagnostic metric for Omnibox.CharTypedToRepaintLatency, to help diagnose regressions in that metric. See that metric's description for more info. jdonnelly@chromium.org ender@google.com Recorded every time the clipboard suggestion is removed from omnibox suggestion list and the system clipboard. The value indicates the estimated age of the clipboard. {ClipboardSuggestionType} Note: There is a recording gap between: 2022.09-2023.08, 2026.01-2026.08. jdonnelly@chromium.org ender@google.com Recorded every time the omnibox is focussed and recent content from the user's clipboard is suggested. The value indicates the estimated age of the clipboard. (If Chrome observed the clipboard modification, this age is exact. If Chrome did not observe the modification, then it's a conservative estimate: the last time Chrome observed a clipboard modification, which is certainly older than the current clipboard. If Chrome never observed a clipboard modification, no clipboard suggestion is shown, meaning this histogram will never be emitted to.) Intended to be compared with MobileOmnibox.PressedClipboardSuggestionAge. {ClipboardSuggestionType} jdonnelly@chromium.org ender@google.com Recorded every time the omnibox is focussed and a recent content from the user's clipboard is suggested. The number emitted is the number of times the clipboard content has been suggested within the same session including the current time. Thus, the third time it is shown, we'll emit a three to this histogram, and this histogram will have previously seen emits of one and two. If the clipboard content was the same during a previous run of Chrome and this clipboard content was suggested during that run, those impressions are not counted. Also, if the clipboard content changes during a particular run of Chrome to other content, the omnibox is focused and that clipboard content is suggested, then content changes back and Chrome starts suggesting the older clipboard content again, the counts start again from scratch. Chrome only remembers the number of times the clipboard content was shown consecutively. This value is useful to compare with the number of times a clipboard suggestion has been shown when it is clicked. This value can be obtained from OmniboxEvent records in which the selected suggestion is from Clipboard provider. In those cases, look in the Clipboard provider's ProviderInfo field for |times_returned_results_in_session|. Note that at the time of this writing that OmniboxEvent logs aren't recorded in incognito whereas histograms are. Thus, the total counts will not be comparable, though the distributions should be. {ClipboardSuggestionType} jdonnelly@chromium.org ender@google.com Recorded every time the omnibox is focussed and a recent content from the user's clipboard is suggested. The value indicates whether the current URL was shown (which would appear above the clipboard suggestion) or was absent (which ought to only happen when the omnibox is empty / the user is on the NTP). On Android, the total count for this histogram can be usefully compared with the count of the user action FocusLocation in order to determine the rate at which a clipboard suggestion is shown in the omnibox. To determine the same rate on iOS, one needs to compare this histogram's count with the sum of the user actions MobileFocusedOmniboxOnNtp, MobileFocusedFakeboxOnNtp, and MobileFocusedOmniboxNotOnNtp. Furthermore, on either platform, this histogram's count can be usefully compared with the count in the clipboard bucket of the Omnibox.SuggestionUsed.Provider histogram to determine the clickthrough rate on these suggestions. {ClipboardSuggestionType} Note: There is a recording gap between: 2022.10-2023.08, 2025.11-2026.08. jennserrano@google.com chrome-desktop-search@google.com Records whether any company entity image was ablated. This histogram is logged to once per autocomplete pass when there exists a suggestion of entity type. Recorded after attempting to find matching domains between a historical URL and a company entity website URI. dhruvkathpalia@google.com chrome-desktop-search@google.com Records whether the context menu (nextbox) animation was shown to the user or blocked due to the ContextMenuAnimationLimiting experiment on Contextual Tasks page. Recorded when the context menu animation is shown on the Nextbox. dhruvkathpalia@google.com chrome-desktop-search@google.com Records whether the context menu (realbox) animation was shown to the user or blocked due to the ContextMenuAnimationLimiting experiment on NTP. Recorded when the context menu animation is shown on the Realbox. khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if at least one contextual search suggestion was offered during the course of the Omnibox session. Given that at least one contextual search suggestion was offered during the session, this records whether or not the user ultimately selected a contextual search suggestion in the Omnibox. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. (Precision = Usage / Recall) khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if at least one contextual search suggestion was offered during the course of the Omnibox session. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. (Recall = Usage / Precision) khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if the user selected a contextual search suggestion in the Omnibox. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. (Usage = Precision * Recall) mastiz@chromium.org chrome-desktop-search@google.com The age of the remote tab when the cross-device suggestion was shown. Background: When the omnibox is focused (Zero-Suggest state), it may show at most one cross-device tab suggestion. This suggestion always corresponds to the user's most recently active tab across all synced devices. If this most recent tab is not eligible (e.g., URL is invalid or the tab is too old), no suggestion is shown. These suggestions always include an action chip to open the synced tabs history page (chrome://history/syncedTabs). Recorded when the user completes their omnibox interaction with a navigation, provided the cross-device suggestion was present in the list (impressed). It is recorded even if the user navigated to a different suggestion, but is not recorded if the cross-device suggestion was not shown at all. mastiz@chromium.org chrome-desktop-search@google.com Tracks the eligibility of showing the cross-device tab match. Background: When the omnibox is focused (Zero-Suggest state), it may show at most one cross-device tab suggestion. This suggestion always corresponds to the user's most recently active tab across all synced devices. If this most recent tab is not eligible (e.g., URL is invalid or the tab is too old), no suggestion is shown. These suggestions always include an action chip to open the synced tabs history page (chrome://history/syncedTabs). Recorded every time CrossDeviceTabProvider is run in Zero-Suggest state (but not in typed state), indicating whether a match was created or why it wasn't. mastiz@chromium.org chrome-desktop-search@google.com The age of the most recent tab found across all foreign sessions, before applying the age filter (i.e. selection of recent tabs only). Background: When the omnibox is focused (Zero-Suggest state), it may show at most one cross-device tab suggestion. This suggestion always corresponds to the user's most recently active tab across all synced devices. If this most recent tab is not eligible (e.g., URL is invalid or the tab is too old), no suggestion is shown. These suggestions always include an action chip to open the synced tabs history page (chrome://history/syncedTabs). Recorded every time CrossDeviceTabProvider is run in Zero-Suggest state (but not in typed state) and at least one tab is found. mastiz@chromium.org chrome-desktop-search@google.com The age of the remote tab when the user navigated by selecting the cross-device tab {Target}. Background: When the omnibox is focused (Zero-Suggest state), it may show at most one cross-device tab suggestion. This suggestion always corresponds to the user's most recently active tab across all synced devices. If this most recent tab is not eligible (e.g., URL is invalid or the tab is too old), no suggestion is shown. These suggestions always include an action chip to open the synced tabs history page (chrome://history/syncedTabs). Recorded on navigation, only if the user selected this specific target. It is not recorded if another suggestion was selected. mastiz@chromium.org chrome-desktop-search@google.com The amount of time between the user focusing the location bar and navigating by selecting the cross-device tab {Target}. Background: When the omnibox is focused (Zero-Suggest state), it may show at most one cross-device tab suggestion. This suggestion always corresponds to the user's most recently active tab across all synced devices. If this most recent tab is not eligible (e.g., URL is invalid or the tab is too old), no suggestion is shown. These suggestions always include an action chip to open the synced tabs history page (chrome://history/syncedTabs). Recorded on navigation, only if the user selected this specific target. It is not recorded if another suggestion was selected. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com The number of cut or copy commands on all selected text in the omnibox. Gathered on desktop platforms (Win, Mac, Linux, Chrome OS). manukh@chromium.org jdonnelly@chromium.org Counts the number of responses from the document suggestion service, bucketed by the HTTP response code. Recorded once per response received, which is 0 or 1 times per request sent, since some requests are cancelled. At most 1 request is sent per omnibox autocompletion cycle (in other words, per each time the user changes the omnibox input). mahmadi@google.com chrome-desktop-search@google.com Counts the number of responses from the DocumentSuggestionsService and if the user is subject to Enterprise policies bucketed by the HTTP response code. Recorded once per response received, which is at most 1 time per request sent, which is at most 1 time per omnibox autocompletion cycle, i.e., each time the user changes the omnibox input. manukh@chromium.org jdonnelly@chromium.org Counts the number of times the document provider's `Start` method is called by the AutocompleteController, bucketed by the reason applied for whether or not the provider is allowed to run (in other words, whether the profile and session meets all the requirements to request document suggestions from the server). Recorded exactly once per omnibox autocompletion cycle (in other words, per each time the user changes the omnibox input). The reason recorded is the first reason encountered which determines that we should not run the provider. In other words, each bucket is an undercount of whether that reason _could have been used_ to decide not to run the provider. Therefore, interpreting these results requires an understanding the order of the checks in `DocumentProvider::IsDocumentProviderAllowed`. manukh@chromium.org jdonnelly@chromium.org Counts the number of requests DocumentProvider sent, were invalidated, and were completed successfully. manukh@chromium.org jdonnelly@chromium.org Measures the duration between when the async backend request was sent and response received. Recorded exactly once per backend request. This will be a subset of times document suggestions were requested, as 1) the provider is debounced, 2) the provider may be interrupted (e.g. due to a new input) before the request is sent (i.e. before the oauth token is ready), and 3) some provider requests are filtered (e.g. input too short). manukh@chromium.org jdonnelly@chromium.org Measures the duration between when the async backend request was sent and response received. Recorded at most once per backend request. This will be a subset of times document suggestions were requested, as 1) the provider is debounced, 2) the provider may be interrupted (e.g. due to a new input) before the request is sent (i.e. before the oauth token is ready), and 3) some provider requests are filtered (e.g. input too short). Only recorded if the backend request was invalidated; i.e., the provider was interrupted before the response was received. manukh@chromium.org jdonnelly@chromium.org Measures the duration between when the async backend request was sent and response received. Recorded at most once per backend request. This will be a subset of times document suggestions were requested, as 1) the provider is debounced, 2) the provider may be interrupted (e.g. due to a new input) before the request is sent (i.e. before the oauth token is ready), and 3) some provider requests are filtered (e.g. input too short). Only recorded if the backend request was not invalidated; i.e., the provider was not interrupted before the response was received. manukh@chromium.org mpearson@chromium.org jdonnelly@chromium.org skare@chromium.org Number of results returned in each document suggestion reply. Logged for successful requests where the provider returned a parseable result set. manukh@chromium.org jdonnelly@chromium.org Measures the duration between when the provider begins (after a debouncing delay) and ends. Recorded exactly once per processed provider request. This will be a subset of times document suggestions were requested, as 1) the provider is debounced, and 2) some provider requests are filtered (e.g. input too short). manukh@chromium.org jdonnelly@chromium.org Measures the duration between when the provider begins (after a debouncing delay) and ends. Recorded at most once per processed provider request. This will be a subset of times document suggestions were requested, as 1) the provider is debounced, and 2) some provider requests are filtered (e.g. input too short). Only recorded if the provider was interrupted (e.g. due to a new input). manukh@chromium.org jdonnelly@chromium.org Measures the duration between when the provider begins (after a debouncing delay) and ends. Recorded at most once per processed provider request. This will be a subset of times document suggestions were requested, as 1) the provider is debounced, and 2) some provider requests are filtered (e.g. input too short). Only recorded if the provider was not interrupted (e.g. due to a new input). kenoss@chromium.org chrome-prerendering@google.com Records a No-Varry-Search data cache change when a non-redirect response header for DSE prefetch is received. khalidpeer@chromium.org kenoss@chromium.org chrome-desktop-search@google.com chrome-prerendering@google.com Measures the difference between "the client judged it should preload" and "preload is actually triggered". Records the result of signal when the client judged it should trigger {PreloadType} in DSE {DsePreloadTriggerType}. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com The new enumeration of how many times users enter keyword hint mode "Search ___ for:" and how. Changing the keyword after entering keyword mode will re-log this metric. orinj@chromium.org chrome-desktop-search@google.com Counts how many times users entered keyword mode with each entry method, just like Omnibox.EnteredKeywordMode2, but logged only when the user has additional input text after entering keyword mode. In many cases, some input is required to enter keyword mode, for example by typing a keyword and then accepting it with tab or space. But then once in keyword mode, the input field again appears empty. This histogram will not log in such cases. It will only log when some extra input remains after entering keyword mode. Some examples of how this could happen: 1) Invoking an omnibox toolbelt action after typing a query like 'hi'. 2) Backing up the cursor and inserting a space afer the 'm' in 'google.comhi'. 3) Typing 'hi' and then pressing Ctrl+K. In these cases, the additional 'hi' text remains after the omnibox enters keyword mode, so this histogram will be logged. Changing the keyword after entering keyword mode will re-log this metric. manukh@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com When the omnibox is focused and escape is pressed, the 1st of the following occurs: 1) If there is temporary text (i.e. a non default suggestion is selected), it is cleared. 2) If the popup is open, the popup is closed. 3) If the popup is open, which is considered as user input in progress, then the popup is closed and user input is cleared. 4) If user input is in progress, it is cleared. This state (i.e. input in progress with the popup closed) typically occurs when input was in progress, then the omnibox was blurred, and then it was refocused. 5) The omnibox is blurred. This histogram records which of the above occurred. It is recorded every time escape is pressed with the omnibox focused. Pressing escape repeatedly e.g. 10 times will emits at most 4 times until the omnibox is blurred. ender@google.com jdonnelly@chromium.org mpearson@chromium.org This records whether user initiated navigation after focusing the Omnibox versus switches focus elsewhere without navigating in the {Usage} case. This metric includes accidental focus-then-losing-focus events, including brief ones. It also includes ones in which the user did not type any text or otherwise engage with the Omnibox. E.g., the user tabbing through all top Chrome UI controls will cause this metric to be recorded. If the user switches focus from the Chrome window to another window while the Omnibox is focused, that also counts as a loss of focus. On Android variants with attachments are recorded as of M144. On Android M144-M146 the values "Navigation w/o attachments" and "No navigation with attachments" were flipped. This metric is not recorded for the Realbox interactions. Recorded every time the Omnibox focus is cleared. khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused the Omnibox and issued a cut/copy command. Recorded when the user cuts/copies all text in the Omnibox (e.g. select-all, followed by cut/copy). If the user deletes all text (a.k.a. clobber) or only cuts/copies part of the text in the Omnibox, then this metric will NOT be recorded. Also, if focus-related timing info is not available (which should be rare), then this metric will NOT be recorded. Collected on desktop platforms (Win, Mac, Linux, Chrome OS). khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused the Omnibox and issued a cut/copy command. Sliced by page context (a.k.a. page classification). Recorded when the user cuts/copies all text in the Omnibox (e.g. select-all, followed by cut/copy). If the user deletes all text (a.k.a. clobber) or only cuts/copies part of the text in the Omnibox, then this metric will NOT be recorded. Also, if focus-related timing info is not available (which should be rare), then this metric will NOT be recorded. Collected on desktop platforms (Win, Mac, Linux, Chrome OS). khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused the Omnibox and issued a cut/copy command. Sliced by zero-prefix state. Recorded when the user cuts/copies all text in the Omnibox (e.g. select-all, followed by cut/copy). If the user deletes all text (a.k.a. clobber) or only cuts/copies part of the text in the Omnibox, then this metric will NOT be recorded. Also, if focus-related timing info is not available (which should be rare), then this metric will NOT be recorded. Collected on desktop platforms (Win, Mac, Linux, Chrome OS). khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused the Omnibox and issued a cut/copy command. Sliced by zero-prefix state and page context (a.k.a. page classification). Recorded when the user cuts/copies all text in the Omnibox (e.g. select-all, followed by cut/copy). If the user deletes all text (a.k.a. clobber) or only cuts/copies part of the text in the Omnibox, then this metric will NOT be recorded. Also, if focus-related timing info is not available (which should be rare), then this metric will NOT be recorded. Collected on desktop platforms (Win, Mac, Linux, Chrome OS). jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com The length of time between when a user focused on the omnibox and opened an omnibox match (which could be what they typed or a suggestion). This is recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. It is not recorded if a match is opened without triggering a focus event, e.g., when a user drags a URL to the omnibox to navigate. To know how common this last condition is, compare the total count of this histogram to the total number of omnibox events. khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused on the omnibox and opened an omnibox match (which could be what they typed or a suggestion). Sliced by page context. This is recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. It is not recorded if a match is opened without triggering a focus event, e.g., when a user drags a URL to the omnibox to navigate. To know how common this last condition is, compare the total count of this histogram to the total number of omnibox events. khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused on the omnibox and opened an omnibox match (which could be what they typed or a suggestion). Sliced by summarized result type (SEARCH, URL, OTHER). This is recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. It is not recorded if a match is opened without triggering a focus event, e.g., when a user drags a URL to the omnibox to navigate. To know how common this last condition is, compare the total count of this histogram to the total number of omnibox events. khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused on the omnibox and opened an omnibox match (which could be what they typed or a suggestion). Sliced by summarized result type (SEARCH, URL, OTHER) and page context. This is recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. It is not recorded if a match is opened without triggering a focus event, e.g., when a user drags a URL to the omnibox to navigate. To know how common this last condition is, compare the total count of this histogram to the total number of omnibox events. khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused on the omnibox and opened an omnibox match (which could be what they typed or a suggestion). Sliced by zero-prefix state. This is recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. It is not recorded if a match is opened without triggering a focus event, e.g., when a user drags a URL to the omnibox to navigate. To know how common this last condition is, compare the total count of this histogram to the total number of omnibox events. khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused on the omnibox and opened an omnibox match (which could be what they typed or a suggestion). Sliced by zero-prefix state and page context. This is recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. It is not recorded if a match is opened without triggering a focus event, e.g., when a user drags a URL to the omnibox to navigate. To know how common this last condition is, compare the total count of this histogram to the total number of omnibox events. khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused on the omnibox and opened an omnibox match (which could be what they typed or a suggestion). Sliced by zero-prefix state and summarized result type (SEARCH, URL, OTHER). This is recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. It is not recorded if a match is opened without triggering a focus event, e.g., when a user drags a URL to the omnibox to navigate. To know how common this last condition is, compare the total count of this histogram to the total number of omnibox events. khalidpeer@chromium.org chrome-desktop-search@google.com The length of time between when a user focused on the omnibox and opened an omnibox match (which could be what they typed or a suggestion). Sliced by zero-prefix state, summarized result type (SEARCH, URL, OTHER), and page context. This is recorded regardless of whether the omnibox dropdown (a.k.a. popup) is open. It is not recorded if a match is opened without triggering a focus event, e.g., when a user drags a URL to the omnibox to navigate. To know how common this last condition is, compare the total count of this histogram to the total number of omnibox events. andypaicu@chromium.org chrome-permissions-team@google.com Recorded every time the geolocation header is attempted to be built by the GeolocationHeaderService. This happens automatically when an omnibox navigation goes to the DSE origin (if it has permission) [Automatic], or during autocomplete match generation when attempting to build the inline location suggestion [InlineSuggestion]. It records the outcome of the attempt to build the geolocation header: either success or the failure reason. andypaicu@chromium.org chrome-permissions-team@google.com Recorded every time the geolocation header service tries to retrieve the user's geoposition in preparation for it be used to construct the XGeo HTTP header. Logs the outcome of the priming attempt: either an early exit due to checks (like no default search provider, permission denied, already in progress, etc) or a successful request start (specifying if it requested a cached position only or a next position update). mahmadi@google.com chrome-desktop-search@google.com Counts the number of times a suggestion group ID is prevented form appearing in the results. This is recorded when the user hides a set of grouped suggestions, such as trending zero-suggest, in the omnibox UI using the control in the grouped suggestions' header. mahmadi@google.com chrome-desktop-search@google.com Counts the number of times a suggestion group ID is permitted to appear in the results. This is recorded when the user makes a set of previously hidden grouped suggestions, such as trending zero-suggest, visible in the omnibox UI using the control in the grouped suggestions' header. orinj@chromium.org jdonnelly-team@google.com Fuzzy match conversion produces modified matches from other synchronous autocomplete providers (sub-providers) using alternative inputs: what the user might have typed, the automatic corrections. This metric is logged once per sub-provider per omnibox input if and only if the fuzzy provider runs a search (not all omnibox inputs result in search) and finds any corrections (this includes the zero case where corrections are found but produce no matches). Logs for each fuzzy sub-provider the number of correction matches converted to fuzzy provider matches for a single omnibox input. This measures how many 'best' matches (among all the sub-provider's matches for a specific correction) are converted from this sub-provider, summed for the various corrections of a single user input (will not exceed `provider_max_matches_` even in unlikely extreme cases). This is useful in evaluating the efficacy of various sub-providers for fuzzy matching. orinj@chromium.org jdonnelly-team@google.com When a fuzzy match was offered at the moment the user opened a match, this measures whether a fuzzy suggestion was taken. This is only recorded when at least one fuzzy match is in the result set, so it is useful to measure total presence and engagement with fuzzy URL suggestions. It can be interpreted as a click through rate for fuzzy match presentation as a whole: given that any fuzzy matches were presented at the moment a match was selected by the user, how often was the selected match a fuzzy URL suggestion? Context: Fuzzy match conversion produces modified matches from other synchronous autocomplete providers (sub-providers) using alternative inputs: what the user might have typed, the automatic corrections. orinj@chromium.org jdonnelly-team@google.com The time taken by HistoryFuzzyProvider to search for fuzzy input corrections. This is measured if and only if a search is performed, so many input states will not result in recording this metric (for example if the input contains a space, that's taken as a hint that the user may be searching instead of typing a domain name so no fuzzy search is performed). It is useful to distinguish portions of the total time taken by the provider, particularly as separate from sub-provider match gathering, so that if there are any pathological cases in the search algorithm then they will be apparent here. Context: Fuzzy match conversion produces modified matches from other synchronous autocomplete providers (sub-providers) using alternative inputs: what the user might have typed, the automatic corrections. andypaicu@chromium.org chrome-permissions@google.com Recorded when an autocomplete pass completes, for Default Search Engines where the geolocation permission is set to ASK. Tracks whether an inline location suggestion was shown, or whether there was or not a eligible parent suggestion. andypaicu@chromium.org chrome-permissions@google.com Recorded when an autocomplete pass completes, for Default Search Engines where the geolocation permission is set to DENY. Tracks whether an inline location suggestion was shown, or whether there was or not a eligible parent suggestion. andypaicu@chromium.org chrome-permissions@google.com Recorded when a duplicate inline location suggestion is shown. Tracks the 0-based position index of the suggestion in the matches list. andypaicu@chromium.org chrome-permissions@google.com Recorded when the user performs a click on an inline location suggestion or its parent. Always emits true. kouhei@google.com chrome-loading@google.com Records the time taken between the OS captured input event timestamp to an URL is about to be selected. Recorded once per call to OmniboxEditModel::OpenSelection if an OmniboxAction is involved. This uses the same time origin with Omnibox.SuggestionUsed.Search.InputToNavigationStart2. See also Omnibox.InputToOpenSelection for the breakdown of input routing latency. See also Omnibox.InputToExecuteAction which covers the other branch. This histogram only records metrics on machines with high-resolution clocks. kouhei@google.com chrome-loading@google.com Records the time taken between the OS captured input event timestamp to OmniboxAction is about to be executed. Recorded once per call to OmniboxEditModel::OpenSelection if an OmniboxAction is involved. This uses the same time origin with Omnibox.SuggestionUsed.Search.InputToNavigationStart2. See also Omnibox.InputToOpenSelection for the breakdown of input routing latency. See also Omnibox.InputToAcceptNonAction which covers the other branch. This histogram only records metrics on machines with high-resolution clocks. kouhei@google.com chrome-loading@google.com Records the time taken between the OS captured input event timestamp to OmniboxEditModel::OpenSelection. Recorded once per call to OmniboxEditModel::OpenSelection. This uses the same time origin with Omnibox.SuggestionUsed.Search.InputToNavigationStart2. See also Omnibox.InputToExecuteAction and Omnibox.InputToAcceptNonAction for other breakdowns of the metric. This histogram only records metrics on machines with high-resolution clocks. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com The kind of input the user provided when using the omnibox to go somewhere. The type can be misleading. For example if the user typed 'http:/', it gets marked as a query because it cannot be opened as a URL even though the user probably wanted and selected a URL from the list of suggestions. In M-74 and earlier, this was only recorded if the user had no incognito windows open. In M-75 and later, it records all omnibox interactions regardless, in order to be consistent with how user actions and histograms are handled. gjc@chromium.org blink-network-stack@google.com The number of IPv4 address parts input by the user. The histogram is used to verify whether shortened IPv4 addresses like 127.1 are still used. This histogram is recorded when the user fully types the URL in the omnibox and the URL uses an IPv4 address or IPv4 embedded IPv6 address as the host. jdonnelly@chromium.org chrome-desktop-search@google.com Whether an omnibox interaction is a paste-and-search/paste-and-go action. (This histogram records both of these in the "True" bucket for this histogram because both of these are referred to as paste-and-go in the code.) These typically involve right-clicking in the omnibox and selecting that option from the dropdown. In M-74 and earlier, this was only recorded if the user had no incognito windows open. In M-75 and later, it records all omnibox interactions regardless, in order to be consistent with how user actions and histograms are handled. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com Whether the user deleted text immediately before selecting an omnibox suggestion. This is usually the result of pressing backspace or delete. In M-74 and earlier, this was only recorded if the user had no incognito windows open. In M-75 and later, it records all omnibox interactions regardless, in order to be consistent with how user actions and histograms are handled. mahmadi@chromium.org chrome-desktop-search@google.com `TemplateURLs` that are active at load time (usually on start up) are logged in this histogram. Each active keyword should fall into exactly 1 slice (in addition to the aggregate unsliced histogram). This only gets logged once each time the search engines are loaded from the database. If a user changes the active status of a search engine during the same browser session, the keyword counts do not get logged again. This slice counts the number of {KeywordType}. yoangela@chromium.org chrome-desktop-search@google.com Records number of times users use keyword mode enumerated by the type of search engine (whether the engine is "built-in"). {Usage} khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if the "Ask Google Lens about this page" action was offered at least once during the course of the Omnibox session. Given it was offered at least once during the session, this records whether or not the user ultimately selected the "Ask Google Lens about this page" action in the Omnibox. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. (Precision = Usage / Recall) khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if the "Ask Google Lens about this page" action was offered at least once during the course of the Omnibox session. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. (Recall = Usage / Precision) khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if the user selected the "Ask Google Lens about this page" action in the Omnibox. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. (Usage = Precision * Recall) nidhijaju@chromium.org chrome-loading@google.com The type of autocomplete match with a recommended action of "preconnect" that {PreconnectableType} in a preconnect by the loading predictor. Emitted when an autocomplete match has a recommended action of "preconnect" as a result of the text entered into the omnibox changing. mahmadi@chromium.org chrome-desktop-search@google.com The amount of time it takes to extract up to the requested number of search terms from the database for both the default and the keyword providers (if applicable) and sort them by recency to produce local prefix search suggestions. Emitted when prefix search suggestions are requested as a result of the user typing into the Omnibox or the NTP Realbox. mahmadi@chromium.org chrome-desktop-search@google.com The length of time it takes for the corresponding URLs that would produce a deleted match to be queried asynchronously and deleted. Emitted when user deletes a local history zero-prefix suggestion. mahmadi@chromium.org chrome-desktop-search@google.com The amount of time it takes to extract up to the requested number of search terms from the database and sort them by frecency to produce local zero-prefix suggestions. Emitted when zero-prefix suggestions are requested as a result of the user focusing into the Omnibox or the NTP Realbox. mahmadi@chromium.org chrome-desktop-search@google.com The length of time it takes to handle the deletion request for a match and to update the list of provider matches synchronously. Emitted when user requests to delete a local history zero-prefix suggestion. gjc@google.com chrome-loading@google.com Records the duration of LocationIconView::Update calls. Recorded when the location icon view is updated (e.g. during navigation or state changes). This metric is only reported for clients with high-resolution clocks. manukh@chromium.org jdonnelly@chromium.org This tracks how unstable omnibox matches are. Typically, each input change is followed by a single synchronous update, and then approximately 3 asynchronous updates. There may be more or less asynchronous updates depending on which providers are enabled for the particular platform/user, the input (e.g. some providers don't run for 0-length inputs), and how quickly the input changes occur (e.g. if the inputs update rapidly, slower async providers won't have time to provide updates before they're aborted by newer inputs). For each autocomplete update, this histogram logs whether any match position changes. If 1 or more matches changed, logs true once; otherwise false once. When the number of matches changes, matches that are removed are considered a 'change', while matches that are appended are less disruptive to the user and not considered a 'change'. This is because this metric is primarily interested in how many times the user could be looking at a match with the intention of selecting it, and then it surprisingly goes away. Note that merely adding a new provider will increase these counts. That's intentional. Swapping matches out annoys users, and to avoid this, we should do some things like: caching, update coalescing, update deferral until next keystroke, provider timeouts, etc. This metric is designed to be normalized by the True count of Omnibox.Start.WantAsyncMatches, which will yield the number of match changes per keystroke or other user gesture. There're the related Omnibox.MatchStability2.InAnyPosition.* slices for tracking match instability for all, asynchronous, and synchronous updates. This histogram can be considered a boolean analogue to the Omnibox.MatchStability2.Index.* histogram which tracks which matches changed. {OmniboxAutocompleteUpdateSlice} manukh@chromium.org jdonnelly@chromium.org This tracks how unstable omnibox matches are. Typically, each input change is followed by a single synchronous update, and then approximately 3 asynchronous updates. There may be more or less asynchronous updates depending on which providers are enabled for the particular platform/user, the input (e.g. some providers don't run for 0-length inputs), and how quickly the input changes occur (e.g. if the inputs update rapidly, slower async providers won't have time to provide updates before they're aborted by newer inputs). For each match change, this histogram logs the index of the match change. Match changes occur when any match position changes; i.e. is set to a new match different from the old match in that position, even if the new match was contained in the old matches set. If multiple matches change in a single autocomplete update, logs each. If none change in a single autocomplete update, this histogram is not logged. We primarily care about the default match, which is logged at index 0. All indices matter though, so we track the other indices too. When the number of matches changes, matches that are removed are considered a 'change', while matches that are appended are less disruptive to the user and not considered a 'change'. This is because this metric is primarily interested in how many times the user could be looking at a match with the intention of selecting it, and then it surprisingly goes away. Note that merely adding a new provider will increase these counts. That's intentional. Swapping matches out annoys users, and to avoid this, we should do some things like: caching, update coalescing, update deferral until next keystroke, provider timeouts, etc. This metric is designed to be normalized by the True count of Omnibox.Start.WantAsyncMatches, which will yield the number of match changes per keystroke or other user gesture. There're the related Omnibox.MatchStability2.Index.* slices for tracking match instability for all, asynchronous, and synchronous updates. There's the related Omnibox.MatchStability2.InAnyPosition histogram for tracking whether any match changed per autocomplete update. {OmniboxAutocompleteUpdateSlice} pnoland@google.com ender@google.com chrome-mobile-search@google.com Records the reason AI Mode was activated in the Mobile Fusebox: * Explicitly via the tool menu * Explicitly via a dedicated button * Implicitly due to the addition of attachment This is only recorded when transitioning to AI Mode from some other state. skym@chromium.org chrome-mobile-search@google.com Records the amount of time between when the user choose to add an attachment, and when it was abandoned. Being abandoned might mean the user removed the attachment, or navigated, or backed out of the UI. Note that abandonment, success, and failure are exclusive outcomes, only one will be reported. skym@chromium.org chrome-mobile-search@google.com Records the amount of time between when the user choose to add an attachment, and when it was abandoned. Being abandoned might mean the user removed the attachment, or navigated, or backed out of the UI. Scoped to a particular button type. Note that abandonment, success, and failure are exclusive outcomes, only one will be reported. pnoland@google.com ender@google.com chrome-mobile-search@google.com Records which attachment buttons were shown when the attachments popup was opened. Recorded once per popup open. Originally triggered when the popup was hidden instead of shown, through the plus button. This is very difficult to actaully do, most hidden is not from plus button, but other inputs. Do not trust data before the M-148 (likely merged to M-147) fix. pnoland@google.com ender@google.com chrome-mobile-search@google.com Counts attachment button clicks, enumerated by the type of button. Recorded once per button click. pnoland@google.com ender@google.com chrome-mobile-search@google.com Records whether a given attachment button was used or not during an omnibox session. Recorded when the omnibox session ends only for buttons that were shown to the user. mreichhoff@chromium.org chrome-mobile-search@google.com The number of attachments of the specified type attached to the query when the user submits navigation. skym@chromium.org chrome-mobile-search@google.com Records the amount of time between when the user choose to add an attachment, and when it failed to upload. Note that abandonment, success, and failure are exclusive outcomes, only one will be reported. skym@chromium.org chrome-mobile-search@google.com Records the amount of time between when the user choose to add an attachment, and when it failed to upload. Scoped to a particular button type. Note that abandonment, success, and failure are exclusive outcomes, only one will be reported. jkoblinsky@google.com chrome-mobile-search@google.com Records whether an OutOfMemoryError was encountered while trying to read and prepare a {FuseboxAttachmentFileType} attachment for upload. There is a unique histogram for each file type (Audio, Image, PDF, ...), and a general aggregate total histogram for all file types. A value is emitted when we attempt to fetch the data of an attachment. This attempt occurs immediately after the Android file/gallery picker is closed via selection, and before the attachment is added to the Omnibox toolbar or uploaded to the server. It records true once if at least one OutOfMemoryError is thrown. It records false if no OutOfMemoryError is thrown, even if the fetch fails for another reason (e.g. IOException). At most one emission occurs per upload attempt. Note that duplicate files will result in separate emissions. jkoblinsky@google.com chrome-mobile-search@google.com Records the result of the size limit check for a Fusebox file attachment. (whether it is under the limit or exceeds the limit on metered or unmetered networks), where exceeding the limit for a given file type and network condition will result in the file not being attached (or sent to the server). A value is emitted when the user selects a file from the file picker, or when they confirm their selection of multiple files from the file picker. In the case of multiple files, a value will be independently emitted for each selected file. Attaching the same file twice will result in duplicate emissions. An emission will certainly occur if the file is ultimately attached, and thus appears as an attachment chip. An emission will still occur even if the file is ultimately not attached on the client side (e.g., because its content cannot be read from disk or upload fails later), given that the title, mime type, and size can be resolved. If the title, mime type, or size cannot be resolved, then no emission will occur. An emission will still occur if the user dismisses the omnibox before the file is uploaded to the server, that is, the omnibox is dismissed while the loading spinner is shown. An emission will not occur if the user dismisses the file picker without selecting any files. At most one emission will occur per file attachment attempt. So, e.g., if a file is so large that it would exceed the size limit on both metered and unmetered networks, but the user is on a metered network, a value will be emitted for the metered network case, but not for the unmetered network case. pnoland@google.com ender@google.com chrome-mobile-search@google.com Records whether the attachments popup button was clicked or not during an omnibox session. Recorded when the omnibox session ends. pnoland@google.com ender@google.com chrome-mobile-search@google.com Counts the number of times the user deliberately toggled the attachments popup on or off. Does not count popup dismissals as the result of attaching an item. skym@chromium.org chrome-mobile-search@google.com Records the amount of time between when the user choose to add an attachment, and when it succeeded uploading. Note that abandonment, success, and failure are exclusive outcomes, only one will be reported. skym@chromium.org chrome-mobile-search@google.com Records the amount of time between when the user choose to add an attachment, and when it succeeded uploading. Scoped to a particular button type. Note that abandonment, success, and failure are exclusive outcomes, only one will be reported. pnoland@google.com ender@google.com chrome-mobile-search@google.com Records the autocomplete request type at the time of leaving the omnibox. Recorded when the omnibox is left without navigating. pnoland@google.com ender@google.com chrome-mobile-search@google.com Records the autocomplete request type at the time of navigation. Recorded when the omnibox is used to navigate. skym@chromium.org chrome-mobile-search@google.com Records the error type when a context (attachment) upload fails. Emitted when the upload transitions to a terminal failure state (validation failure, upload failure, or upload expiration) after a user attempts to add an attachment (e.g. by choosing a file, capturing an image, or adding a tab) in the Composebox. This is recorded once per failed upload attempt. If an upload fails and is retried, subsequent failures will trigger additional emissions. It is not emitted if the upload succeeds, or if the user manually removes the pending attachment before the failure is reported. Adding the same attachment repeatedly will trigger subsequent emissions for each attempt. skym@chromium.org chrome-mobile-search@google.com Records the status of a context (attachment) upload. Emitted on every status change reported by the backend for an active upload, starting when the user adds an attachment (e.g. file, image, tab) in the Composebox. This includes intermediate states (processing, upload started) and terminal states (success, validation failed, upload failed, expired). Emitted multiple times per attachment upload (once for each transition). If the user manually removes the attachment before the upload finishes, no further status changes for that upload are recorded. Adding the same attachment repeatedly triggers subsequent emissions for each attempt. thegreenfrog@chromium.org ericekey@google.com Records the type of content (Text, Image, Tab, PDF, or Unknown) that is dragged and dropped into the Composebox, categorized by specific content type. Recorded for each processed item from a drag-and-drop action into the Composebox. {ComposeboxDragAndDropType} jkoblinsky@google.com chrome-mobile-search@google.com Records the size of the Fusebox file attachment. There is a unique histogram for each file type (Audio, Image, PDF, ...), and a general agregate total histogram for all file types. A value is emitted to both the general histogram and a specific file type histogram when the user selects a file from the file picker, or when they confirm their selection of multiple files from the file picker. In the case of multiple files, a value will be independently emmited for each selected file. Attaching the same file twice will result in duplicate emissions. An emmision to both histograms will certainly occur if file is ultimately attached, and thus appears as an attachment chip. An emmission will still occur even if the file is ultimately not attached on the client side (e.g., because it's title cannot be resolved), given that the size and mime type can be resolved. If either the size or mime type cannot be resolved, then no emmission will occur. An emmission will still occur if the file exceeds the size limit (an error message is shown). An emmission will still occur if the user dismisses the omnibox before the file is uploaded to the server, that is, the omnibox is dismissed while the loading spinner is shown. An emmission will not occur if the user dismisses the file picker without selecting any files. mreichhoff@chromium.org chrome-mobile-search@google.com The number of files attached to the query when the user selects a file. mreichhoff@chromium.org chrome-mobile-search@google.com The number of images attached to the query when the user selects an image. skym@chromium.org chrome-mobile-search@google.com Records the active model when a AI Omnibox session is ended. The model id comes from the server driven config. skym@chromium.org chrome-mobile-search@google.com Records the active model when a AI Omnibox session turns into a navigation. The model id comes from the server driven config. skym@chromium.org chrome-mobile-search@google.com Records the model that is selected when the user interacts with a model button on the popup. This may or may not be the model used to fulfill a subsequent query. The model id comes from the server driven config. skym@chromium.org chrome-mobile-search@google.com Records all of the ai mode models that are shown as options when the popup appears. The model id comes from the server driven config. erahmaoui@google.com chrome-mobile-search@google.com The number of Drive files attached to the query when the user selects a Drive file. ameurhosni@google.com chrome-mobile-search@google.com Records the number of tabs attached via the Fusebox tab picker. Recorded when the user explicitly selects tabs and taps the attach button to include them in the Fusebox attachments. stkhapugin@google.com chrome-mobile-search@google.com Records whether the user edited the text in the Fusebox input plate before entering AI Mode. Recorded when AI Mode is activated. skym@chromium.org chrome-mobile-search@google.com Records the tool mode whenever it is selected by the user in the AI Mode popup. This may or may not be the tool used to fulfill a subsequent query. The tool id comes from the server driven config. skym@chromium.org chrome-mobile-search@google.com Records all of the AI tool modes that are shown as options when the popup appears. The tool id comes from the server driven config. niharm@google.com chrome-desktop-search@google.com The amount of time for QueryMostVisitedURLs() to invoke its callback in the Most Visited Sites Provider. Only recorded when the history service callback is invoked when the provider is configured to query the HistoryService directly to update its set of most visited sites rather than querying TopSites to get its set of most visited sites. Currently only recorded on Desktop. niharm@google.com chrome-desktop-search@google.com Records the number of results returned from HistoryService's QueryMostVisitedURLs() in the Most Visited Sites provider. Only recorded when the provider is configured to query the HistoryService directly to update its set of most visited sites rather than querying TopSites to get its set of most visited sites. Currently only recorded on Desktop. niharm@google.com chrome-desktop-search@google.com Records the number of results requested from HistoryService's QueryMostVisitedURLs() in the Most Visited Sites provider. Only recorded when the provider is configured to query the HistoryService directly to update its set of most visited sites rather than querying TopSites to get its set of most visited sites. Currently only recorded on Desktop. mercerd@google.com chrome-desktop-search@google.com The length of time between a DOMContentLoaded event and the suggest popup being shown to the user. Recorded the first time the the omnibox popup is opened after a DOMContentLoaded loaded. Only recorded on the first omnibox popup shown after a navigation. Subsequent omnibox openings are ignored. If the user focused the omnibox before the main document element was available, this metric will not be recorded. Each tab keeps track of its own page change events and omnibox popup open events, meaning if the user opens multiple tabs and opens the omnibox popup on each one, this metric will be recorded multiple times. mercerd@google.com chrome-desktop-search@google.com The length of time between a DOMContentLoaded event and the suggest popup being shown to the user. Recorded the first time the the omnibox popup is opened after a DOMContentLoaded event. Only recorded on the first omnibox popup shown after a navigation. Subsequent omnibox openings are ignored. If the user focused the omnibox before the main document element was available, this metric will not be recorded. Each tab keeps track of its own DOMContentLoaded events and omnibox popup open events, meaning if the user opens multiple tabs and opens the omnibox popup on each one, this metric will be recorded multiple times. Sliced by page context to help better understand the latency budget for different page types. mercerd@google.com chrome-desktop-search@google.com The length of time between a the main document element being available and the suggest popup being shown to the user. The main document element is available when the HTML has finished parsing and window.document is available. Recorded the first time the the omnibox popup is opened after a main document element available event. Only recorded on the first omnibox popup shown after a navigation. Subsequent omnibox openings are ignored. If the user focused the omnibox before the main document element was available, this metric will not be recorded. Each tab keeps track of its own main document element available events and omnibox popup open events, meaning if the user opens multiple tabs and opens the omnibox popup on each one, this metric will be recorded multiple times. mercerd@google.com chrome-desktop-search@google.com The length of time between a the main document element being available and the suggest popup being shown to the user. The main document element is available when the HTML has finished parsing and window.document is available. Recorded the first time the the omnibox popup is opened after a main document element available event. Only recorded on the first omnibox popup shown after a navigation. Subsequent omnibox openings are ignored. If the user focused the omnibox before the main document element was available, this metric will not be recorded. Each tab keeps track of its own main document element available events and omnibox popup open events, meaning if the user opens multiple tabs and opens the omnibox popup on each one, this metric will be recorded multiple times. Sliced by page context to help better understand the latency budget for different page types. mercerd@google.com chrome-desktop-search@google.com The length of time between a page change event and the suggest popup being shown to the user. Recorded the first time the the omnibox popup is opened after a page change event. Only recorded on the first omnibox popup shown after a navigation. Subsequent omnibox openings are ignored. If the user focused the omnibox before the main document element was available, this metric will not be recorded. Each tab keeps track of its own page change events and omnibox popup open events, meaning if the user opens multiple tabs and opens the omnibox popup on each one, this metric will be recorded multiple times. mercerd@google.com chrome-desktop-search@google.com The length of time between a page change event and the suggest popup being shown to the user. Recorded the first time the the omnibox popup is opened after a page change event. Only recorded on the first omnibox popup shown after a navigation. Subsequent omnibox openings are ignored. If the user focused the omnibox before the main document element was available, this metric will not be recorded. Each tab keeps track of its own page change events and omnibox popup open events, meaning if the user opens multiple tabs and opens the omnibox popup on each one, this metric will be recorded multiple times. Sliced by page context to help better understand the latency budget for different page types. christianxu@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Logged only when non-trivial suggestions were shown. Logs whether a non-trivial suggestion was selected (True) or a verbatim suggestion was selected (False), sliced by the active AIM model mode at submission time. This metric is only recorded when the active AIM model is explicitly specified (i.e., not Unspecified). christianxu@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Logged only when non-trivial suggestions were shown. Logs whether a non-trivial suggestion was selected (True) or a verbatim suggestion was selected (False), sliced by the active AIM tool mode at submission time. This metric is only recorded when the active AIM tool is explicitly specified (i.e., not Unspecified). christianxu@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Logged only when non-trivial suggestions were shown. Logs whether a non-trivial suggestion was selected (True) or a verbatim suggestion was selected (False), sliced by the combination of active AIM tool mode and model mode. This metric is only recorded when the active AIM tool and model is explicitly specified (i.e., not Unspecified). christianxu@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Logs whether non-trivial (non-verbatim) suggestions were shown (True) or not (False) for a submitted query, sliced by the AIM model mode that was active. This metric is only recorded when the active AIM model is explicitly specified (i.e., not Unspecified). christianxu@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Logs whether non-trivial (non-verbatim) suggestions were shown (True) or not (False) for a submitted query, sliced by the AIM tool mode that was active. This metric is only recorded when the active AIM tool is explicitly specified (i.e., not Unspecified). christianxu@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Logs whether non-trivial (non-verbatim) suggestions were shown (True) or not (False) for a submitted query, sliced by the combination of AIM tool mode and model mode that were active. This metric is only recorded when the active AIM tool and model is explicitly specified (i.e., not Unspecified). ender@google.com woa-performance-bugs+jank@google.com Records the number of characters visible in the omnibox. Recorded once per call to UrlBar.calculateVisibleHint(). manukh@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com How many calculator matches where shown. Includes matches from both the search and calculator providers. Logged after deduping, so duplicate matches from the search and calc provider won't be double counted. Logged after culling, so matches that were generated but not shown are not counted. Logged when the last provider calls `OnProviderUpdate()`. So autocomplete calls with `omit_asynchronous_matches` true (i.e. classification calls) won't log this. Likewise, interrupted autocompleted passes (i.e. when the user is typing faster than the slowest async provider) won't log this. The search and calculator providers are on the slow end of async providers; so if they complete, it's likely this will be logged. Logged once per input (whose last autocomplete pass completed). Not logged once per autocomplete pass or once per omnibox selection. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com The number of terms in the text the user entered in the omnibox when they used the omnibox to go somewhere. Terms are defined by splitting on whitespace. All values larger than 6 are recorded in bucket 6. In M-74 and earlier, this was only recorded if the user had no incognito windows open. In M-75 and later, it records all omnibox interactions regardless, in order to be consistent with how user actions and histograms are handled. cechen@google.com suggest-2g@google.com Recorded once when OnDeviceHeadProvider is run and the provider calls the on device brain model. Records the latency for the brain model to generate predictions for a given prefix, in unit millisecond. cechen@google.com suggest-2g@google.com Recorded once when OnDeviceHeadProvider is run and the provider calls the on device brain model. Records how many predictions the brain model generates for a given prefix. cechen@google.com suggest-2g@google.com Recorded once for each prediction when OnDeviceHeadProvider is run and the provider calls the on device brain model to generate predictions for a given prefix. Records the length of each prediction respectively. juanmojica@google.com mercerd@google.com chrome-desktop-search@google.com Recorded once when the omnibox suggestion popup is opened. Records the current page paywall signal status as of the time the popup was opened. Records the paywall signal if its present, or unavailable if the APC was not available when the popup opened. This does not indicate that contextual suggestions were shown or hidden. manukh@google.com chrome-desktop-search@google.com Records what keyboard modifiers were used to alter the way the match opens. E.g. "alt+return" to open the match in a new foreground tab. Recorded once each time the user presses "return" in the omnibox. Recorded when the user presses "return" to open a match. The keyboard modifiers do affect how the match is opened. Recorded when the user presses "return" to open a pedal. The keyboard modifiers sometimes affect how the pedal is opened, but sometimes don't; e.g. modifiers don't affect the "open incognito window" pedal. Recorded when the user presses "return" to activate the "switch to tab" chip. The keyboard modifiers do not affect how tab switch behaves. Recorded when the user presses "return" on a match that does not navigate or perform an action (e.g. empty keyword inputs, instant keyword matches, or null match). The keyboard modifiers do not have an effect. Not recorded when the user mouse clicks or gestures to open a match. The keyboard modifiers do not affect how the match is opened. Does not record modifiers ignored in determining match opening. E.g., "option+return" and "option+command+return" both open the match in a new foreground tab and both record the same value. This case of ignored modifiers only occurs on mac with the ("option+return" and "option+command+return") pair and their +shift and +ctrl variants. This metric uses the key names used in the code rather than the names used commonly on each OS. E.g. linux's "super" is coded as "command" in chrome. The user pressing "super+return" will log "command+return" instead. manukh@chromium.org mpearson@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Records the time to paint the omnibox contents. This is a subcomponent of Omnibox.CharTypedToRepaintLatency. Implemented on desktop platforms. jdonnelly@chromium.org chrome-desktop-search@google.com The number of paste commands on the text in the omnibox. Reported every time a paste command is done. jdonnelly@chromium.org orinj@chromium.org chrome-desktop-search@google.com Counts the type (concept ID) of omnibox pedals shown when the user used the omnibox to go somewhere. Pedals are a button attached to a search suggestion that either navigate to a chrome:// URL or trigger a Chrome action (for example, opening the page translation dialog or opening a new window in Incognito mode). Note that, while it is uncommon, it is possible for multiple pedals to be shown at one time so this can't be used as a count of how many times a pedal or pedals were present. This histogram is related to Omnibox.SuggestionUsed.Pedal. Starting with Chrome/Android M142 this histogram is recorded whenever the Omnibox is used to navigate somewhere, closely matching how other Omnibox histograms are recorded. Before M142 this histogram would be recorded any time the Omnibox interaction has completed, whether the user initiated navigation or not. mahmadi@chromium.org kylixrd@chromium.org chrome-desktop-search@google.com Records the time between the AI Mode WebUI page load which happens when the popup presenter is constructed and the first time the popup widget is shown. Given that the AI Mode WebUI page begins the asynchronous process of loading its resources, initialization, and binding immediately after it is loaded, this metric can be seen as a time budget for the AI Mode WebUI page remote to be bound and ready to receive calls. Recorded at most once per browser window. Recorded the very first time the AI Mode WebUI Omnibox popup is shown to the user during the course of a browser session (i.e. subsequent show-popup operations in the same browser window DO NOT log this histogram). avivkiss@chromium.org kylixrd@chromium.org chrome-desktop-search@google.com Records whether the renderer process has crashed and the contents is being reloaded before showing the WebUI AI Mode popup. Recorded every time the AI Mode WebUI Omnibox popup web content is shown. avivkiss@chromium.org kylixrd@chromium.org chrome-desktop-search@google.com Records the termination status of the AI Mode Popup WebUI renderer process when it goes away, whether due to normal termination or a process crash. This helps monitor crash rates and types. khalidpeer@chromium.org mahmadi@chromium.org chrome-desktop-search@google.com Records the time between the Full WebUI page load which happens when the omnibox popup presenter is constructed and the first time the popup widget is shown. Given that the Full WebUI page begins the asynchronous process of loading its resources, initialization, and binding immediately after it is loaded, this metric can be seen as a time budget for the WebUI page remote to be bound and ready to receive calls. Recorded at most once per browser window. Recorded the very first time the full WebUI Omnibox popup is shown to the user during the course of a browser session (i.e. subsequent show-popup operations in the same browser window DO NOT log this histogram). khalidpeer@chromium.org avivkiss@chromium.org chrome-desktop-search@google.com Records whether the renderer process has crashed and the contents is being reloaded before showing the Full WebUI Omnibox popup. Recorded every time the full WebUI Omnibox popup web content is shown. khalidpeer@chromium.org avivkiss@chromium.org chrome-desktop-search@google.com Records the termination status of the Full WebUI Omnibox Popup renderer process when it goes away, whether due to normal termination or a process crash. This helps monitor crash rates and types. mych@chromium.org ryanakiyama@chromium.org chrome-desktop-search@google.com Records the number of times the Views popup was shown but not being able to record the Omnibox.Popup.ResultToContentReady metric due to various early exit reasons. mych@chromium.org ryanakiyama@chromium.org chrome-desktop-search@google.com Measures the latency from when the Omnibox controller receives a new set of results to when the popup is rendered and visible for the very first time after popup creation. Recorded at most once per popup lifetime. The starting point is when the controller receives autocomplete results and begins updating the UI. The end point is when content is ready (compositor presentation for Views). mych@chromium.org ryanakiyama@chromium.org chrome-desktop-search@google.com Measures the latency from when the Omnibox controller receives a new set of results to when the popup is rendered and visible. Recorded every time the popup transitions from closed to open. The starting point is when the controller receives autocomplete results and begins updating the UI. The end point is when content is ready (compositor presentation for Views). mahmadi@chromium.org chrome-desktop-search@google.com Records the time between the WebUI page load which happens when the omnibox popup presenter is constructed and the first time the popup widget is shown. Given that the WebUI page begins the asynchronous process of loading its resources, initialization, and binding immediately after it is loaded, this metric can be seen as a time budget for the WebUI page remote to be bound and ready to receive calls. Recorded at most once per browser window. Recorded the very first time the classic WebUI Omnibox popup is shown to the user during the course of a browser session (i.e. subsequent show-popup operations in the same browser window DO NOT log this histogram). avivkiss@chromium.org chrome-desktop-search@google.com Records whether the renderer process has crashed and the contents is being reloaded before showing the classic WebUI Omnibox popup. Recorded every time the classic WebUI Omnibox popup web content is shown. mahmadi@chromium.org chrome-desktop-search@google.com Records whether WebUI page remote is bound and ready to receive calls when the WebUI Handler attempts to make its first call to the WebUI Page. Recorded at most once per browser window. avivkiss@chromium.org chrome-desktop-search@google.com Records the termination status of the Omnibox WebUI renderer process when it goes away, whether due to normal termination or a process crash. This helps monitor crash rates and types. mahmadi@chromium.org chrome-desktop-search@google.com Records the time between AutocompleteController::Observer's OnResultChanged is called and the time when the <cr-searchbox-dropdown> is ready to render the results. If there are multiple calls to OnResultChanged before the results are rendered, logs the time since the earliest. This is Comparable to Omnibox.WebUI.CharTypedToRepaintLatency.ToPaint but excludes the time taken to send the input to the browser and process it. Similarly this does not take into account the time the DOM change task spends in the message loop nor its duration. mahmadi@chromium.org chrome-desktop-search@google.com Records the duration it took for the visual state callback to be called (or fallback timeout to be reached) during a deferred show of the {WebUIType} popup, for every show of the popup. mahmadi@chromium.org chrome-desktop-search@google.com Records the duration it took for the visual state callback to be called (or fallback timeout to be reached) during a deferred show of the {WebUIType} popup, for the first show of the popup. mahmadi@chromium.org chrome-desktop-search@google.com Records whether the deferred show of the {WebUIType} popup was triggered by the fallback timer task (True) or the visual state callback (False), for every show of the popup. mahmadi@chromium.org chrome-desktop-search@google.com Records whether the deferred show of the {WebUIType} popup was triggered by the fallback timer task (True) or the visual state callback (False), for the first show of the popup. mych@chromium.org ryanakiyama@chromium.org chrome-desktop-search@google.com Records the reason for early exit when the ResultToContentReady latency cannot be recorded for the {WebUIType} popup. Metrics for the AIM popup will not be recorded because it's triggered via explicit user interaction versus an async autocomplete result delivery. mych@chromium.org ryanakiyama@chromium.org chrome-desktop-search@google.com Records the latency from when the popup results are updated to the first visual state change of the {WebUIType} popup on the first show. Metrics for the AIM popup will not be recorded because it's triggered via explicit user interaction versus an async autocomplete result delivery. ryanakiyama@chromium.org chrome-desktop-search@google.com Records the latency from when the popup results are updated to the first visual state change of the {WebUIType} popup. Metrics for the AIM popup will not be recorded because it's triggered via explicit user interaction versus an async autocomplete result delivery. mahmadi@chromium.org ryanakiyama@chromium.org chrome-desktop-search@google.com Record the time between the request of the {WebUIType} widget to show and when the first frame is painted by the widget on the screen, for every show of the popup. mahmadi@chromium.org ryanakiyama@chromium.org chrome-desktop-search@google.com Record the time between the first request of the {WebUIType} widget to show and when the first frame is painted by the widget on the screen, for the first show of the popup. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com The length of time taken by the {OmniboxProvider}Provider's synchronous pass. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com Time it takes for the omnibox to become responsive to user input after the user has typed N characters (for 'Omnibox.QueryTime2.N') or any length input (for 'Omnibox.QueryTime2'). This measures the time it takes to start all autocomplete providers (but not wait for the asynchronous ones to finish). {QueryTimeSuffix} manukh@chromium.org chrome-desktop-search@google.com Emits the position of any "Resume Journey" omnibox actions shown in the popup. The position index is 0-based, so an action shown in the topmost match is logged as value 0, consistent with Omnibox.SelectedPosition. Note that these are emitted when the user uses the omnibox to go somewhere. When that happens, one count is emitted per action visible in the popup. These are NOT emitted per-keystroke, in order to make this a suitable denominator for Omnibox.SuggestionUsed.ResumeJourney. junzou@chromium.org chrome-intelligence-core@google.com Emits the type of the matched cluster keyword of any "Resume Journey" omnibox actions shown in the popup. The types indicate the sources from which the keywords are generated in the history clustering backend. Note that these are emitted when the user uses the omnibox to go somewhere. When that happens, one keyword type is emitted per action visible in the popup. These are NOT emitted per-keystroke, in order to make this a suitable denominator for Omnibox.SuggestionUsed.ResumeJourney.ClusterKeywordType. manukh@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Measures the number of sessions for which each type of rich autocompletion triggered; does not measure the number of times each type of rich autocompletion triggered. As the user types into the omnibox, the omnibox suggestions are updated. Some of those suggestions may have rich autocompletion. No suggestion may have multiple types of rich autocompletion. A type of rich autocompletion is considered triggered only if the default suggestion has rich autocompletion. If a non-default suggestion has rich autocompletion, does not suffice. If any input during the session triggered a rich autocompletion type, that type is considered triggered for the entire session. Recorded multiple times per omnibox session (i.e. per user selecting a suggestion). Recorded once for each type of rich autocompletion that triggered during the session (i.e. while the user was typing their input). If a rich autocompletion type triggered multiple times during the session (very common), it will be logged exactly once. Hence, it's impossible for any single bucket's count to be larger than the count of omnibox sessions or Omnibox.RichAutocompletion.Triggered.Any. If multiple rich autocompletion types triggered during the session (less common), each will be logged. Hence, it's possible for the total count of this histogram to be larger than the count of omnibox sessions. manukh@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Measures the number of sessions for which any type of rich autocompletion triggered. As the user types into the omnibox, the omnibox suggestions are updated. Some of those suggestions may have rich autocompletion. No suggestion may have multiple types of rich autocompletion. A type of rich autocompletion is considered triggered only if the default suggestion has rich autocompletion. If a non-default suggestion has rich autocompletion, does not suffice. If any input during the session triggered a rich autocompletion type, that type is considered triggered for the entire session. The related "Omnibox.RichAutocompletion.Triggered" histogram breaks down the trigger count for each rich autocompletion type. Recorded exactly once per omnibox session (i.e. per user selecting a suggestion). ender@google.com woa-performance-bugs+jank@google.com Measures the amount of time it takes to call UrlBar.scrollToTLD(). Logged once per call. Note: There is a recording gap between: 2026.03-2026.08. ender@google.com chrome-desktop-search@google.com Whenever Ctrl+Enter is used to complete an interaction with the Omnibox, this metric captures whether the keystroke was used to initiate navigation to a website (by affixing ".com") or execute a search query (if affixing ".com" would not produce a valid URL). Recorded each time Ctrl+Enter is used to complete an interaction. Note: There is a recording gap between: 2026.07-2026.08. ender@google.com chrome-desktop-search@google.com Whether Ctrl+Enter key combination was used to complete an interaction with the Omnibox. Recorded each time user accepts Omnibox text via Keyboard. Note: There is a recording gap between: 2026.07-2026.08. jdonnelly@chromium.org roagarwal@chromium.org chrome-incognito@google.com This histogram records the number of searches done from omnibox using default search engine on desktop and android devices, sliced based on being in regular mode or private modes. andypaicu@chromium.org chrome-desktop-search@google.com Records whether the X-Geo HTTP header was attached to a search request originating from the omnibox. Emitted when the network loader throttle processes WillStartRequest or WillRedirectRequest for default search engine search requests. mahmadi@chromium.org chrome-desktop-search@google.com Records the length of the gs_lcrp= param in the Search Result Page request URLs. Recorded every time a Search Result Page URL is generated in the omnibox/realbox. This happens either when the user selects a suggestion in order to load Search Result Page or when a proactive request is made to prefetch the Search Result Page. jdonnelly@chromium.org wfh@chromium.org chrome-desktop-search@google.com The type of search engine associated with a match opened from the omnibox, recorded after all navigations (including server redirects) have completed. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com The type of search engine associated with a match opened from the omnibox. {Population} lingqi@chromium.org chrome-prerendering@google.com Records the network error code from the completion status when a search prefetch request using CacheAliasSearchPrefetchURLLoader completes. This is recorded in CacheAliasSearchPrefetchURLLoader::OnComplete. net::OK (value 0) is recorded on success. This helps monitor network failures for search prefetches that are aliased in the cache. lingqi@chromium.org chrome-prerendering@google.com Records the final stage of a keep-alive request for search prefetch activated pages. Recorded when the SearchPrefetchKeepAliveRequestTracker is destroyed. ryansturm@chromium.org chrome-desktop-search@google.com Records whether a "search what you type" omnibox navigation was also a {HistoryOrSuggest} type. Recorded when the user navigates to a search via typing the full query into the omnibox. gjc@google.com chrome-prerendering@google.com Records whether the resource response is available when the prefetch response is taken from the memory cache. This histogram helps understand the critical path of loading if a prefetch is triggered. The result determines if the navigation itself or the prefetch is in the critical path. lingqi@chromium.org ryansturm@chromium.org chrome-prerendering@google.com Recorded when posting a task to destroy StreamingSearchPrefetchURLLoader. Used to track whether the native forwarding works as expected. Together with Omnibox.SearchPreload.ForwardingResult.WasServedToPrerender, these two metrics are used to monitor whether shareable cache does not break the forwarding logic. lingqi@chromium.org ryansturm@chromium.org chrome-prerendering@google.com Recorded when posting a task to destroy StreamingSearchPrefetchURLLoader. Together with Omnibox.SearchPreload.ForwardingResult.NotServedToPrerender, these two metrics are used to monitor whether shareable cache does not break the forwarding logic. lingqi@chromium.org ryansturm@chromium.org chrome-prerendering@google.com Tracks whether the StreamingSearchPrefetchURLLoader::ResponseReader can successfully serving to prerender clients. Recorded when a `StreamingSearchPrefetchURLLoader::ResponseReader` is destroyed. mpearson@chromium.org jdonnelly@chromium.org cch@chromium.org Counts the number of requests SearchProvider sent, were invalidated, and were completed successfully. jdonnelly@chromium.org Whether asynchronous matches are requested. Recorded every time AutocompleteController::Start() is called. False counts roughly correspond to non-interactive invocations of AutocompleteController - like when we are classifying user text as a Search or URL. True counts roughly correspond to keystrokes or on-focus events, and can be used as a normalizer for per-user-gesture metrics. khalidpeer@chromium.org chrome-desktop-search@google.com When the user makes an omnibox selection to go somewhere, this records whether each (summarized) type of suggestion was shown at least once during the course of the Omnibox session. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. khalidpeer@chromium.org chrome-desktop-search@google.com When the user makes an omnibox selection to go somewhere, this records whether each (summarized) type of suggestion was shown at least once during the course of the Omnibox session. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. Sliced by page context in order to allow us to answer questions like: Did the user see at least one Search/URL suggestion, during the course of the Omnibox session, when they selected a suggestion in the given page context? mahmadi@google.com chrome-desktop-search@google.com Records which suggestion URL was selected. khalidpeer@chromium.org chrome-desktop-search@google.com When the user makes an omnibox selection to go somewhere, this records whether each (summarized) type of suggestion was shown at least once during the course of the Omnibox session. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. Sliced by zero-prefix state in order to allow us to answer questions like: Did the user see at least one zero-prefix/typed Search/URL suggestion during the course of the Omnibox session? khalidpeer@chromium.org chrome-desktop-search@google.com When the user makes an omnibox selection to go somewhere, this records whether each (summarized) type of suggestion was shown at least once during the course of the Omnibox session. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. Sliced by zero-prefix state and page context in order to allow us to answer questions like: Did the user see at least one zero-prefix/typed Search/URL suggestion, during the course of the Omnibox session, when they selected a suggestion in the given page context? jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com Counts how often omnibox suggestions are used, and in the case an Answer suggestion was selected - records the type of an answer. This histogram is useful because there is no distinct suggestion type recorded for answers so their use is not recorded by Omnibox.SuggestionUsed.ProviderAndResultType. nyquist@chromium.org ssid@chromium.org chrome-segmentation-platform@google.com For each user navigation using the omnibox, logs the selected omnibox result as one of a limited set of result types, based on the autocomplete match. As an example, HISTORY_URL and HISTORY_TITLE are both summarized into the Url summarized result type. This histogram intended to match the server-side histograms that use OmniboxSummarizedResultType such as Omnibox.SuggestionUsed.SearchVsUrl. This is also calculated on the client side to enable functionality that is based on listening to local metrics at runtime. Logged whenever a user navigates using the omnibox. mpearson@chromium.org jdonnelly@chromium.org ender@google.com Measures whether the suggestion that was selected by the user offered a tab match. A tab match occurs when the URL specified by the suggestion matches the URL navigated to by another tab in the browser, within the margin of our URL stripping scheme. This metric typically only makes sense with respect to Omnibox.SuggestionUsed.OfferedTabMatch. Only recent versions of the browser send the metric. Therefore, other metrics may include datapoints not covered by this metric (unless one narrows the data by version.) In M-74 and earlier, this was only recorded if the user had no incognito windows open. In M-75 and later, it records all omnibox interactions regardless, in order to be consistent with how user actions and histograms are handled. jdonnelly@chromium.org orinj@chromium.org chrome-desktop-search@google.com Counts how often omnibox pedals are used and records the type (concept ID) of the pedal used. Pedals are a button attached to a search suggestion that either navigate to a chrome:// URL or trigger a Chrome action (for example, opening the page translation dialog or opening a new window in Incognito mode). This histogram is related to Omnibox.PedalShown. Starting with Chrome/Android M142 this histogram is recorded whenever the Omnibox is used to navigate somewhere, closely matching how other Omnibox histograms are recorded. Before M142 this histogram would be recorded any time the Omnibox interaction has completed, whether the user initiated navigation or not. manukh@chromium.org chrome-desktop-search@google.com chrome-journeys@google.com Logs the position of "Resume Journey" omnibox actions actually selected by the user. The position index is 0-based, so a selected action in the topmost match is logged as value 0, consistent with Omnibox.SelectedPosition. This can be combined with Omnibox.ResumeJourneyShown to compute the Usage (or CTR) of the "Resume Journey" omnibox action on a per-position basis. It's safe to compare the total count of this metric to the total count of Omnibox.ResumeJourneyShown because within a single popup, only zero or one "Resume Journey" can be shown. If multiple actions start being shown in the popup, comparing to the total count becomes misleading to interpret as a CTR. sophiechang@chromium.org chrome-journeys@google.com Logs the type of the matched cluster keyword of "Resume Journey" omnibox actions actually selected by the user. This can be combined with Omnibox.ResumeJourneyShown.ClusterKeywordType to compute the precision (or CTR) of the "Resume Journey" omnibox action on a keyword type basis. It's safe to compare the total count of this metric to the total count of Omnibox.ResumeJourneyShown.ClusterKeywordType because within a single popup, only zero or one "Resume Journey" can be shown. If multiple actions start being shown in the popup, comparing to the total count becomes misleading to interpret as a CTR. sophiechang@chromium.org chrome-journeys@google.com Emitted when the user uses the omnibox to go somewhere AND the "Resume Journey" chip triggered by {ClusterKeywordTypeLabel} was offered in any position. This metric records "Selected" if the offered action chip was selected, and records "Not Selected" if the offered action chip was not selected. Therefore the "Selected" bucket proportion is the CTR of the action chip. The count of this bucket matches the {ClusterKeywordTypeLabel} bucket of Omnibox.SuggestionUsed.ResumeJourney.ClusterKeywordType. The total count of both buckets is how many times we've offered the chip triggered by {ClusterKeywordTypeLabel} in total, and matches the {ClusterKeywordTypeLabel} bucket of Omnibox.ResumeJourneyShown.ClusterKeywordType. manukh@chromium.org chrome-journeys@google.com Emitted when the user uses the omnibox to go somewhere AND the "Resume Journey" chip was offered in any position. This metric records "Selected" if the offered action chip was selected, and records "Not Selected" if the offered action chip was not selected. Therefore the "Selected" bucket proportion is the CTR of the action chip. The count of this bucket matches the sum of Omnibox.SuggestionUsed.ResumeJourney. The total count of both buckets is how many times we've offered the chip total, and matches the sum of Omnibox.ResumeJourneyShown. manukh@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com Measures the number of sessions for which each type of rich autocompletion was used. As the user types into the omnibox, the omnibox suggestions are updated. Some of those suggestions may have rich autocompletion. No suggestion may have multiple types of rich autocompletion. A type of rich autocompletion is considered triggered only if the default suggestion has rich autocompletion. If a non-default suggestion has rich autocompletion, does not suffice. If any input during the session triggered a rich autocompletion type, that type is considered triggered for the entire session. Recorded exactly once per omnibox session (i.e. per user selecting a suggestion). jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com Measures the time from navigation start to first meaningful paint. Only recorded for a search query suggestion selected from the omnibox. spelchat@chromium.org chrome-brapp-loading@google.com chrome-desktop-search@google.com Measures the time from the user selecting the omnibox suggestion and the navigation start time getting ticked. Only recorded for a search query suggestion selected from the omnibox. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com Measures the time from navigation start to first contentful paint. Only recorded for a search query suggestion selected from the omnibox. lingqi@chromium.org chrome-prerendering@google.com chrome-desktop-search@google.com Measures the time from navigation start to largest contentful paint (https://github.com/w3c/largest-contentful-paint). Only recorded for a search query suggestion selected from the omnibox. spelchat@chromium.org chrome-brapp-loading@google.com chrome-desktop-search@google.com Measures the time from navigation to the time the first largest contentful paint candidate (https://github.com/w3c/largest-contentful-paint#the-last-candidate) above 2 seconds. Only recorded for a search query suggestion selected from the omnibox. Note that this histogram is most useful for use with Chrometto in order to record a high LCP trace as soon as it happens (rather than only once the slow page loads gets discarded). mpearson@chromium.org jdonnelly@chromium.org ender@google.com Measures whether the suggestion that was selected by the user offered a tab match and specifically that the user chose the tab match over normal navigation. A tab match occurs when the URL specified by the suggestion matches the URL navigated to by another tab in the browser, within the margin of our URL stripping scheme. By selecting the tab match, the browser simply switches focus to the matching tab. This metric typically only makes sense with respect to Omnibox.SuggestionUsed.OfferedTabMatch. Only recent versions of the browser send the metric. Therefore, other metrics may include datapoints not covered by this metric (unless one narrows the data by version.) This metric should be stricly less than Omnibox.SuggestionUsed.OfferedTabMatch, and is typically used to discover the percentage of offered tab matches that the user accepts. In M-74 and earlier, this was only recorded if the user had no incognito windows open. In M-75 and later, it records all omnibox interactions regardless, in order to be consistent with how user actions and histograms are handled. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com Measures the time from navigation start to first meaningful paint. Only recorded for a URL suggestion selected from the omnibox. spelchat@chromium.org chrome-brapp-loading@google.com chrome-desktop-search@google.com Measures the time from the user selecting the omnibox suggestion and the navigation start time getting ticked. Only recorded for a URL suggestion selected from the omnibox. jdonnelly@chromium.org mpearson@chromium.org chrome-desktop-search@google.com Measures the time from navigation start to first contentful paint. Only recorded for a URL suggestion selected from the omnibox. robertlin@chromium.org chrome-prerendering@google.com chrome-desktop-search@google.com Measures the time from navigation start to largest contentful paint. Only recorded for a URL suggestion selected from the omnibox. mpearson@chromium.org jdonnelly@chromium.org cch@chromium.org The time elapsed between the sending of a suggest request to Google until the time the request was returned with status==failed. Ignores requests that were canceled before being returned. mpearson@chromium.org jdonnelly@chromium.org cch@chromium.org The time elapsed between the sending of a suggest request to Google until the time the request was returned with status==success. Ignores requests that were canceled before being returned. mahmadi@chromium.org chrome-desktop-search@google.com The number of requests sent by the omnibox to its suggest backends, bucketed by the request type. Recorded when the request starts, i.e., after obtaining the OAuth token if applicable, at most once per omnibox autocompletion cycle as the user types or has focused or cleared the omnibox but has not typed in yet (aka zero-suggest); In other words, at most once per each time the user changes the omnibox input. For zero-suggest prefetching requests, this may be recorded on page load and on tab switch events for eligible pages. mahmadi@chromium.org chrome-desktop-search@google.com The number of responses from the omnibox suggest backends, sliced by the request type and the page context (a.k.a. page classification) and bucketed by the HTTP response code. Recorded once per response received, which is at most one time per Omnibox.SuggestRequestsSent is recorded, since some requests are cancelled. mahmadi@chromium.org chrome-desktop-search@google.com The number of responses from the omnibox suggest backends, sliced by the request type and bucketed by the HTTP response code. Recorded once per response received, which is at most one time per Omnibox.SuggestRequestsSent is recorded, since some requests are cancelled. mahmadi@chromium.org chrome-desktop-search@google.com How long it took in milliseconds to receive responses from the omnibox suggest backends for completed requests only, sliced by the request type, response success status, and the page context (a.k.a. page classification). Recorded once per response received, which is at most one time per Omnibox.SuggestRequestsSent is recorded, since some requests are cancelled. ananyaseelam@google.com manukh@chromium.org chrome-desktop-search@google.com How long it took in milliseconds to receive responses from the EnterpriseSearchAggregatorProvider suggest backend. Sliced by whether the request was completed or interrupted. Sliced by request type. Recorded once per response received, which is at most one time per Omnibox.SuggestRequestsSent is recorded, since some requests are cancelled. Recorded for completed, completed with error, completed with empty response, and interrupted requests. Not recorded for requests that were queued but not started (i.e. provider debouncer or auth request did not complete before the provider was interrupted). khalidpeer@chromium.org mahmadi@chromium.org chrome-desktop-search@google.com How long it took in milliseconds to receive responses from the omnibox suggest backends for completed requests only, sliced by the request type, and response success status. Recorded once per response received, which is at most one time per Omnibox.SuggestRequestsSent is recorded, since some requests are cancelled. ananyaseelam@chromium.org manukh@chromium.org chrome-desktop-search@google.com The number of results returned for each suggestion of type {EnterpriseSuggestionType} and the total number of suggestions. Can be more than the matches shown to the user as not every result in the response will be shown. Sliced by request type. Recorded once per response received, which is at most one time per Omnibox.SuggestRequestsSent is recorded, since some requests are cancelled. Recorded for completed, completed with error, and completed with empty response requests. Not logged for interrupted requests. Not recorded for requests that were queued but not started (i.e. provider debouncer or auth request did not complete before the provider was interrupted). mahmadi@chromium.org chrome-desktop-search@google.com The number of requests sent by the omnibox to its suggest backends, bucketed by the request type, sliced by the page context (a.k.a. page classification). Recorded when the request starts, i.e., after obtaining the OAuth token if applicable, at most once per omnibox autocompletion cycle as the user types or has focused or cleared the omnibox but has not typed in yet (aka zero-suggest); In other words, at most once per each time the user changes the omnibox input. For zero-suggest prefetching requests, this may be recorded on page load and on tab switch events for eligible pages. ender@google.com mahmadi@chromium.org The index of the item in the MostVisited carousel that the user deleted. Zero-based: the first item in the carousel is recorded in bucket 0, second in bucket 1 and so on. Items beyond 16 will be stored in the overflow bucket (15). Recorded every time the user initiates deletion of a suggest tile, even if the operation is later canceled. Note: There is a recording gap between: 2026.07-2026.08. ender@google.com mahmadi@chromium.org Records the type of the SuggestTile that the user deleted. Most Visited URLs record a URL, and Organic Repeatable Queries record a Search type. Recorded every time the user initiates deletion of a suggest tile, that results with tile removal. Not recorded if the user chooses to cancel the action. Note: There is a recording gap between: 2026.07-2026.08. ender@google.com mahmadi@chromium.org The index of the item in the MostVisited carousel that the user opened. Zero-based: the first item in the carousel is recorded in bucket 0, second in bucket 1 and so on. Items beyond 16 will be stored in the overflow bucket (15). Recorded every time the user selects the tile to initiate navigation, even if the navigation could not be completed (eg. target site did not load). ender@google.com mahmadi@chromium.org Records the type of the SuggestTile that the user interacted with. Most Visited URLs record a URL, and Organic Repeatable Queries record a Search type. Recorded every time the user selects the tile to initiate navigation, even if the navigation could not be completed (eg. target site did not load). Note: There is a recording gap between: 2023.06-2023.08. ender@google.com mahmadi@chromium.org Total count of offered {SuggestTileType} tile types. Recorded every time the current context is eligible to receive MostVisitedTiles, even if there were no tiles of any kind to show. Note: There is a recording gap between: 2023.06-2023.08, 2026.07-2026.08. jdonnelly@chromium.org mpearson@chromium.org ender@google.com chrome-desktop-search@google.com This histogram reports the amount of time it takes to match one set of suggestions against all open tabs. This metric is collected once for every time a new set of suggestions is received. This includes the Omnibox Focus event (when zero-prefix suggestions are offered) and every subsequent key stroke, including deletion, backspace etc. Each keystroke produces multiple events offering autocomplete matches: a) one synchronous, when Start() is called. b) any number of intermediate events, depending on whether Providers request the update. c) one at the end, when the process completes. Since these are produced about 3 times per keystroke, the total time consumed per Omnibox interaction is - optimistically - 3*Omnibox.TypedLength*TabMatchTime. this excludes all the time spent formulating the query, such as correcting the input. This metric does not express the cumulative time spent matching the tabs (because we do not have a metric that counts the number of suggestions the user actually fetched - eg. we do not count the number of suggestions received when user pressed the backspace key). This histogram only records metrics on machines with high-resolution clocks. (Expired in 2024-04-28. Revived in 2025-01-06.) Note: There is a recording gap between: 2026.02-2026.08. dgn@google.com ender@google.com chrome-regionalcapabiltiies@google.com At the beginning of the process of merging prepopulated engines into the keywords database, records the number of entries that match the current default search engine. Matching is done by preopulate ID or by ID of the DSE's pre-migration ID, if relevant. There may be more than one engine matching due to some unexpected behaviour associated with migrations, sync or changes in the profile's assigned country. Recorded once per keywords database merging, which gets triggered on startup if the built-in search engines data has been updated, or the profile's assigned country changed. dgn@google.com ender@google.com chrome-regionalcapabiltiies@google.com During the process of merging prepopulated engines into the keywords database, records a reason why an existing entry might be preserved after it did not match any of the regional prepopulated engines. Recorded once per keywords database merging, which gets triggered on startup if the built-in search engines data has been updated, or the profile's assigned country changed. dgn@chromium.org chrome-omnibox-team@google.com Emitted when an engine is migrated to a new ID during the Keywords database update pass. Records whether the migrated engine was the user's Default Search Provider or another engine present in the keywords DB. dgn@google.com chrome-regionalcapabilities@google.com The match or mismatch reason found while comparing prepopulated engines and keywords DB engines during prepopulated engines migration. A "match" (e.g., exact or host match) indicates that an engine in the keywords database corresponds to a prepopulated engine definition and can be migrated. A "mismatch" (e.g., URL mismatch or invalid URL) indicates that the existing engine does not sufficiently match the prepopulated one, and thus cannot be safely migrated. Recorded for each engine under migration that matches an existing engine, during the keywords DB refresh that is done on profile load after a database version update, country change, or migration feature flag flip. dgn@google.com chrome-regionalcapabilities@google.com Recorded when multiple TemplateURLs tagged as created by a regulatory program (e.g., Android EEA Choice Screen) are loaded from the Keyword Web Database during startup reconciliation. Records True if all such duplicate regulatory entries share the identical search keyword, and False if at least one entry has a different keyword. This helps identify whether database duplicates are caused by row cloning vs incomplete deletions of prior engine choices. dgn@google.com chrome-regionalcapabilities@google.com The total number of duplicate prepopulated engine IDs found in the search engine database during a refresh. dgn@google.com ender@google.com chrome-regionalcapabiltiies@google.com At the end of the process of merging prepopulated engines into the keywords database, records the number of entries that match the current default search engine but that did not get reconciled with some existing entry and will be discarded. Recorded once per keywords database merging, which gets triggered on startup if the built-in search engines data has been updated, or the profile's assigned country changed. dgn@google.com chrome-reg-cap@google.com The type of match found during prepopulated engine migration in the DSE reconciler. Recorded for each engine under migration that matches an existing engine. ender@google.com chrome-desktop-search@google.com Captures the type of performed reconciliation (if any). Recorded once per Default Search Engine reconciliation event (on start + any time the Default Search Engine is changed). ender@google.com chrome-desktop-search@google.com Captures the outcome of TemplateURL reconciliation whenever reconciliation takes place. This histogram captures outcome of reconciliation {ByVariant}. ender@google.com chrome-desktop-search@google.com Records the type of regulatory extension used to formulate the Search URL. Recorded for all TemplateURLs every time a Search URL is created, regardless of whether extensions are used, or a specific extension type is populated. Note: There is a recording gap between: 2026.07-2026.08. ender@google.com chrome-desktop-search@google.com Records the type of regulatory extension used to formulate the Suggest URL. Recorded for all TemplateURLs every time a Suggest URL is created, regardless of whether extensions are used, or a specific extension type is populated. ender@google.com jdonnelly@google.com chrome-desktop-search@google.com For every TemplateUrl expansion, captures whether Query has an organic nature (RLZ empty) or not (RLZ present). Recorded once for every TemplateUrl expansion if the Template URL references the {google:RLZ} parameter. Note: There is a recording gap between: 2026.07-2026.08. ender@google.com jdonnelly@google.com chrome-desktop-search@google.com For every TemplateUrl expansion, captures whether Query has an organic nature (Search client empty) or not (Search client present). Recorded once for every TemplateUrl expansion if the Template URL references the {google:searchClient} parameter. ender@google.com jdonnelly@google.com chrome-desktop-search@google.com For each TemplateUrl parameter that cannot be expanded, captures the origin of the template url parameter. Prepopulated TemplateUrl definitions come from `prepopulated_engines.json` file, whereas Non-prepopulated definitions may originate from external configuration files linked to region-specific DMA implementations (Android), user-supplied definitions (Desktop), or device configuration (e.g. ADCP, Enterprise policies). See go/chrome-android-dma for additional details. Recorded once per unexpanded parameter for every TemplateUrl expansion. Values reported by this histogram should be zero for mobile devices, possibly also for Desktop and ChromeOS (unconfirmed). Note: There is a recording gap between: 2026.07-2026.08. mpearson@chromium.org jdonnelly@chromium.org chrome-desktop-search@google.com The scheme of the destination URL for the selected omnibox suggestion. This could be a what-you-typed suggestion (if the user fully typed a URL), an inline autocompletion, or something in the dropdown, anything as long as it's a URL navigation, not a search query. Excludes omnibox URL navigations that are effectively reloads as well as cut-and-pastes of URLs. Also does not take into account any redirects that destination URL may do before finally serving a page. In other words, it's the scheme of the first request in a possible chain. Due to a bug, recorded paste-and-go actions through M-88 (inclusive). Excluded in M-89+. mahmadi@chromium.org yoangela@chromium.org chrome-desktop-search@google.com The amount of time it takes to execute the URL scoring model for all the eligible matches. Emitted when all the providers are done and there is at least one eligible match for model execution. This histogram only records metrics on machines with high-resolution clocks. mahmadi@chromium.org yoangela@chromium.org chrome-desktop-search@google.com The number of matches the URL scoring model was executed for. Emitted when all the providers are done and there is at least one eligible match for model execution. khalidpeer@chromium.org manukh@chromium.org chrome-desktop-search@google.com Records whether there was a cache hit when attempting to fetch the ML score associated with a given vector of scoring signals. This will be recorded for each match that is submitted to the ML scoring service. Each omnibox input triggers multiple autocomplete passes with each pass generating multiple autocomplete matches. Therefore, this metric will get logged several times for a single omnibox input. khalidpeer@chromium.org manukh@chromium.org chrome-desktop-search@google.com Records the percentage of scoring-eligible autocomplete matches that were assigned non-null scores by the ML scoring model. This will be recorded for each batch that is submitted to the ML scoring service. khalidpeer@chromium.org manukh@chromium.org chrome-desktop-search@google.com During the execution of `AutocompleteScoringModelExecutor::Preprocess()`, this metric records whether or not the number of input tensors passed in matches the size of the ModelInput. This will be recorded once for each suggestion contained in a batch that's submitted to the ML scoring service. This will NOT be recorded for any suggestion that already has a non-null scoring result stored in the ML score cache. khalidpeer@chromium.org manukh@chromium.org chrome-desktop-search@google.com For each ML eligible match generated by the autocomplete provider of type {ProviderType}, records the number of null/non-null values logged by client code for the ML scoring signal of type {ScoringSignalType}. tluk@chromium.org chrome-desktop-search@google.com Records the number of milliseconds between the views omnibox popup construction and the first time content for the popup is displayed on the screen. This is emitted once each time the omnibox is opened. It is recorded again if the omnibox has closed and later re-opened. It is not emitted more than once for a single opened instance of the ombibox popup. gjc@google.com chrome-loading@google.com Records the duration of OmniboxViewViews::RevertAll. Recorded when the omnibox view is reverted (e.g. when the user presses Escape or navigation starts). This metric is only reported for clients with high-resolution clocks. gjc@google.com chrome-loading@google.com Records whether a call to OmniboxViewViews::SetTextAndSelectedRange was idempotent (i.e., the text and selection were already set to the target values, and no additional text was present). Recorded when SetTextAndSelectedRange is called. This helps measure the potential savings of adding an idempotency guard. gjc@google.com chrome-loading@google.com Records the duration of OmniboxViewViews::SetTextAndSelectedRange. Recorded when the text and selection in the omnibox view are updated. This metric is only reported for clients with high-resolution clocks. orinj@chromium.org chrome-desktop-search@google.com Logged each time a selection is opened from the WebUI omnibox popup. Records whether or not the AutocompleteResult sequence identifier specified by the page (WebUI popup) matched that of the AutocompleteController's published result. This can be used to determine how often the UI attempts to make use of a result that is not the latest from autocomplete. mahmadi@chromium.org chrome-desktop-search@google.com Records the time between a keystroke being typed in the <cr-searchbox> and the time when the <cr-searchbox-dropdown> is ready to render the results. If there are multiple keystrokes before the results are rendered, logs the time since the earliest. This does not take into account the time the DOM change task spends in the message loop nor its duration. mahmadi@chromium.org kylixrd@google.com chrome-desktop-search@google.com between AutocompleteController::Observer's OnResultChanged and the time when the <cr-searchbox-dropdown> is ready to render the results. If there are multiple calls to OnResultChanged before the results are rendered, logs the time since the earliest. This does not take into account the time the DOM change task spends in the message loop nor its duration. orinj@chromium.org chrome-desktop-search@google.com Logged each time a selection is opened from the WebUI omnibox popup. Records whether or not the selection specified by the page (WebUI popup) matched the current OmniboxEditModel popup selection. agale@chromium.org chrome-desktop-search@google.com top-chrome-desktop-ui@google.com The width of the omnibox view in each open browser window, in DIPs, reported once per UMA log. Desktop only. agale@chromium.org chrome-desktop-search@google.com top-chrome-desktop-ui@google.com The ratio of the width of the omnibox view relative to the window width in each open browser window. Reported once per UMA log. Desktop only. pnoland@chromium.org ender@google.com chrome-desktop-search@google.com The number of results (either query or URL) from ZeroSuggest. This is emitted every time ZeroSuggestProvider produces results on omnibox focus or on omnibox input clobber, either from the cache or from the remote response. khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if at least one zero-prefix suggestion was offered during the course of the Omnibox session. Given that at least one zero-prefix suggestion was offered during the session, this records whether or not the user ultimately selected a zero-prefix suggestion in the Omnibox. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. This metric is analogous to "Bsb zpSCTR". Precision = Zero-Prefix Suggestions Used / Navigations with Zero-Prefix Suggestions Offered (Precision = Usage / Recall). khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if at least one zero-prefix suggestion was offered during the course of the Omnibox session. Given that at least one zero-prefix suggestion was offered during the session, this records whether or not the user ultimately selected a zero-prefix suggestion in the Omnibox. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. Sliced by page context (a.k.a. page classification). This metric is analogous to "Bsb zpSCTR". Precision = Zero-Prefix Suggestions Used / Navigations with Zero-Prefix Suggestions Offered (Precision = Usage / Recall). pnoland@chromium.org ender@google.com chrome-desktop-search@google.com The number of query results returned from ZeroSuggest. This is emitted every time ZeroSuggestProvider produces results on omnibox focus or on omnibox input clobber, either from the cache or from the remote response. khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if at least one zero-prefix suggestion was offered during the course of the Omnibox session. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. This metric is analogous to "Bsb QwZPS". Recall = Navigations with Zero-Prefix Suggestions Offered / All Navigations (Recall = Usage / Precision). khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if at least one zero-prefix suggestion was offered during the course of the Omnibox session. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. This metric is analogous to "Bsb QwZPS". Recall = Navigations with Zero-Prefix Suggestions Offered / All Navigations (Recall = Usage / Precision). Sliced by page context (a.k.a. page classification). pnoland@chromium.org ender@google.com chrome-desktop-search@google.com The number of URL results returned from ZeroSuggest. This is emitted every time ZeroSuggestProvider produces results on omnibox focus or on omnibox input clobber, either from the cache or from the remote response. khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if the user selected a zero-prefix suggestion in the Omnibox. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. This metric is analogous to "Bsb zpSQ/SEQ". Usage = Zero-Prefix Suggestions Used / All Navigations (Usage = Precision * Recall). khalidpeer@chromium.org chrome-desktop-search@google.com Upon navigation, this metric is recorded if the user selected a zero-prefix suggestion in the Omnibox. An "Omnibox session" is currently defined as a span of time that starts when the user focuses the Omnibox and ends when the user de-focuses it, whether implicitly (e.g. by selecting one of the suggestions) or explictly (e.g. by clicking on some non-Omnibox browser UI). The session data that's maintained by AutocompleteResult will be initialized when the session starts, updated throughout the course of the session, and ultimately reset when the session ends. This metric is analogous to "Bsb zpSQ/SEQ". Usage = Zero-Prefix Suggestions Used / All Navigations (Usage = Precision * Recall). Sliced by page context (a.k.a. page classification). mahmadi@chromium.org chrome-desktop-search@google.com Logs whether ZeroSuggestProvider is eligible to request and display zero- prefix suggestions, and if not, why not. Emitted for both omit_asynchronous_matches_ true (i.e, Autocomplete classifier) and false inputs (i.e, when the user has typed in, focused the omnibox, or cleared it but has not typed in yet) in ZeroSuggestProvider::Start(). Also emitted on applicable page load/switch events in ZeroSuggestProvider::StartPrefetch(). mahmadi@chromium.org chrome-desktop-search@google.com Enumerates the events in the ZeroSuggestProvider as a result of {RequestType} for {ResultType} (i.e., suggestions shown when the user has focused or cleared the omnibox but has not typed in yet). khalidpeer@chromium.org chrome-desktop-search@google.com Emitted when the user uses the Omnibox to go somewhere AND an action of the given type was shown in the Omnibox popup. This metric records "Selected" (1) if the action was selected and records "Not Selected" (0) if the action was not selected. Therefore, the "Selected" bucket proportion is the CTR (click-through rate) of the action. The total count of both buckets is how many times we've shown the action total. nhiroki@chromium.org chrome-prerendering@google.com {SearchPrefetch} Measures the time between the construction of CacheAliasSearchPrefetchURLLoader and the moment the prefetch fell back from the disk cache to network. This is recorded when the loader starts the fallback in CacheAliasSearchPrefetchURLLoader::RestartDirect(). nhiroki@chromium.org chrome-prerendering@google.com {SearchPrefetch} The reason that a search prefetch request failed to read a response from the disk cache and then fell back to network. This is recorded when CacheAliasSearchPrefetchURLLoader is destructed regardless of whether the fallback happened. When the fallback didn't happen, this records kNoFallback. chikamune@chromium.org chrome-prerendering@google.com {SearchPrefetch} This histogram records whether a prefetch URL loader receives a No-Vary-Search HTTP response header or not. This is only recorded when the response is servable. {PrefetchFallbackOrInitial} {NavigationOrSuggestionPrefetch} spelchat@chromium.org chrome-brapp-loading@google.com chrome-desktop-search@google.com {SearchPrefetch} Measures the time between the navigation is intercepted by the Search Prefetch code and the moment the Search Prefetch URL loader has finished forwarding the whole response to the navigation URL loader. This time includes finishing fetching the Search response and any queuing delays in the UI thread preventing the Search Prefetch URL loader from forwarding bytes to the navigation code. chikamune@chromium.org chrome-prerendering@google.com {SearchPrefetch} This histogram records the length of the No-Vary-Search HTTP response header that a prefetch URL loader receives. This is only recorded when the response is servable and the No-Vary-Search HTTP response header exists. {PrefetchFallbackOrInitial} {NavigationOrSuggestionPrefetch} ryansturm@chromium.org chrome-desktop-search@google.com {SearchPrefetch} The reason that a search prefetch request issued when a user navigates to a suggestion was not eligible to be prefetched (or 'Prefetched' if it was prefetched). {NavigationOrSuggestionPrefetch} ryansturm@chromium.org chrome-desktop-search@google.com {SearchPrefetch} The status of a Search Prefetch request when it is deleted by expiration or by serving the request. {NavigationOrSuggestionPrefetch} ryansturm@chromium.org lingqi@chromium.org chrome-desktop-search@google.com chrome-prerendering@google.com {SearchPrefetch} The reason that a navigation request could or could not serve a search prefetch request. {PrerenderOrNavigation} ryansturm@chromium.org chrome-desktop-search@google.com chrome-prerendering@google.com {SearchPrefetch} This histogram records whether an activated (i.e., served) prefetch URL Loader receives a servabled response from the server. A servabled reasponse should contain valid headers and body, with any 200 response code. {PrefetchFallbackOrInitial} {NavigationOrSuggestionPrefetch} jdonnelly@chromium.org chrome-desktop-search@google.com The number of entries in `ShortcutsBackend`'s database. Recorded once on profile load. See also ShorcutsProvider.DatabaseSize.FileMB, ShortcutsProvider.DatabaseSize.OldEntries and ShortcutsProvider.OldEntryDeletions. jdonnelly@chromium.org chrome-desktop-search@google.com The number of entries in `ShortcutsBackend`'s database that are older than 90 days. Recorded once on profile load. This value is expected to be near 0 as there are two mechanisms to delete old entries. The first is individual deletions due to notificaitons that the associated URL has been deleted from the history system. This mechanism is not 100% reliable, however, since the URL deletions are performed by HistoryService, which may be started up before ShortcutsBackend, which handles the notifications. Therefore the second mechanism is a batch deletion of all entries older than 90 days by ShortcutsBackend on profile load. The count of deletions via the second mechanism is recorded in ShortcutsProvider.OldEntryDeletions. See also ShortcutsProvider.DatabaseSize and ShortcutsProvider.DatabaseSize.OldEntriesPercentage. jdonnelly@chromium.org chrome-desktop-search@google.com The percentage of entries in `ShortcutsBackend`'s database that are older than 90 days. Recorded once on profile load. See ShortcutsProvider.DatabaseSize.OldEntries for additional details on how and why this is recorded. manukh@chromium.org chrome-desktop-search@google.com The number of entries in `ShortcutsBackend`'s database that were deleted due to the associated keyword being deleted from the `TemplateURLService` or inactive. Recorded once on profile load. See also ShortcutsProvider.DeletedOrInactiveKeywordEntryDeletions.OnKeywordChange. manukh@chromium.org chrome-desktop-search@google.com The number of entries in `ShortcutsBackend`'s database that were deleted due to the associated keyword being deleted from the `TemplateURLService` or inactive. Recorded each time an `OnTemplateURLServiceChanged` notification from `TemplateURLService` is received by `ShortcutsBackend`. See also ShortcutsProvider.DeletedOrInactiveKeywordEntryDeletions.OnInit. jdonnelly@chromium.org chrome-desktop-search@google.com The number of entries in `ShortcutsBackend`'s database that were deleted due to the associated URL being deleted from the history database. Recorded each time an `OnHistoryDeletions` notification from `HistoryService` is received by `ShortcutsBackend`. See also ShortcutsProvider.OldEntryDeletions.OnInit. jdonnelly@chromium.org chrome-desktop-search@google.com The number of entries in `ShortcutsBackend`'s database that were deleted due to being older than 90 days. Recorded once on profile load. For each profile load, this is expected to record the same value as ShortcutsProvider.DatabaseSize.OldEntries. If experimental data appears to confirm this, it may not be necessary to maintain both histograms. See also ShortcutsProvider.OldEntryDeletions.OnHistoryDeletions. wenhuc@google.com chrome-desktop-search@google.com Total actions taken by users of Voice Search across ALL surfaces. This provides an aggregated view over all entry points. These actions may navigate away from the current page (e.g., submitting a speech query), but can also happen without navigating away (e.g., initiating, retrying, or canceling Voice Search). Recorded immediately when the user performs a specific voice search action, or when a lifecycle event concludes (e.g., an error canceling the search). Recorded exactly once per user action or lifecycle event. wenhuc@google.com chrome-desktop-search@google.com Actions taken by users of Voice Search on {OmniboxPageContext}. These actions may navigate away from the current page (e.g., submitting a speech query), but can also happen without navigating away (e.g., initiating, retrying, or canceling Voice Search). Recorded immediately when the user performs a specific voice search action, or when a lifecycle event concludes (e.g., an error canceling the search). Recorded exactly once per user action or lifecycle event. wenhuc@google.com chrome-desktop-search@google.com Total errors that occur during Voice Search across ALL surfaces. This provides an aggregated view over all entry points. These may be user-induced (e.g., the user's utterance could not be recognized - no match), or resulting from external circumstances (e.g., network error, lack of microphone permission). Recorded immediately when the underlying Web Speech API reports an error event or a no-match event. All errors are recorded (recorded exactly once per error occurrence). wenhuc@google.com chrome-desktop-search@google.com Errors that occur during Voice Search use on {OmniboxPageContext}. These may be user-induced (e.g., the user's utterance could not be recognized - no match), or resulting from external circumstances (e.g., network error, lack of microphone permission). Recorded immediately when the underlying Web Speech API reports an error event or a no-match event. All errors are recorded (recorded exactly once per error occurrence). wenhuc@google.com chrome-desktop-search@google.com Records the entrypoint source immediately when the user submits a voice search query (i.e., QUERY_SUBMITTED action). This provides a consolidated view to compare voice query volumes across all 4 Chrome searchbox entrypoints (NTP Realbox Classic, NTP Composebox, Omnibox Composebox, and Nextbox Composebox).