battre@chromium.org chrome-autofill-team@google.com Logged when users select Autocomplete entries in the dropdown, this histogram captures the number of days that have passed since the selected autocomplete entry was last submitted on a website. I.e., the distribution of time between uses of an "active" autocomplete entry. battre@chromium.org chrome-autofill-team@google.com Autocomplete events which are recorded when the user interacts with suggestions served from Autocomplete. This is for an ablation study that we may want to reactivate at some points in the future. battre@chromium.org chrome-autofill-team@google.com Records for time from the first change to an input element (typed or autofilled) on any form of a frame to a form submission. Note that the change could even happen to a different form on the page than the one submitted. This is for an ablation study that we may want to reactivate at some points in the future. battre@chromium.org chrome-autofill-team@google.com Records whether after changing the value of an input element (typed or autofilled) in a frame, any form on that page is submitted. koerber@google.com chrome-autofill-alerts@google.com Logs if the filling of a field was accepted even though it had a NUMERIC_QUANTITY prediction. This metric is only emitted if the feature to grant the heuristic precedence is disabled. Emitted on submission time. koerber@google.com chrome-autofill-alerts@google.com Tracks whether Profile (Address) Autofill is enabled on page load for a page containing forms. koerber@google.com chrome-autofill-alerts@google.com Tracks whether Profile (Address) Autofill is enabled when Chrome launches. battre@chromium.org chrome-autofill-alerts@google.com The number of unverified autofill addresses deleted because they have not been used for a long time, and are not used as billing addresses of valid credit cards. Note the deletion only happens once per major version upgrade. battre@chromium.org chrome-autofill-alerts@google.com The number of address suggestions not shown in the Autofill popup because they have not been used recently enough. Note that suppression only applies when the user has not typed any text into the field. If any text is in the field, all matching addresses are displayed, regardless of how recently they have been used. koerber@google.com battre@chromium.org Each country can require different fields (ZIP code, state, city) to exist for an address to be valid. This histogram logs which mandatory fields were missing in a submitted address form. koerber@google.com battre@chromium.org Logs whether the individual requirements for importing an address profile are met at form submission time. koerber@google.com battre@chromium.org Logs the overall status of a profile import attempt on form submission time. battre@chromium.org chrome-autofill-alerts@google.com The number of address suggestions shown in the Autofill popup. koerber@google.com chrome-autofill-alerts@google.com For each {AddressType} in a given AutofillProfile, the verification status of the corresponding non-empty type is recorded when a profile is used to fill a form. schwering@google.com chrome-autofill-alerts@google.com Records at submission time for each autofilled field with autocomplete != off whether the user edited the autofilled field value or not. {AutofillFormType} schwering@google.com chrome-autofill-alerts@google.com Records at submission time for each autofilled field with autocomplete != off whether the user edited the autofilled field value or not. {AutofillFormType} schwering@google.com chrome-autofill-alerts@google.com Records for each submitted form whether the user accepted the suggestion to fill values and the triggering field has autocomplete != off. This is counted as 'yes' if the user accepted such a suggestion at any time, regardless whether other suggestions were ignored or whether the accepted suggestion was reverted afterwards. {AutofillFormType} schwering@google.com chrome-autofill-alerts@google.com Records at submission time for each autofilled field with autocomplete = off whether the user edited the autofilled field value or not. {AutofillFormType} schwering@google.com chrome-autofill-alerts@google.com Records at submission time for each autofilled field with autocomplete = off whether the user edited the autofilled field value or not. {AutofillFormType} schwering@google.com chrome-autofill-alerts@google.com Records for each submitted form whether the user accepted the suggestion to fill values and the triggering field has autocomplete = off. This is counted as 'yes' if the user accepted such a suggestion at any time, regardless whether other suggestions were ignored or whether the accepted suggestion was reverted afterwards. {AutofillFormType} koerber@google.com fleimgruber@google.com chrome-autofill-team@google.com Records a pair of (PredictionState, AutocompleteState) for each field in a submitted form. PredictionState indicates if server and/or heuristic type prediction were available. AutocompleteState indicates if the autocomplete attribute was present and whether it was valid. Emitted on form submission. koerber@google.com fleimgruber@google.com chrome-autofill-team@google.com Records the heuristic type of each field with autocomplete=garbage in a submitted form. Emitted on form submission. koerber@google.com fleimgruber@google.com chrome-autofill-team@google.com Records the server type of each field with autocomplete=garbage in a submitted form. Emitted on form submission. koerber@google.com fleimgruber@google.com chrome-autofill-team@google.com Records the server type of each field with autocomplete=garbage in a submitted form. If no server type is available, the heuristics type is logged instead. Emitted on form submission. koerber@google.com fleimgruber@google.com chrome-autofill-team@google.com Records the PredictionType of each field in a submitted form, depending on the field's AutocompleteState. Emitted on form submission. jkeitel@google.com chrome-autofill-team@google.com Records how a user removed a single Autocomplete entry (i.e. via the keyboard or via a delete button in the Autofill popup). Emitted on Autocomplete entry deletion. jihadghanna@google.com chrome-autofill-alerts@google.com Records for each autofilled field where {PredictionType} predictions yielded {FieldType}, what was the corresponding autocomplete value. battre@chromium.org chrome-autofill-team@google.com Whether an autocomplete query is created for a field. battre@chromium.org chrome-autofill-team@google.com Whether there is any suggestions for an autocomplete query. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Tracks the time it takes to fetch the full PAN of a credit card once user successfully authenticates using WebAuthn. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Tracks the time it takes to fetch the full PAN of a credit card once user successfully authenticates using WebAuthn. Deprecated in M111. Subsumed by Autofill.BetterAuth.CardUnmaskPreflightCalledWithFidoOptInStatus. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Tracks the number of times Chrome made a GetDetailsForGetRealPan call. A preflight call is only made when card suggestions are shown, and can only happen when the user has server cards and is eligible for WebAuthn. As a percentage of the number of times card suggestions are shown, which is tracked under Autofill.FormEvents.CreditCard, this metric provides an estimate for the potential reach for the Autofill Better Auth project. Moreover, this acts as a baseline value for other metrics in this project. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com The total count of this histogram tracks the number of times Chrome made a preflight GetDetailsForGetRealPan call. A preflight call is only made when card suggestions are shown, and can only happen when the user has server cards and is eligible for WebAuthn. For every log in this histogram, it also tracks whether the user is opted-in to WebAuthn or opted-out of WebAuthn. A log of true indicates the user is opted-in, and a log of false indicates the user is opted-out. As a percentage of the number of times card suggestions are shown, which is tracked under Autofill.FormEvents.CreditCard, this metric provides an estimate for the potential reach for the Autofill Better Auth project. Moreover, this acts as a baseline value for other metrics in this project. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Tracking the latency of a GetDetailsForGetRealPan call to Payments servers. This duration should be comparable to that of Autofill.UnmaskPrompt.Duration and should ideally stay under 500 ms in order for the user to autofill their credit card without experiencing much friction. vinnypersky@google.com autofill-auth-team@google.com Logs the number of times that we initiate the card unmask preflight flow. This will log both when the user is eligible for WebAuthn as well as when the user is not eligible for WebAuthn, as it is logged before we check this status. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com If the user is definitely opted-in to the new auth flow, Payments sends a list of instrument IDs in the GDFGRP call, and Chrome makes the final call on whether CVC or WebAuthn should be shown. Tracks which authentication method was prompted. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Tracks when a user completes each step in a card unmasking flow per authentication flow type, with an additional breakdown for if it was a server card or virtual card. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Tracks when a user completes each step in a card unmasking flow per authentication type. This will provide a relative conversion rate for each authentication type. {AutofillCreditCardAuthenticationFlows} jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Tracks when users opt-in either from the settings page or from a checkout flow, making an UpdateAutofillUserPreference call. For each call to payments, logs if the call was made in order to verify an existing credential, to create a new credential, or to fetch a challenge. {AutofillCreditCardWebauthnOptInOrigin} vinnypersky@google.com shgar@google.com Records when the Better Auth (FIDO) opt-in promo could have been offered on Desktop, but wasn't. Logged at the time of the promo not being shown. This metric can only be logged from the checkout flow, as we do not block opting in to FIDO from the settings page. It logs the enum reason of what caused the promo to not be shown. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Logs the number of times the opt-in promo to use FIDO authentication for card unmasking has been shown. Only applicable on Desktop. This is useful when compared to Autofill.BetterAuth.OptInPromoUserDecision, to see what percentage of users are interacting with the dialog. Also, when an opted-out user receives the preflight call before selecting a card (which is recorded by the first bucket in Autofill.BetterAuth.UserPerceivedLatencyOnCardSelection.OptedOut), then the promo should eventually show if the user selects a masked card and successfully authenticates through CVC. {AutofillCreditCardWebauthnOptInOrigin} jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Tracks the user response to the opt-in promo for using FIDO authentication for card unmasking. The user can either accept the promo and proceed to perform user-verification, can decline the promo immediately, or first accept the promo but then decline while the challenge is being fetched. Only applicable on Desktop. {AutofillCreditCardWebauthnOptInOrigin} jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Tracks the number of times UpdateAutofillUserPreference has been called with the intention of opting out from FIDO authentication using the toggle switch on the payments section on the settings page. This will be useful when compared to values in Autofill.BetterAuth.OptInCalled to give an idea of what percentage of users decide to opt-out. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com The GetDetailsForGetRealPan call is made when card suggestions are shown. This metric logs the duration of the perceived latency when the response for this call is received after a card is chosen by an opted-in user. After waiting a set number of seconds without receiving a response, Chrome will fall back to CVC authentication. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com The GetDetailsForGetRealPan call is made when card suggestions are shown. If an opted-in user selects a card before the response is returned, latency is perceived. Given that the user perceives latency, this metric logs whether the request timed out and fell back to CVC or if the request was completed and continued to WebAuthn. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com The GetDetailsForGetRealPan call is made when card suggestions are shown. This metric tracks whether the response is received before or after a card is chosen by the user. For an opted-in user, a late response would imply perceived latency. For an opted-out user, a late response would imply that opt-in may not have been offered. {AutofillFidoAuthenticationEnabledState} jsaul@google.com siyua@chromium.org autofill-auth-team@google.com Tracks how long it takes to check that the user is verifiable through WebAuthn's IsUserVerifiablePlatformAuthenticatorAvailable() call. This check is done before deciding to make a GetDetailsForGetRealPan call to Payments. jsaul@google.com siyua@chromium.org autofill-auth-team@google.com This metric tracks the result of the WebAuthn prompt when the user attempts to either opt-in for FIDO authentication or unmask a card using FIDO authentication. {AutofillFidoUserVerificationFlow} jsaul@google.com siyua@chromium.org payments-autofill-team@google.com Events tracking the usage of the cardholder name fix flow prompt. This prompt is triggered whenever cardholder name must be explicitly requested from the user in order to upload the card to Google Payments. jsaul@google.com siashah@chromium.org longsheng@chromium.org payments-autofill-team@google.com Records the initial state of the ScreenLockCheckBox. The ScreenLockCheckBox is the checkbox shown to the user as part of the CardUnmaskPrompt. This histogram will be logged only when the CardUnmaskPrompt is initialized. This is only available on Android. jsaul@google.com siashah@chromium.org longsheng@chromium.org payments-autofill-team@google.com Records the check/uncheck action from users on the ScreenLockCheckBox. The ScreenLockCheckBox is the checkbox shown to the user as part of the CardUnmaskPrompt. This histogram will be updated whenever the user clicks/unclicks the checkbox. This is only available on Android. siyua@chromium.org jsaul@google.com siashah@chromium.org Records the result of the Card Unmask Authentication Selection Dialog, such as user cancelation before/after selecting a challenge option, or automatic dismissal after a server success/failure for a selected option was returned. The metric is recorded any time the dialog is dismissed. Deprecated in M109. Subsumed by Autofill.CardUnmaskAuthenticationSelectionDialog.Shown2. siyua@chromium.org jsaul@google.com siashah@chromium.org Records true every time the card unmask challenge option selection dialog was shown. This dialog is shown when a user needs to select a challenge option to authenticate a card for payments autofill. siyua@chromium.org jsaul@google.com siashah@chromium.org vinnypersky@google.com On every show of the card unmask challenge option selection dialog, this histogram records a count (with a maximum of 10) for the number of challenge options that were shown. This dialog is shown when a user needs to select a challenge option to authenticate a card for payments autofill. jsaul@google.com siyua@chromium.org payments-autofill-team@google.com Whether upload was offered upon detecting a form submission with credit card data, a detailed reason if upload was offered even with some missing fields and detailed reasons if it wasn't. jsaul@google.com aneeshali@google.com payments-autofill-team@google.com Detailed reasons why (or why not) card upload was enabled. When a user submits a form, this check is triggered to decide whether to ask the user if she wants to upload the card. jsaul@google.com chrome-autofill-alerts@google.com Tracks whether Credit Card Autofill is enabled on page load for a page containing forms. jsaul@google.com chrome-autofill-alerts@google.com Tracks whether Credit Card Autofill is enabled when Chrome launches. schwering@google.com chrome-autofill-alerts@google.com Records for each credit card form the quality of the fill. {AutofillSeamlessnessFillability} {AutofillSeamlessnessMeasurementTime} {AutofillSeamlessnessVisibility} The fields in question are: cardholder name (full, or first and last), credit card number, expiration date (MM/YY, MM/YYYY, MM and YY, or MM and YYYY), and CVC. Each bucket represents a minimal set of fields that must be autofilled. Lower numbers are better: Bucket 0 = name & number & exp. date & CVC = Full fill :-D Bucket 1 = number & exp. date & CVC = Optional name missing :-) Bucket 2 = name & number & exp. date = Optional CVC missing :-) Bucket 3 = number & exp. date = Optional name and CVC missing :-) Bucket 4 = name & number & CVC = Full fill but exp. date missing :-| Bucket 5 = all other scenarios = Partial fill :-( Any form that contains at least one credit card field counts as credit card form. schwering@google.com chrome-autofill-alerts@google.com Records for each credit card form the quality of the fill. {AutofillSeamlessnessFillability} {AutofillSeamlessnessMeasurementTime} {AutofillSeamlessnessVisibility} The emitted value is a non-zero bitmask whose bits have the following meaning, from highest to lowest bit: Bit #4 is true iff a cardholder name was filled. Bit #3 is true iff a card number was filled. Bit #2 is true iff an expiraton date was filled. Bit #1 is true iff a CVC name was filled. siyua@chromium.org payments-autofill-team@google.com The latency between an Autofill credit card suggestion being shown, and when it was selected, in milliseconds. Logged immediately when a card is selected by the user if the card has an issuer id, and it is broken down by whether the selected card has card metadata available. This is also broken down by card issuer id. This helps identify whether showing the card metadata has potential impact on latency for selecting a particular card. siyua@chromium.org payments-autofill-team@google.com The latency between Autofill credit card suggestion dropdown being shown, and when a suggestion was selected, in milliseconds. Logged immediately when a card suggestion is selected by the user. Broken down by whether any card (not necessarily the selected card) in the suggestion list has card metadata available. This helps identify whether showing the card metadata has potential impact on assisting card selection in general. Deprecated 01/23 and replaced by Autofill.CreditCard.SelectionLatencySinceShown.AnyCardWithMetadata.{CardMetadataVisible}. siyua@chromium.org payments-autofill-team@google.com The latency between Autofill credit card suggestion dropdown being shown, and when a suggestion was selected, in milliseconds. Logged immediately when a card suggestion is selected by the user, on the condition that any card (not necessarily the selected card) in the suggestion list has card metadata available (even if the metadata is not shown). This helps identify whether showing the card metadata has potential impact on assisting card selection in general. vishwasuppoor@chromium.org payments-autofill-team@google.com Emits true if a {CardIssuer}: 1. shown in Autofill suggestions had metadata 2. selected from Autofill suggestions had metadata Emits false if: 1. every {CardIssuer} shown in Autofill suggestions did not have metadata 2. a {CardIssuer} selected from Autofill suggestions did not have metadata Histograms without "Once" are logged every time Autofill suggestions that are shown or selected have an issuer id. Histograms with "Once" are logged once per page load. jsaul@google.com battre@chromium.org chrome-autofill-alerts@google.com The relative frequency with which users accept, deny, or ignore the Autofill credit card assisted filling infobar prompt. jsaul@google.com battre@chromium.org chrome-autofill-alerts@google.com The relative frequency with which users accept, deny, or ignore the Autofill credit card info bar prompt. {AutofillCreditCardInfoBarSaveType} Deprecated 10/2022. Will not launch save card Message UI. lazzzis@google.com jsaul@google.com chrome-autofill-alerts@google.com The relative frequency with which users accept, deny, or ignore the Autofill credit card message prompt when card is saved to server and users see the dialog prompt followed by the Message UI. Message prompt is an alternative UI to info bar prompt. Deprecated 10/2022. Will not launch save card Message UI. lazzzis@google.com jsaul@google.com chrome-autofill-alerts@google.com The relative frequency with which users accept, deny, or ignore the Autofill credit card message prompt when card is saved to {SaveDestination} and it is {SaveSituation}. Message prompt is an alternative UI to info bar prompt. jsaul@google.com chrome-autofill-alerts@google.com The relative frequency with which users accept, deny, or ignore the Autofill credit card prompt when card is saved to for a {SaveDestination} save, {SaveSituation}. Note that this metric concerns the result of final save, rather than the CTR of the prompt, and this metric should record when a decision of whether card will be saved or not is made. battre@chromium.org koerber@google.com chrome-autofill-alerts@google.com The number of local credit cards deleted during a major version upgrade because they have not been used recently enough and are expired. battre@chromium.org koerber@google.com chrome-autofill-alerts@google.com The number of credit card suggestions not shown in the Autofill popup because they have not been used recently enough and are expired. Note that suppression only applies when the user has not typed any text into the field. If any text is in the field, all matching cards are displayed, regardless of how recently they have been used and their expiration status. Deprecated 11/22. The feature is not going to be launched. siyua@chromium.org jsaul@google.com Records when credit card upload provides feedback on its status to the user. vinnypersky@google.com payments-autofill-team@google.com Emits true when a CVC authentication starts and does not emit any value otherwise. Broken down into sub-histograms based on the type of the card, for example virtual card or server card. vinnypersky@google.com payments-autofill-team@google.com Logs the result of the OTP authentication, broken down into sub-histograms by card type. The different possible results can be found in the AutofillCvcAuthEvent enum, with the exception of any retriable failure, which is logged in a separate histogram. This histogram is 1:1 with Autofill.CvcAuth.{CardType}.Attempt vinnypersky@google.com payments-autofill-team@google.com Logs any retryable failure that occurs during the CVC authentication flow. battre@chromium.org chrome-autofill-alerts@google.com Logs the number of days that have passed since the credit card was last used. battre@chromium.org chrome-autofill-alerts@google.com Logged at the time of autofill address use, this histogram captures the number of days that have passed since the address was last used. I.e., the distribution of time between uses of an "active" autofill address. battre@chromium.org chrome-autofill-alerts@google.com Logs the number of days that have passed since each credit card belonging to a given Chrome Profile was last used. This is logged for each Autofill credit card once per Chrome User Profile load. qihuizhao@google.com jsaul@google.com payments-autofill-team@google.com Logs the number of days that have passed since each IBAN belonging to a given Chrome Profile was last used. This is logged for each Autofill IBAN once per Chrome User Profile load. Deprecated in M111. Subsumed by Autofill.DaysSinceLastUse.StoredProfile.Legacy. battre@chromium.org chrome-autofill-alerts@google.com This histogram captures the number of days that have passed since each stored address profile belonging to a given Chrome Profile was last used. This is logged for each Autofill address profile once per Chrome User Profile load. battre@chromium.org chrome-autofill-alerts@google.com This histogram captures the number of days that have passed since each stored address profile belonging to a given Chrome Profile was last used. This is logged for each Autofill address profile of the given category once per Chrome User Profile load. battre@chromium.org chrome-autofill-alerts@google.com Measures the adoption of the HTML autocomplete type hint specification (see http://is.gd/whatwg_autocomplete for more details). For each fillable form detected, logs whether that form includes author-specified type hints. koerber@google.com battre@google.com Total number of fields at submission time that were autofilled and have or have not been editing by the user afterwards. koerber@google.com battre@google.com Total number of fields at submission time of a specific type that were autofilled and have or have not been editing by the user afterwards. koerber@google.com battre@google.com On submission time, this metric tracks for every field that was autofilled if the filling was accepted or subsequently corrected. This metric is aggregated over all field types. koerber@google.com battre@google.com On submission time, this metric tracks for every field that was autofilled if the filling was accepted or subsequently corrected. This metrics resolves the field type. siyua@chromium.org siashah@chromium.org jsaul@google.com Log when an autofill error dialog is shown to the user along with its type. The type here denotes the flows in which the dialog is shown. Such flows include virtual card retrieval, masked server card risk based authentication and etc. See "AutofillErrorDialogType" for details. vinnypersky@google.com siyua@chromium.org payments-autofill-team@google.com Logs when an autofill error dialog is shown along with its type. The type here denotes the flows in which the dialog is shown. Such flows include virtual card retrieval, masked server card risk based authentication and etc. See "AutofillErrorDialogType" for details. This is a secondary histogram to the "Autofill.ErrorDialogShown" and it is logged when server side returns text to override the static client-side error messages to be shown in the dialog. jsaul@google.com siashah@google.com payments-autofill-team@google.com Events tracking the usage of the expiration date fix flow prompt. This prompt is triggered whenever expiration date must be explicitly requested from the user in order to upload the card to Google Payments. jsaul@google.com siashah@google.com payments-autofill-team@google.com The number of times the expiration date fix flow prompt is shown. tchudakov@google.com chrome-autofill-alerts@google.com This metric measures how many users Clicked on the Delete Address option in the extended Autofill menu and the next action. The metric is logged when the user closes the delete address profile dialog. The experiment has been launched in 04/2022. evih@google.com schwering@google.com chrome-autofill-alerts@google.com In UpdateFormCache(), we compare FormData structs to re-extract changed ones. This metric records: - the number of times the shallow comparison is enough to identify a difference between the forms; - the number of times the deep comparison finds a difference between the forms, but the shallow does not; - the number of times none of the comparisons find a difference, i.e. the forms are equal. The metric takes into account every comparison of FormData structs in UpdateFormCache(). bwolfgang@google.com jkeitel@google.com vizcay@google.com Cache state for when a given origin and form signature are checked for their Fast Checkout trigger form capability. vizcay@google.com chrome-autofill-alerts@google.com The http response code or net error code returned on a query. bwolfgang@google.com jkeitel@google.com vizcay@google.com Parsing result of the response body of a Fast Checkout capabilities fetch. vizcay@google.com chrome-autofill-alerts@google.com Response time for fetching FastCheckout capabilities. The time is recorded for both successful and failed fetches. bwolfgang@google.com jkeitel@google.com vizcay@google.com The outcome of a Fast Checkout run. It is recorded when a run is completed, successfully or not, or when the run got cancelled, e.g. by the user closing the tab. bwolfgang@google.com jkeitel@google.com vizcay@google.com The outcome of an attempt to trigger a FastCheckout bottomsheet for a user that has the feature enabled and a form on a site for which FastCheckout is known to be available. vidhanj@google.com chrome-autofill-alerts@google.com Number of context menu impressions on fields by their autocomplete attribute value. Recorded on the form submission. vidhanj@google.com chrome-autofill-alerts@google.com Number of context menu impressions on fields by their autofill type. Recorded on the form submission. kolos@chromium.org battre@chromium.org chrome-autofill-alerts@google.com Number of fields in a form that Autofill encounters. koerber@google.com chrome-autofill-alerts@google.com For {AutofillFormType} logs an histogram of the number of fields with the {FillingStatus} at submission time. The non-aggregated FillingStatuses are mutually exclusive and each field can only contribute to one of corresponding histograms. However, the combined histograms that are prefixed with Total are not mutually exclusive and a single field can contribute to multiple of those. fleimgruber@google.com chrome-autofill-alerts@google.com Logs the index of the phone number grammar that matched. Emitted when parsing forms using local heuristics. Additionally logs whether the special case handling matched a suffix field. This pair is encoded as 2*grammar_index + matched_suffix + 1. battre@chromium.org chrome-autofill-alerts@google.com Aggregate Autofill field-type prediction outcomes. See https://en.wikipedia.org/wiki/Confusion_matrix for an explanation of the values. {AutofillFieldPredictionSource} battre@chromium.org chrome-autofill-alerts@google.com Autofill field-type prediction outcomes, broken down by field type. See https://en.wikipedia.org/wiki/Confusion_matrix for an explanation of the values. {AutofillFieldPredictionSource} battre@chromium.org chrome-autofill-alerts@google.com Predicted and actual form field type. This is a computed sparse histogram where the value is ((predicted << 16)| actual). Predicted and actual are taken from the autofill::ServerFieldType enumeration. {AutofillFieldPredictionSource} battre@chromium.org chrome-autofill-alerts@google.com Time elapsed between the user's first interaction with a form and the form's submission, for an autofilled form. An interaction requires changing a form control's value manually or via autofill. The interaction can happen on a different form than the one which is submitted. {AutofillFormType} battre@chromium.org chrome-autofill-alerts@google.com Time elapsed between the user's first interaction with a form and the form's submission, for a non-autofilled form. An interaction requires changing a form control's value manually or via autofill. The interaction can happen on a different form than the one which is submitted. {AutofillFormType} battre@chromium.org chrome-autofill-alerts@google.com Time elapsed between form load and form submission, for an autofilled form. battre@chromium.org chrome-autofill-alerts@google.com Time elapsed between form load and form submission, for a non-autofilled form. The experiment has been launched in 05/2022. evih@google.com schwering@google.com chrome-autofill-alerts@google.com Records the time spent to determine if a form control element, given by its unique renderer id, is in the DOM. It is done by measuring the time it takes for FindFormControlElementByUniqueRendererId() to execute. Note that histogram samples for clients without high-resolution clocks are dropped. The experiment has been launched in 05/2022. evih@google.com schwering@google.com chrome-autofill-alerts@google.com Records the time spent to determine if a vector of form control elements, given by their unique renderer ids, is in the DOM. It is done by measuring the time it takes for FindFormControlElementsByUniqueRendererId() to execute. Note that histogram samples for clients without high-resolution clocks are dropped. battre@google.com chrome-autofill-alerts@google.com Records for each submitted form that is affected by our "lax local heuristic rule" whether the user accepted filling an autofill suggestion. The "lax local heuristic rule" is that we require at least 3 fields to be classified by the local heuristic to propagate that classification - but we don't require 3 distinct field types, which would be the "stricter local heuristic rule". A form is affected if any field type would be different if we applied the stricter rule. {AutofillFormType} battre@google.com chrome-autofill-alerts@google.com Records for each submitted form that is affected by our "lax local heuristic rule" whether the user edited an autofilled field. The "lax local heuristic rule" is that we require at least 3 fields to be classified by the local heuristic to propagate that classification - but we don't require 3 distinct field types, which would be the "stricter local heuristic rule". A form is affected if any field type would be different if we applied the stricter rule. {AutofillFormType} The experiment has been launched in 04/2022. evih@google.com schwering@google.com chrome-autofill-alerts@google.com Records the peak number of the form cache size. The peak size is reached when navigating to a new page or when the page is refreshed. The metric is counted once for every loaded frame. vidhanj@google.com chrome-autofill-alerts@google.com Number of fields on form where the context menu was shown. Recorded on the form submission. battre@chromium.org koerber@google.com chrome-autofill-alerts@google.com Autofill form events for address forms. These are recorded when the user interacts with a form requesting an address. {AutofillDataAvailability} Important caveat about submission metrics: - Submission using autofill data is determined by simply evaluating if there was a fill operation in this page. So, if the user filled with local data, completed erased or modified the data after and then submitted, we would only emit one "Submitted with server suggestion filled (once)"; - The submission segmentation works by checking what kind of data was last filled for this type of form in the page load. So, if a user initially filled with local data and after that filled with server, we will only emit "Submitted with server suggestion filled (once)". siyua@chromium.org jsaul@google.com Autofill form events for credit card forms. These are recorded when the user interacts with a form requesting a credit card, a dropdown of suggestions is shown and at least one of the suggestions has a linked credit card offer. jsaul@google.com battre@chromium.org Autofill form events for credit card forms. These are recorded when the user interacts with a form requesting a credit card. {AutofillDataAvailability} Important caveat about submission metrics: - Submission using autofill data is determined by simply evaluating if there was a fill operation in this page. So, if the user filled with local data, completed erased or modified the data after and then submitted, we would only emit one "Submitted with server suggestion filled (once)"; - The submission segmentation works by checking what kind of data was last filled for this type of form in the page load. So, if a user initially filled with local data and after that filled with server, we will only emit "Submitted with server suggestion filled (once)". koerber@google.com chrome-autofill-alerts@google.com For {AutofillFormType} logs a filling complex score on form submission that is calculated as following: Score = 10 * number_of_accepted_fields + number_of_corrected_fields The score resembles a two dimensional histogram to evaluate the number of accepted fields against the number of corrected ones. Both number of fields used in the score are limited to 9 to guaranteed that the score will be within 0 and 99 and that the significant digit corresponds to the number of accepted fields while the least significant digit corresponds to the number of corrected fields. The score is only emitted when there is at least one correct or accepted field. koerber@google.com chrome-autofill-alerts@google.com For {AutofillFormType} logs a filling score on form submission that is calculated as following: Score = 2 * number_of_accepted_fields - 3 * number_of_corrected_fields + 100 The score is only emitted when there is at least one correct or accepted field. tmartino@chromium.org bling-transactions@google.com chrome-autofill-alerts@google.com Records whether the form was successfully filled by Autofill on iOS. schwering@google.com chrome-autofill-alerts@google.com Records the time it takes to retrieve a browser form for a given renderer form. (A renderer form is a single frame's form, whereas a browser form may or may not transcend multiple frames.) This corresponds to the duration of FormForest::GetBrowserFormOfRendererForm() and is emitted per each execution. Note that histogram samples for clients without high-resolution clocks are dropped. schwering@google.com chrome-autofill-alerts@google.com Records the time it takes to retrieve the renderer forms for a given browser form. (A renderer form is a single frame's form, whereas a browser form may or may not transcend multiple frames.) This corresponds to the duration of FormForest::GetRendererFormsOfBrowserForm() and is emitted per each execution. Note that histogram samples for clients without high-resolution clocks are dropped. schwering@google.com chrome-autofill-alerts@google.com Records the time it takes to update Autofill's form/frame tree. This corresponds to the duration of FormForest::UpdateTreeOfRendererForm() and is emitted per each execution. Note that histogram samples for clients without high-resolution clocks are dropped. schwering@google.com chrome-autofill-alerts@google.com Records nodes visited on a form/frame tree. This is emitted per each call of FormForest::UpdateTreeOfRendererForm() that actually does an entire tree traversal. rhalavati@chromium.org chrome-privacy-core@google.com This histogram records the browser profile type when an autofill form is submitted. battre@chromium.org chrome-autofill-alerts@google.com The autofill state related to a submitted form. fleimgruber@google.com chrome-autofill-team@google.com Like Autofill.Funnel.FillAfterSuggestion.Address, but conditioned on autocomplete=unrecognized fields. The metric is only recorded if the user saw a suggestion on an autocomplete=unrecognized field. On desktop, that means using the manual fallback option through the context menu. On mobile, keyboard accessory suggestions appear independently of the autocomplete attribute. Emitted on navigation (when the AutofillManager is destroyed), at most once per page. battre@chromium.org kolos@chromium.org nepper@chromium.org Counts whether users accepted any autofill suggestion that was shown to them for a given form. This metric is only recorded if a suggestion for the given form type (see histogram name) was shown at least once. This is recorded once per form. If the user accepts one suggestion, this is reported as "User chose to fill" once. It does not matter if the user clears the filled values nor if the user accepts a different suggestion later. {AutofillFormType} battre@chromium.org kolos@chromium.org nepper@chromium.org Counts whether users interacted with a form of a certain type. Focusing a field is sufficient to consider a form as being interacted with. The user does not need to type anything. Note that some forms may get focused on page load. This metric is recorded once per form observed by Autofill, but only for forms that Autofill classifies to be of the type indicated by the histogram name. If a form changes dynamically, Autofill interprets the forms before and after the change as two different forms and records two values. If a form did not have features that classify it as a form of a certain type (e.g. an address form or payment form), then nothing is recorded. {AutofillFormType} battre@chromium.org kolos@chromium.org nepper@chromium.org Counts whether a form was parsed/interpreted to be of the type indicated in the histogram name. This metric is recorded once for each form observed by Autofill. If a form changes dynamically, then Autofill treats the different versions of the form as different forms. {AutofillFormType} battre@chromium.org kolos@chromium.org nepper@chromium.org Counts whether users submitted a form that was filled via autofill. This metric is recorded once for each form observed by Autofill but only for forms that the user filled via Autofill. {AutofillFormType} battre@chromium.org kolos@chromium.org nepper@chromium.org Counts whether users were shown suggestions to fill the form, given that they have already interacted with the form. This metric is recorded only for forms that users interacted with. It is recorded only once per form, meaning that it does not matter how often the user sees suggestions. If a form changes dynamically, then Autofill treats the different versions of the form as different forms. {AutofillFormType} The experiment has been launched in 05/2022. evih@google.com schwering@google.com chrome-autofill-alerts@google.com Records the time it takes to get the unowned form field elements. This is done by measuring the time it takes for GetUnownedFormFieldElements() to execute. Note that histogram samples for clients without high-resolution clocks are dropped. The experiment has been launched in 05/2022. evih@google.com schwering@google.com chrome-autofill-alerts@google.com Records the time spent to determine if there is a password field in the web frame. It is done by measuring the time it takes for HasPasswordField() to execute. Note that histogram samples for clients without high-resolution clocks are dropped. battre@chromium.org chrome-autofill-alerts@google.com Logs when a hidden or presentational field is autofilled. The hidden or presentational fields are only autofilled for 'select' fields to support synthetic fields. qihuizhao@google.com jsaul@google.com payments-autofill-team@google.com Recorded when the user has IBANs and clicks on an IBAN form field. Logs whether IBAN suggestions were allowed to be shown, blocked from being shown, or if the blocklist was not accessible at all. qihuizhao@google.com jsaul@google.com payments-autofill-team@google.com These metrics are relevant to the IBAN suggestions popup, such as when it is shown or when a suggestion is selected. The IBAN-based suggestions popup gets displayed when a form's field that can be autofilled with an IBAN is selected, and the user has at least one IBAN saved. The metric is recorded upon each action, such as IBAN suggestions being shown or selected. The metric has not produced meaningful results. schwering@google.com chrome-autofill-alerts@google.com Counts per form submission the number of frames across which the form's autofilled credit card fields are distributed. A field is an "autofilled credit card field" if it is autofilled at submission time and its field type belongs to the credit card group. For example, emits 1 if all fields are in the same frame, and emits 2 if the fields live in two different frames. Never emits 0. The metric has not produced meaningful results. schwering@google.com chrome-autofill-alerts@google.com Counts per form submission the number of frames across which the form's detected credit card fields are distributed. A field is a "detected credit card field" if its field type belongs to the credit card group. For example, emits 1 if all fields are in the same frame, and emits 2 if the fields live in two different frames. Never emits 0. The metric has not produced meaningful results. schwering@google.com chrome-autofill-alerts@google.com Counts per form submission the number of frames across which the form's detected fields are distributed. A field is "detected" if its field type is neither EMPTY_TYPE or UNKNOWN_TYPE. For example, emits 1 if all fields are in the same frame, and emits 2 if the fields live in two different frames. Never emits 0. vishwasuppoor@chromium.org siyua@chromium.org payments-autofill-team@google.com Logs the roundtrip latency for fetching an image in AutofillImageFetcher. It is logged when the fetch request for image is completed. siyua@chromium.org payments-autofill-team@google.com Record the image fetch result of one image. If true, then the image was fetched successfully. battre@chromium.org jsaul@google.com chrome-autofill-alerts@google.com This includes Autofill.Address.IsEnabled.PageLoad and Autofill.CreditCard.IsEnabled.PageLoad, and tracks whether either profile Autofill or payment Autofill is enabled on page load for a page containing forms. It helps deduce the overlap by showing what percentage of users have one type of Autofill enabled but not the other. battre@chromium.org jsaul@google.com chrome-autofill-alerts@google.com This includes Autofill.Address.IsEnabled.Startup and Autofill.CreditCard.IsEnabled.Startup, and tracks whether either profile Autofill or payment Autofill is enabled when Chrome launches. It helps deduce the overlap by showing what percentage of users have one type of Autofill enabled but not the other. The experiment has been launched in 05/2022. evih@google.com schwering@google.com chrome-autofill-alerts@google.com Records the time spent to determine if at least one form control element among the given ones is visible and is in the web frame. It is done by measuring the time it takes for IsSomeControlElementVisible() to execute. Note that histogram samples for clients without high-resolution clocks are dropped. Deprecated in July 2022. Subsumed by Autofill.IsValueNotAutofilledOverExistingValueSameAsSubmittedValue2. vidhanj@google.com koerber@google.com chrome-autofill-alerts@google.com Records, for each field, that did not get autofilled due to a prefilled value, whether the submitted field value is the same as the non-empty value that could have been autofilled in the field. This metric is recorded on form submission. vidhanj@google.com koerber@google.com chrome-autofill-alerts@google.com This metric is recorderd on form submission for each field that had an initial value on page load and was edited by the user later on. The result of the equality comparison between the submitted field value and supposedly autofillable value is emitted by this metric. battre@chromium.org kolos@chromium.org nepper@chromium.org Counts for submitted forms whether users accepted the suggestion to fill values. This is counted as 'yes' if the user accepted such a suggestion at any time, regardless whether other suggestions were ignored or whether the accepted suggestion was reverted afterwards. {AutofillFormType} battre@chromium.org kolos@chromium.org nepper@chromium.org Counts for submitted forms whether the user filled any fields via Autofill. If the user reverts the filling, the form is still counted as filled. This metric is different from Autofill.KeyMetrics.FillingAcceptance in the sense that the latter is only recorded if the user has actually seen a prompt to fill data. {AutofillFormType} battre@chromium.org kolos@chromium.org nepper@chromium.org Counts for submitted and autofilled forms whether users edited at least one filled value before submitting the form. {AutofillFormType} battre@chromium.org kolos@chromium.org nepper@chromium.org Counts for submitted forms whether Chromium had any address or payments data to fill. It does not matter whether the user actually requested to fill the data. It does not matter either whether the data available for filling corresponded to the submitted data. {AutofillFormType} battre@chromium.org kolos@chromium.org nepper@chromium.org Counts for filled (by Autofill) forms whether users submitted those forms. This is only recorded for forms that the user filled via Autofill. It does not matter if the user reverted the filling afterwards. This is recorded once Autofill stops tracking the form (e.g. due to a navigation or due to removal from the DOM). {AutofillFormType} battre@chromium.org kolos@chromium.org nepper@chromium.org Counts for not filled (by Autofill) forms whether users submitted those forms. This is only recorded for forms into which the user typed anything but did not fill anything. It does not matter if the user reverted what they typed. This is recorded once Autofill stops tracking the form (e.g. due to a navigation or due to removal from the DOM). {AutofillFormType} fleimgruber@google.com chrome-autofill-team@google.com Logs how/if the label of an input was derived. Emitted at form submission for every field where the data the user entered matches some stored Autofill data. koerber@google.com fleimgruber@google.com chrome-autofill-team@google.com Logs the number of kLocalOrSynable profiles that are a strict superset of some kAccount profile. This corresponds to the number of profiles that cannot be automatically deduplicated, since no profiles should be silently deleted from the account storage. Emitted when the Chrome user profile is loaded. koerber@chromium.org fleimgruber@chromium.org chrome-autofill-team@google.com Like Autofill.KeyMetrics.FillingAssistance.Address, but split by profile category. koerber@chromium.org fleimgruber@chromium.org chrome-autofill-team@google.com Like Autofill.KeyMetrics.FillingCorrectness.Address, but split by profile category. siyua@chromium.org jsaul@google.com Record events related to bubble showing. Logged when bubble is requested or is actually shown to users. siyua@chromium.org jsaul@google.com Records whether and how the local card migration bubble was accepted or closed. siyua@chromium.org jsaul@google.com Record how bubble is closed by different user interactions. sujiezhu@google.com siyua@chromium.org jsaul@google.com Record the decisions made when determining if local card migration should be offered. siyua@chromium.org jsaul@google.com Record duration of the local card migration dialog being visible to users. {AutofillLocalCardMigrationDialogDurationWithCloseEvent} siyua@chromium.org jsaul@google.com Record events related to showing the local card migration dialog. siyua@chromium.org jsaul@google.com Record user interactions related to local card migration dialog. siyua@chromium.org jsaul@google.com Record the percentage of cards selected by the user in the migration dialog. siyua@chromium.org jsaul@google.com Records when local card migration prompts are shown and/or accepted. {AutofillLocalCardMigrationOrigin} battre@chromium.org chrome-autofill-alerts@google.com The number of log events of type {LogEventTypes} which have been recorded until the FieldInfo metric is recorded into UKM at form submission or form destruction time (whatever comes first). jsaul@google.com siyua@chromium.org The frequency of user interactions with the Manage Cards prompt. {AutofillManageCardsPrompt} fleimgruber@google.com chrome-autofill-team@google.com Records the acceptance of manual fallback suggestions, by tracking the number of times a user accepted/didn't accept the manual fallback option in the context menu. Emitted on navigation (when the AutofillManager is destroyed), at most once per page. Deprecated in M109 as this migration never applied to ChromeOS ASH. msarda@google.com payments-autofill-team@google.com This metric is recorded when the bit that indicates the user is opted in to wallet sync transport is migrated (part of the migration from using email to using Gaia ID as the account identifier). koerber@google.com chrome-autofill-alerts@google.com For each {NameType} in a given AutofillProfile, the verification status of the corresponding non-empty type is recorded when a profile is used to fill a form. jihadghanna@google.com chrome-autofill-alerts@google.com Logs whether a street address merge operation favored the new or old address because of the feature `kAutofillConvergeToExtremeLengthStreetAddress`. koerber@google.com chrome-autofill-alerts@google.com The {AcceptanceStatus} autofilled fields in a form after receiving a form submission event. koerber@google.com chrome-autofill-alerts@google.com The {AcceptanceStatus} of autofilled fields with an unrecognized autocomplete attribute in a form after receiving a form submission event. battre@chromium.org chrome-autofill-alerts@google.com The number of autofilled fields that were subsequently edited prior to the form being submitted. battre@chromium.org chrome-autofill-alerts@google.com The number of Autofill profiles that have been considered for deduplication. battre@chromium.org chrome-autofill-alerts@google.com The number of Autofill profiles that have been removed during deduplication. battre@chromium.org chrome-autofill-alerts@google.com Records whether the number of fillable form elements matches the number of fields in the form's description. Instances where this is recorded as False, denote cases where autofill failed to preview/fill an autofill suggestion. This can happen when a fields is filtered out of a formless form. koerber@google.com chrome-autofill-alerts@google.com Logs that a field with a heuristic prediction for an NUMERIC_QUANTITY collides with a server prediction. The metric is emitted on form submission. siyua@chromium.org jsaul@google.com When at least one of the cards in the Autofill suggestions list has a linked offer and the user selects a suggestion, this metric records whether or not the selected suggestion had a linked offer. Nothing is recorded if none of the cards suggested have linked offers. Deprecated in June 2022. Subsumed by Autofill.Offer.StoredOfferCount.{OfferType}. siyua@chromium.org payments-autofill-team@google.com Tracks the number of autofill offers data a user has stored, measured at Chrome profile launch time. Deprecated in August 2022. Subsumed by Autofill.Offer.StoredOfferCount2.{OfferType}. siyua@chromium.org payments-autofill-team@google.com Tracks the number of Autofill offers a user has stored, separated by offer type, and measured at Chrome profile launch time. siyua@chromium.org jsaul@google.com Tracks the number of Autofill offers a user has stored (including if the user has zero offers), separated by offer type, and measured at Chrome profile launch time. siyua@chromium.org jsaul@google.com Tracks the number of the credit cards an autofill card linked offer data is related to, measured at Chrome profile launch time. Deprecated in August 2022. Subsumed by Autofill.Offer.StoredOfferRelatedMerchantCount.{OfferType}. siyua@chromium.org payments-autofill-team@google.com Tracks the number of the merchants an autofill offer data is related to, measured at Chrome profile launch time. siyua@chromium.org jsaul@google.com Tracks the number of the merchants an autofill offer data is related to, separated by offer type, and measured at Chrome profile launch time. siyua@chromium.org jsaul@google.com When at least one of the cards in the Autofill suggestions list has a linked offer and the user submits the form, this metric records whether or not the form was submitted using the card with a linked offer. Nothing is recorded if none of the cards suggested have linked offers. siyua@chromium.org jsaul@google.com When the user is shown the Autofill suggestions list, this metric records whether or not a credit card that is linked to an offer is shown as part of the suggestions. Deprecated August 2022. Subsumed by Autofill.Offer.Suggestion2.{OfferType}. vinnypersky@google.com jsaul@google.com payments-autofill-team@google.com This metric is recorded every time an event related to an individual offer suggestion in the offers suggestions popup gets triggered. The offers suggestions popup gets displayed when a form's field that can be autofilled with an offer is selected. vinnypersky@google.com jsaul@google.com payments-autofill-team@google.com This metric is recorded every time an event related to an individual offer suggestion in the offers suggestions popup gets triggered. The offers suggestions popup gets displayed when a form's field that can be autofilled with an offer is selected, and there is no promo code already filled into the field. This histogram is different from Autofill.Offer.Suggestion.{OfferType} because Autofill.Offer.Suggestion.{OfferType} logged that suggestions were shown when a promo code was already filled into the field and the field was clicked again, but in this case suggestions would not have been shown due to the field already having a full value. Since we updated the logic for when this histogram is logged to, we also needed to create a new histogram. Deprecated August 2022. Subsumed by Autofill.Offer.SuggestionsPopupShown2. vinnypersky@google.com jsaul@google.com payments-autofill-team@google.com This metric records two enums, one for every time the offers suggestions popup is shown, and another for that same event, but only one per unique field. The offers suggestions popup is shown when a form's field that can be autofilled with an offer is selected. vinnypersky@google.com jsaul@google.com payments-autofill-team@google.com This metric records two enums, one for every time the offers suggestions popup is shown, and another for that same event, but only one per unique field. The offers suggestions popup is shown when a form's field that can be autofilled with an offer is selected, and there is no promo code already filled into the field. This histogram is different from Autofill.Offer.SuggestionsPopupShown because Autofill.Offer.SuggestionsPopupShown logged that suggestions were shown when a promo code was already filled into the field and the field was clicked again, but in this case suggestions would not have been shown due to the field already having a full value. Since we updated the logic for when this histogram is logged to, we also needed to create a new histogram. siyua@chromium.org jsaul@google.com Tracks whether the offer data is valid or not, measured whenever offer data is synced down via Sync. meiliang@chromium.org chrome-shopping@google.com Records whether the offer notification bubble is shown from the History Cluster or normal navigations. It emits true for History Cluster and false for normal navigation. This is recorded when the bubble is shown. siyua@chromium.org jsaul@google.com payments-autofill-team@google.com Records whether the offer notification bubble is the first such offer that the user has been shown or is reshown due to user actions. The metric is recorded when the bubble is shown. meiliang@chromium.org chrome-shopping@google.com Records whether the copy promo code button is clicked on the offer notification bubble from History Cluster or normal navigations. It emits true for History Cluster and false for normal navigation. This is recorded when the copy promo code button on the offer notification bubble is clicked by the user. jsaul@google.com siyua@chromium.org payments-autofill-team@google.com Records when the copy promo code button for an offer notification bubble is clicked by the user. The subhistogram is the type of offer shown, such as GPay promo code offer or free-listing coupon offer. siyua@chromium.org jsaul@google.com payments-autofill-team@google.com Records the reason for closing the offer notification bubble. Recorded when the bubble is closed. jsaul@google.com yuezhanggg@chromium.org siyua@chromium.org payments-autofill-team@google.com chrome-shopping@google.com Records when the offer notification bubble should show but gets suppressed due to reasons like show frequency rate control. The subhistogram is the type of offer shown, such as GPay promo code offer or free-listing coupon offer. siashah@chromium.org siyua@chromium.org payments-autofill-team@google.com Emits true when the offer notification infobar is displayed and does not emit any value otherwise. siashah@chromium.org siyua@chromium.org payments-autofill-team@google.com Records the reason for closing the offer notification infobar for {OfferType}. Recorded when the infobar is closed. siyua@chromium.org payments-autofill-team@google.com Emits true when an OTP authentication starts and does not emit any value otherwise. siyua@chromium.org payments-autofill-team@google.com Logs the roundtrip latency of the SelectChallengeOptionRequest in the OTP authentication. siyua@chromium.org payments-autofill-team@google.com Logs the roundtrip latency of the UnmaskCardRequest in the OTP authentication. siyua@chromium.org payments-autofill-team@google.com Logs the result of the OTP authentication. siyua@chromium.org payments-autofill-team@google.com Logs any retriable failure before the OTP authentication completes. siyua@chromium.org payments-autofill-team@google.com Logs the type of the error when any temporary error is shown in the card unmask OTP dialog. siyua@chromium.org payments-autofill-team@google.com Emits true when the "Get New Code" button is clicked and a new OTP is requested. Doesn't emit any other value. siyua@chromium.org payments-autofill-team@google.com Logs the reason of the closure when the card unmask OTP dialog is closed. siyua@chromium.org payments-autofill-team@google.com Logs the reason of the closure when the card unmask OTP dialog is closed. This breaks down on whether any temporary error happened before the card unmask OTP dialog was closed. siyua@chromium.org payments-autofill-team@google.com Emits true when the card unmask OTP dialog is shown. Doesn't emit any other value. meiliang@chromium.org chrome-shopping@google.com Records whether the offer notification icon is shown due to the navigation from History Cluster or normal navigation. It emits true for History Cluster and false for normal navigation. This is recorded when the offer notification omnibox icon is shown for a FreeListing coupon. meiliang@chromium.org chrome-shopping@google.com Emits true if the offer notification icon is currently being shown in the omnibox after a page navigation for {OfferType}. Doesn't emit any other value. koerber@google.com chrome-autofill-team@google.com Tracks whether the visible page language was translated or not upon form submission. sujiezhu@google.com payments-autofill-team@google.com Tracks the users mandatory reauth result during the checkout flow for opted-in users breakdown by each card type and each authentication method. Whenever a reauth opted-in user starts, succeeds or fails the mandatory reauth flow during a payments autofill form fill, we will log the MandatoryReauthAuthEvent to this histogram. This is logged in order to get the reauth usages and corresponding success rate for each breakdown. This subhistogram pertains to {CardType}s that used {AuthenticationMethod} during the checkout flow. koulvipul@google.com payments-autofill-team@google.com Tracks the auth result when the user tries to edit a local card and mandatory reauth feature is enabled. Whenever a user tries to edit the card from the Settings page, we will log into the `flow started` bucket. The user would then be challenged with an auth, where if the auth was successful, we will log in the `flow succeded` bucket, else we will log in the `flow failed` bucket. vinnypersky@google.com sujiezhu@google.com payments-autofill-team@google.com Logs the detailed reason why (or why not) mandatory reauth opt-in was offered during a credit card checkout flow. Whenever we determine whether to offer the mandatory reauth opt-in prompt, we will log the decision result to this histogram. koulvipul@google.com payments-autofill-team@google.com Tracks the users auth result during the {ChangingStatus} flow for the mandatory reauth feature. Whenever a user triggers to change the mandatory reauth feature from the {Source}, we will log into the `flow started` bucket. The user would then be challenged with an auth, where if the auth was successful, we will log in the `flow succeded` bucket, else we will log in the `flow failed` bucket. justinleewells@google.com payments-autofill-team@google.com Tracks events related to offering the mandatory reauth opt-in feature, for instance when it is shown or why it is not shown. This metric is recorded when the mandatory reauth opt-in prompt is or is not displayed. Mandatory reauth requires the user to unlock their device or pass a biometric auth when autofilling payment method information. justinleewells@google.com payments-autofill-team@google.com Tracks the reason the mandatory reauth opt-in prompt was closed. This metric is recorded when the user closes the mandatory reauth opt-in prompt. Mandatory reauth requires the user to unlock their device or pass a biometric auth when autofilling payment method information. justinleewells@google.com payments-autofill-team@google.com Tracks various events related to the mandatory reauth opt-in confirmation prompt. These metrics are recorded when the prompt is displayed or the user interacts with the prompt. Mandatory reauth requires the user to unlock their device or pass a biometric auth when autofilling payment method information. koerber@google.com chrome-autofill-alerts@google.com For a form of type {FormType}, log at submission time if the filling experience was perfect. In a perfect filling experience, all non-empty fields have been autofilled without subsequent corrections. Note that the {FormType} is not mutually exclusive. If a single form contains both address and credit card information, the metric is recorded for each {FormType}. In such a combined form, both the address and the credit card information needs to be filled perfectly, in order to record perfect filling. mreichhoff@chromium.org kaklilu@chromium.org Records user interactions with the experimental plus addresses modal, which provides context for new plus addresses and gives the user a chance to opt out if desired. Written when the user clicks either of the cancel or ok buttons, and when the modal is presented to the user. mreichhoff@chromium.org kaklilu@chromium.org Records any OAuth error that the experimental plus addresses feature encounters. This is recorded when the PlusAddressClient needs to fetch an OAuth token to make a network request. This enum also captures the non-error case with NONE. mreichhoff@chromium.org kaklilu@chromium.org Measures the latency of network requests made by the experimental plus addresses feature. Latency is measured as the difference between when the PlusAddressClient issues the request and when it receives a response. The PlusAddressClient records this whenever it gets a response for the network requests it makes. mreichhoff@chromium.org kaklilu@chromium.org Records the response body size of network requests made by the experimental plus addresses feature. The PlusAddressClient records this whenever it gets a response for the network requests it makes. mreichhoff@chromium.org kaklilu@chromium.org Records HTTP response codes of network requests made by the experimental plus addresses feature. The PlusAddressClient records this whenever it gets a response for the network requests it makes. mreichhoff@chromium.org kaklilu@chromium.org Records user interactions with the experimental plus addresses feature in autofill. Includes suggestions and clicks of both new plus address creation suggestions and existing plus address filling suggestions. Recorded when the suggestions are shown, and when they are chosen. jkeitel@google.com brunobraga@google.com derinel@google.com Records instances in which the user attempted to accept an Autofill suggestion within less than the acceptance threshold (500ms). For those cases, it measures how long the user took to interact. koerber@google.com mamir@chromium.org This tracks the reasons for which the Autofill popup disappers or cannot be displayed. Recorded everytime an Autofill popup disappears or cannot be displayed. battre@chromium.org chrome-autofill-alerts@google.com The profile action that took place when a form was submitted. fleimgruber@google.com chrome-autofill-team@google.com Logs that a given field type was removed on import, due to being setting inaccessible in the imported profile's country. Emitted on profile import. fleimgruber@google.com chrome-autofill-team@google.com Logs if at least one field was removed on import, due to being setting inaccessible in the imported profile's country. Emitted on profile import. koerber@google.com fleimgruber@google.com src/components/autofill/OWNERS Logs the user's decision for migrating a stored profile with source AutofillProfile::Source::kLocalOrSyncable to the account storage. This metric is emitted at the end of an import process once the user-provided import decision is final. koerber@google.com fleimgruber@google.com src/components/autofill/OWNERS Logs that a specific type was edited in a profile migration prompt. This metric is emitted once the user-provided import decision is final. koerber@google.com fleimgruber@google.com src/components/autofill/OWNERS Logs the number of fields that have been edited by the user in the process of succesfully migrating a profile after an observed form submission. koerber@google.com src/components/autofill/OWNERS Logs the user's decision for storing a new address profile observed in a form submission. This metric is emitted at the end of an import process once the user-provided import decision is final. koerber@google.com src/components/autofill/OWNERS Logs that a specific type was edited in a new profile save prompt that was shown to the user when a new address profile is observed in a form submission. This metric is emitted once the user-provided import decision is final. fleimgruber@google.com chrome-autofill-team@google.com Logs the number of fields with an unrecognized autocomplete attributed that were considered for the import due to AutofillFillAndImportFromMoreFields. Emitted at the end of an import process, once the user-provided import decision is final. koerber@google.com src/components/autofill/OWNERS Logs the number of fields that have been edited by the user in the process of succesfully importing a new profile after an observed form submission. fleimgruber@google.com chrome-autofill-team@google.com Logs if a phone number was parsed successfully on profile import. Only emitted when a number is present in the submitted form. koerber@google.com src/components/autofill/OWNERS The type of an import of an address that is observed in a form submission. This metric is emitted once the import decision is final. This does not necessarily mean that the user was prompted. koerber@google.com src/components/autofill/OWNERS The type of an import of an address that is observed in a form submission when the form does not satisfy profile import requirements. This metric is emitted once the import decision is final. koerber@google.com src/components/autofill/OWNERS Logs that a specific type would have changed in a profile update process that received a specific {Decision}. The update was shown to the user because a profile similar to an already existing profile was observed in a form submission. Note that this metric collects the changed types before the user potentially applies additional edits. The metric is recorded on form submission once the user decision is final. koerber@google.com src/components/autofill/OWNERS Logs the user's decision for editing an already existing address after a similar profile was observed in a form submission. This metric is emitted at the end of an import process once the user-provided import decision is final. koerber@google.com src/components/autofill/OWNERS Logs that a specific type was edited in a profile update prompt that was shown to the user when a profile similar to an already existing profile was observed in a form submission. This metric is emitted once the user-provided import decision is final. koerber@google.com src/components/autofill/OWNERS Logs the number of fields that would be changed by an accepted update for any possible Decision. Note that this metric collects the number of changed fields before the user potentially applies additional edits. The metric is recorded on form submission once the user decision is final. fleimgruber@google.com chrome-autofill-team@google.com Logs the number of fields with an unrecognized autocomplete attributed that were considered for the update due to AutofillFillAndImportFromMoreFields. Emitted at the end of an update process, once the user-provided update decision is final. koerber@google.com src/components/autofill/OWNERS Logs the number of fields that have been edited by the user in the process of succesfully updating an existing profile after an observed form submission. jihadghanna@chromium.org chrome-autofill-alerts@google.com Given a field set S containing an address field type, logs whether two profiles A and B, where A is a subset of B with respect to the field type set S minus the address field types, have different values for those address field types. battre@chromium.org src/components/autofill/OWNERS This metric is recorded when the autofill-use-improved-label-disambiguation experiment is enabled and profile suggestions are available. This metric measures how often suggestions were created with and without a formatter. Warning: this histogram was expired from 2020-09-30 to 2022-04-07; data may be missing. siashah@chromium.org siyua@chromium.org jsaul@google.com payments-autofill-team@google.com Records the result of the progress dialog, which can either be canceled (user canceled while it was in progress) or not canceled (user waited until confirmation). This dialog is shown in between other dialogs in a flow to provide a progress state to the user. If the user does not cancel it, after its related background task completes it moves on to the next dialog in the flow that it is a part of. The metric is recorded when this dialog is dismissed, and the result that gets logged is false if the user waited until confirmation or true if the user canceled the dialog. siashah@chromium.org siyua@chromium.org jsaul@google.com payments-autofill-team@google.com Records true every time the progress dialog is shown. This dialog is shown in between other dialogs in a payments autofill flow to provide a progress state to the user. If the user does not cancel it, after its related background task completes it moves on to the next dialog in the flow that it is a part of. battre@chromium.org chrome-autofill-alerts@google.com For credit card forms that are queried for Autofill, a ratio of how many are within secure contexts (which includes mixed passive content). battre@chromium.org chrome-autofill-alerts@google.com The delay of a network request for a query due to exponential backoff. battre@chromium.org chrome-autofill-alerts@google.com The number of bytes that were sent in a query that subsequently failed. This is to help determine the appropriate threshold at which autofill queries should switch from GET to POST, and if there are certain sizes of queries which are prone to failure. battre@chromium.org chrome-autofill-alerts@google.com The http response code or net error code returned on a query. battre@chromium.org chrome-autofill-alerts@google.com The HTTP method used to query the autofill server. battre@chromium.org chrome-autofill-alerts@google.com The duration of a network request for a query. battre@chromium.org chrome-autofill-alerts@google.com Was the autofill query response retrieved from the HTTP cache. battre@chromium.org chrome-autofill-alerts@google.com The quality of fields rationalization, putting rationalization result into good/ok/bad categories. jsaul@google.com payments-autofill-team@google.com If the cardholder name fix flow is shown when credit card upload is offered, records if the cardholder name textfield was prefilled with the name from the user's Google Account. jsaul@google.com payments-autofill-team@google.com If the cardholder name fix flow is shown during credit card upload and the user accepts upload, logs whether the final cardholder name was changed from its prefilled value or not. jsaul@google.com siyua@chromium.org payments-autofill-team@google.com Records the reason expiration date was explicitly requested from the user during credit card save. jsaul@google.com siyua@chromium.org payments-autofill-team@google.com The relative frequency with which the Autofill save credit card prompt is shown or not to save credit card {AutofillSaveCreditCardPromptDestination}. Logged when the flow is triggered and the prompt should be shown. jsaul@google.com siyua@chromium.org payments-autofill-team@google.com The relative frequency with which users accept or deny the Autofill save credit card prompt to save credit card {AutofillSaveCreditCardPromptDestination}. Logged when the prompt closes. vishwasuppoor@google.com siyua@chromium.org payments-autofill-team@google.com The relative frequency with which the Autofill save CVC prompt is shown or not to save CVC {AutofillSaveCreditCardPromptDestination}. Logged when the flow is triggered and the prompt should be shown. It was a {ShowType}. vishwasuppoor@google.com siyua@chromium.org payments-autofill-team@google.com The relative frequency with which users accept or deny the Autofill save CVC prompt to save CVC {AutofillSaveCreditCardPromptDestination}. Logged when the prompt closes. It was a {ShowType}. jsaul@google.com qihuizhao@google.com payments-autofill-team@google.com Records every time the save IBAN bubble or omnibox icon (due to maxstrike reached) is offered to the user, broken down by destination and show type. jsaul@google.com payments-autofill-team@google.com Records when the user accepts the bubble to save an IBAN, with or without nickname. jsaul@google.com qihuizhao@google.com payments-autofill-team@google.com Records when the user makes a decision on the save IBAN bubble, broken down by destinations. battre@chromium.org chrome-autofill-alerts@google.com Whether a credit card scan was completed or cancelled. battre@chromium.org chrome-autofill-alerts@google.com How long a credit card took to scan. {CreditCardScanSuccess} battre@chromium.org koerber@chromium.org chrome-autofill-alerts@google.com Usage of the "Scan card" control item. fleimgruber@google.com schwering@google.com chrome-autofill-alerts@google.com The number of fields per section after sectioning a form using kAutofillUseParameterizedSectioning. Only considers fields that may actually be autofilled: fields that (a) are either focusable or a select field, and (b) have a fillable type (e.g., UNKNOWN_TYPE and NUMERIC_QUANTITY are not fillable). Emitted once per section every time sectioning is done. fleimgruber@google.com schwering@google.com chrome-autofill-alerts@google.com The number of sections after sectioning a form using kAutofillUseParameterizedSectioning. Only considers fields that may actually be autofilled: fields that (a) are either focusable or a select field, and (b) have a fillable type (e.g., UNKNOWN_TYPE and NUMERIC_QUANTITY are not fillable). Emitted every time sectioning is done. jsaul@google.com battre@chromium.org chrome-autofill-alerts@google.com Logged when the user clicks on the server credit card link in the settings page. siyua@chromium.org payments-autofill-team@google.com Emits true when a server card unmasking process starts and does not emit any value otherwise. siyua@chromium.org payments-autofill-team@google.com Emits true when a form is submitted with information fetched in a server card unmasking process, and does not emit any value otherwise. siyua@chromium.org payments-autofill-team@google.com Logs the result of a server card unmasking process when the unmasking is finished (whether it succeeded or otherwise reason of the failure). It includes the type of the card to be unmasked and the flow type (what authentication used) in the unmasking. battre@chromium.org chrome-autofill-alerts@google.com The usefulness of Autofill server information. battre@chromium.org chrome-autofill-alerts@google.com Tracks whether Autofill server had at least some prediction data for a given form at query response time. fhorschig@chromium.org chrome-autofill-alerts@google.com Records which entry point opened the Autofill Options screen. Recorded on Android. fhorschig@chromium.org chrome-autofill-alerts@google.com Records true whenever the user opts into the third party autofill experience. Records false whenever they switch back to the default, Chrome-provided autofill experience. Recorded when the user flips the toggle in the autofill options settings. vishwasuppoor@chromium.org siashah@chromium.org payments-autofill-team@google.com Emits true whenever {Button} is clicked in the mobile {CardType} edit page. Never emits false. schwering@google.com fleimgruber@google.com chrome-autofill-team@google.com 3-way comparison between {SourcePair} and the value that was in a field on submission. This is emitted after an autofillable form has been submitted. battre@chromium.org chrome-autofill-alerts@google.com Records whether an autofill operation was skipped because the number of fields to be filled is different than that number of fields registered in the form cache. siashah@chromium.org jsaul@google.com payments-autofill-team@google.com Emits true when the action button on the autofill snackbar is clicked and does not emit any value otherwise. siashah@chromium.org jsaul@google.com payments-autofill-team@google.com Emits true when the autofill snackbar is displayed and does not emit any value otherwise. jsaul@google.com battre@chromium.org chrome-autofill-alerts@google.com The number of credit cards a user has stored, measured at Chrome profile launch time. siyua@chromium.org payments-autofill-team@google.com The number of server cards with a valid card art image, measured at Chrome profile launch. siyua@chromium.org payments-autofill-team@google.com The number of server cards with virtual card metadata, measured at Chrome profile launch. battre@chromium.org chrome-autofill-alerts@google.com The number of disused credit cards a user has stored, measured at Chrome profile launch time. This is only reported for users who have at least one stored credit card. qihuizhao@google.com jsaul@google.com payments-autofill-team@google.com The number of local IBANs a user has stored, measured at Chrome profile launch time. It's logged once per profile loaded. qihuizhao@google.com jsaul@google.com payments-autofill-team@google.com The number of local IBANs with nickname a user has stored, measured at Chrome profile launch time. It's logged one per profile loaded. qihuizhao@google.com jsaul@google.com payments-autofill-team@google.com The number of disused IBANs a user has stored, measured at Chrome profile launch time. This is only reported for users who have at least one stored IBAN. Deprecated in M111. Subsumed by Autofill.StoredProfileCount.Legacy. battre@chromium.org chrome-autofill-alerts@google.com The number of Autofill addresses a user has stored, measured at launch time. battre@chromium.org chrome-autofill-alerts@google.com The number of Autofill addresses a user has stored of the given category, measured at launch time. battre@chromium.org chrome-autofill-alerts@google.com The number of Autofill addresses a user has stored, measured when an autofillable form is submitted. Deprecated in M111. Subsumed by Autofill.StoredProfileDisusedCount.Legacy. battre@chromium.org chrome-autofill-alerts@google.com The number of stored Autofill address profiles which have not been used in a sufficiently long time for autofill to consider them disused. Measured once per Chrome user profile launch. This metric is only recorded if the user has at least one profile. battre@chromium.org chrome-autofill-alerts@google.com The number of stored Autofill address profiles of the given category, which have not been used in a sufficiently long time for autofill to consider them disused. Measured once per Chrome user profile launch. This metric is only recorded if the user has at least one profile of that category. Deprecated in M111. Subsumed by Autofill.StoredProfileUsedCount.Legacy. koerber@google.com chrome-autofill-alerts@google.com The number of stored Autofill address profiles which are not in the disused state. Measured once per Chrome user profile launch. This metric is only recorded if the user has at least one profile. koerber@google.com chrome-autofill-alerts@google.com The number of stored Autofill address profiles of the given category, which are not in the disused state. Measured once per Chrome user profile launch. This metric is only recorded if the user has at least one profile of that category. Deprecated in M111. Subsumed by Autofill.StoredProfileUsedPercentage.Legacy. koerber@google.com chrome-autofill-alerts@google.com The percentage of stored Autofill address profiles which are not in the disused state. Measured once per Chrome user profile launch. This metric is only recorded if the user has at least one profile. koerber@google.com chrome-autofill-alerts@google.com The percentage of stored Autofill address profiles of the given category, which are not in the disused state. Measured once per Chrome user profile launch. This metric is only recorded if the user has at least one profile of that category. fleimgruber@google.com chrome-autofill-alerts@google.com The number of Autofill profiles of type kLegacyOrSyncable without a country a user has stored, measured at launch time. This metric is only recorded if the user has at least one kLegacyOrSyncable profile. jsaul@google.com payments-autofill-team@google.com Records when credit card save is not offered (either at all on mobile or by simply not showing the bubble on desktop) due to the candidate card having too many strikes. qihuizhao@google.com jsaul@google.com payments-autofill-team@google.com Records when IBAN save prompt is not offered due to the candidate IBAN having too many strikes. It is recorded when offering IBAN save to user and detects the max strikes has been reached. jsaul@google.com payments-autofill-team@google.com Records when local card migration is not offered due to the candidate's LocalCardMigration strike count reaching maximum strikes. jsaul@google.com payments-autofill-team@google.com Records the number of "strikes" a particular feature has when a new strike is added for that feature. {AutofillStrikeDatabaseProjectType} jsaul@google.com payments-autofill-team@google.com When a StrikeDatabase fails to initialize, records the number of consecutive failed initialization attempts. qihuizhao@google.com jsaul@google.com payments-autofill-team@google.com Records the number of "strikes" a given IBAN had when a user decided to save it. It is recorded right after the user clicks the Accept button. jsaul@google.com payments-autofill-team@google.com Records the number of "strikes" a user has when local card migration is accepted. jsaul@google.com payments-autofill-team@google.com Records the number of "strikes" a given card had when a user opted to save the card to Chrome. jsaul@google.com payments-autofill-team@google.com Records the number of "strikes" a given card had when a user successfully uploaded the card to Google Payments. jsaul@google.com payments-autofill-team@google.com Records the number of "strikes" present in a StrikeDatabase entry when a strike expires. {AutofillStrikeDatabaseProjectType} jsaul@google.com siyua@chromium.org payments-autofill-team@google.com Records the number of "strikes" a given card had when a user successfully enrolled in a virtual card. jsaul@google.com siyua@chromium.org payments-autofill-team@google.com Records and emits true when virtual card enrollment is not offered due to the candidate's strike count reaching maximum strikes. jsaul@google.com siyua@chromium.org payments-autofill-team@google.com Records and emits true when virtual card enrollment is not offered due to the required delay not yet passing since candidate's last strike. jsaul@google.com payments-autofill-team@google.com Metric to measure credit card state when form is submitted, specifically if it had a valid card number and/or expiration date. jsaul@google.com payments-autofill-team@google.com Metric to measure if a submitted card's expiration date matches the same server card's expiration date (unmasked or not). Cards are considered to be the same if they have the same card number (if unmasked) or if they have the same network and last four digits (if masked). battre@chromium.org jsaul@google.com koerber@google.com Metric to measure if a submitted form contains any recognizable value patterns (e.g., Unified Payment Interface Virtual Payment address (UPI VPA)). Reported for every submitted non-empty visible field observed by Autofill. rhalavati@chromium.org chrome-privacy-core@google.com Records acceptance of autofill suggestions in regular and off-the-record modes. battre@chromium.org chrome-autofill-alerts@google.com The index of the accepted Autocomplete suggestion in the popup. Due to crbug.com/966411, the iOS data is incorrect. battre@chromium.org chrome-autofill-alerts@google.com The index of the accepted Autofill suggestion in the popup. Due to crbug.com/966411, the iOS data is incorrect. {AutofillSuggestionAcceptedIndexSuggestionType} The experiment has been launched in 08/2022. schwering@chromium.org chrome-autofill-alerts@google.com Records whether a click was ignored (because it came too early after the popup was shown) or accepted. An accepted click was either normally accepted or followed an ignored click. Every click falls into one of the three categories. Recorded on each click on an Autofill popup suggestion. rhalavati@chromium.org chrome-privacy-core@google.com Records showing of autofill suggestions in regular and off-the-record modes. pkotwicz@chromium.org chrome-autofill-alerts@google.com Recorded when a "Manage..." suggestion is selected from autofill popup. Records the type of the "Manage..." suggestion (ex "Manage Credit Cards"). schwering@chromium.org kenjitoyama@chromium.org battre@chromium.org chrome-autofill-alerts@google.com Number of milliseconds passed between the start and end of {AutofillTimedFunction}. mlerman@google.com tchudakov@google.com vykochko@google.com chrome-autofill-team@google.com Records whether a user has still used autofill after dismissing the payments bottom sheet. There is a fallback to still allow the user to autofill the form after dismissing the bottom sheet, that is to use the keyboard accessory suggestion. This metric is recorded when submitting the form: true - if there is at least one autofilled field in the submitted form and the payments bottom sheet was shown and dismissed by user, false - otherwise. The metrics is recorded only if the payments bottom sheet was displayed for the form submitted. mlerman@google.com tchudakov@google.com vykochko@google.com chrome-autofill-team@google.com For the Payments bottom sheet (Touch To Fill for credit cards), tracks whether or not the user has edited at least one of the autofilled fields before submitting the form. The metric is recorded on form submission. mlerman@google.com tchudakov@google.com vykochko@google.com chrome-autofill-team@google.com The number of credit cards shown in the Touch To Fill bottom sheet. Recorded when showing the bottom sheet. mlerman@google.com tchudakov@google.com vykochko@google.com chrome-autofill-team@google.com Records the outcome with which the bottom sheet was closed: credit card selected, virtual card selected, go to payment settings, scan new credit card or dismissed with no action. The metric is recorded right after user has done the action: the credit card selection or some other option (which always leads to the bottom sheet being closed) or swiped the sheet to close it. See the TouchToFillCreditCardMediator.java for details. Note that "Go to payment settings" click is also considered as the outcome, although it doesn't close the Touch To Fill. So in this case there will be a double count for one bottom sheet showing. This histogram contains a bug of not accounting all users' manual bottom sheet dismissal. It should be removed after M114 is rolled out. mlerman@google.com tchudakov@google.com vykochko@google.com chrome-autofill-team@google.com Records the outcome with which the bottom sheet was closed: credit card selected, virtual card selected, go to payment settings, scan new credit card or dismissed with no action. The metric is recorded right after user has done the action: the credit card selection or some other option (which always leads to the bottom sheet being closed) or swiped the sheet to close it. See the TouchToFillCreditCardMediator.java for details. Note that "Go to payment settings" click is also considered as the outcome, although it doesn't close the Touch To Fill. So in this case there will be a double count for one bottom sheet showing. This fixes the bug introduced in Autofill.TouchToFill.CreditCard.Outcome and counts all user bottom sheet dismissals. The old histogram should be removed after M114 is rolled out. mlerman@google.com tchudakov@google.com vykochko@google.com chrome-autofill-team@google.com For the Payments bottom sheet (Touch To Fill for credit cards), logs at submission time if the filling experience was perfect or not. In a perfect filling experience, all non-empty fields have been autofilled without subsequent corrections. The metric is logged on form submission. mlerman@google.com tchudakov@google.com vykochko@google.com chrome-autofill-team@google.com The index of the selected credit card in the Touch To Fill bottom sheet. Recorded when user selects a credit card from the list. mlerman@google.com tchudakov@google.com vykochko@google.com chrome-autofill-team@google.com Records the outcome of the attempt to trigger Touch To Fill for credit cards. It is recorded only when the touch to fill feature is enabled and the form is parsed as a credit card form by autofill. koerber@google.com chrome-autofill-team@google.com The visible page language (best guess of the original or the translated language, if translation was used) upon form submission. This is a sparse histogram where the integer value represents the language code as described by the ISO 639 standard. jsaul@google.com siyua@chromium.org Duration of the interaction with the UnmaskPrompt since it was shown until it was closed. This prompt is triggered when a user selects a masked card in an autofill dropdown. {AutofillUnmaskPromptCloseReasonEvents} Deprecated in M109. Subsumed by Autofill.UnmaskPrompt.{CardType}.Events. jsaul@google.com siyua@chromium.org Events tracking the usage of the unmasking prompt. This prompt is triggered when a user selects a masked card in a autofill dropdown. jsaul@google.com siyua@chromium.org Duration of the GetRealPan API call. This API call is triggered by the unmasking prompt when the user types information to verify their ownership of the card being fetched. siyua@chromium.org payments-autofill-team@google.com Duration of the GetRealPan API call. This API call is triggered by the unmasking prompt when the user types information to verify their ownership of the card being fetched. Broken down by the type of the card being fetched and the result. jsaul@google.com siyua@chromium.org Tracks the result of the GetRealPan API call. This API call is triggered by the unmasking prompt when the user types information to verify their ownership of the card being fetched. jsaul@google.com siyua@chromium.org payments-autofill-team@google.com Tracks the result of the GetRealPan API call. This API call is triggered by the unmasking prompt when the user types information to verify their ownership of the card being fetched. Broken down by type of the card being fetched. jsaul@google.com siyua@chromium.org Time the user waited before abandoning an unmasking operation. In such a scenario, the user is cancelling a pending unmasking operation (possibly because it is taking too long). The time measured here corresponds to the time between the user clicking the "Verify" button and then clicking "Cancel". jsaul@google.com siyua@chromium.org Duration between the user clicking the Verify button within the unmasking prompt until we get a response back from the server. This prompt is triggered when a user selects a masked card in an autofill dropdown. jsaul@google.com siyua@chromium.org Duration between the user clicking the Verify button within the unmasking prompt until we get a response back from the server. This prompt is triggered when a user selects a masked card in an autofill dropdown. Broken down by the type of the card being fetched and the result. vinnypersky@google.com jsaul@google.com siyua@chromium.org payments-autofill-team@google.com Events tracking the usage of the unmasking prompt, recorded for {CardType}. This prompt is triggered when a user selects a masked card in a autofill dropdown. battre@chromium.org chrome-autofill-alerts@google.com The delay of a network request for an upload due to exponential backoff. battre@chromium.org chrome-autofill-alerts@google.com The number of bytes that were sent in an upload that subsequently failed. This is to help determine if there are certain upload sizes which are prone to failure. battre@chromium.org chrome-autofill-alerts@google.com The http response code or net error code returned on an upload. battre@chromium.org chrome-autofill-alerts@google.com The duration of a network request for an upload. jsaul@google.com payments-autofill-team@google.com Measures if a card for which upload was accepted is already stored as a local card on the device or if it has not yet been seen. battre@chromium.org chrome-autofill-alerts@google.com Whether or not an upload was sent after having been triggered by a form submission or proxy-form-submission. {AutofillUploadEvents} jsaul@google.com payments-autofill-team@google.com Measures if a card for which upload was offered is already stored as a local on the device or if it has not yet been seen. siyua@chromium.org jsaul@google.com payments-autofill-team@google.com Records the number of times that the cache for unmasked server cards has been accessed for a given card. For example, if the cache is being accessed and it has already been accessed for the card twice before, then "3" is recorded. siyua@chromium.org jsaul@google.com payments-autofill-team@google.com Records the number of times that the cache for virtual cards has been accessed for a given card. For example, if the cache is being accessed and it has already been accessed for the card twice before, then "3" is recorded. battre@chromium.org chrome-autofill-alerts@google.com Measures the frequency of various events in the Autofill user interaction flow. By comparing frequencies, we can compute several interesting "user happiness" metrics. {AutofillFormType} siyua@chromium.org payments-autofill-team@google.com Emits true whenever a virtual card Enroll request is sent. It is broken down by the source of the request (i.e., Upstream, Downstream, settings page). siyua@chromium.org payments-autofill-team@google.com Emitted whenever a virtual card Enroll response is received. It is broken down by the source of the request (i.e., Upstream, Downstream, settings page) and logged based on whether the request suceeded. siyua@chromium.org payments-autofill-team@google.com Emits true whenever a virtual card GetDetailsForEnrollment request is sent. It is broken down by the source of the request (i.e., Upstream, Downstream, settings page). siyua@chromium.org payments-autofill-team@google.com Records the latency for the GetDetailsForEnrollment roundtrip call. The timer starts when a GetDetailsForEnrollment request is sent. It is recorded (the timer stops) when a GetDetailsForEnrollment response is received. siyua@chromium.org payments-autofill-team@google.com Emits whenever a virtual card GetDetailsForEnrollment response is received. It is broken down by the source of the request (i.e., Upstream, Downstream, settings page) and logged based on whether the request suceeded. siyua@chromium.org payments-autofill-team@google.com The number of times that virtual card metadata is propagated via Chrome Sync. It is logged based on whether the metadata is for an existing card or a new card. siyua@chromium.org payments-autofill-team@google.com Emits true whenever a virtual card Unenroll request is sent. It is broken down by the source of the request (i.e., Upstream, Downstream, settings page). siyua@chromium.org payments-autofill-team@google.com Emitted whenever a virtual card Unenroll response is received. It is broken down by the source of the request (i.e., Upstream, Downstream, settings page) and logged based on whether the request suceeded. vishwasuppoor@chromium.org siashah@chromium.org payments-autofill-team@google.com Emits true when a user accepts {Dialog} in the mobile virtual card edit page. Emits false if the user declines. vishwasuppoor@chromium.org siashah@chromium.org payments-autofill-team@google.com Records which link is clicked whenever a user clicks on links in {Dialog} in the mobile virtual card edit page. The links are the education text link, Google legal message link, and issuer legal message link. alexandertekle@google.com payments-autofill-team@google.com This metric emits true if the card art image is available for use in the virtual card enroll bubble for the {EnrollmentSource} and false if it is not available. Recorded when bubble is shown. alexandertekle@google.com payments-autofill-team@google.com This metric emits true when a user clicks on virtual card enrollment link from flows that start from the {EnrollmentSource}. vinnypersky@google.com alexandertekle@google.com siyua@chromium.org payments-autofill-team@google.com Logs the latency between Save Card Bubble accepted and the timestamp for when the Virtual Card Enroll Bubble is shown. This metric is logged right before the Virtual Card Enroll Bubble is shown, but if web contents are unavailable it will be logged before waiting for web contents to become available. vinnypersky@google.com alexandertekle@google.com siyua@chromium.org payments-autofill-team@google.com This metric is recorded every time the virtual card enrollment bubble would have been offered but is not offered due to the maximum number of strikes being reached. It logs the source for the flow where the bubble would have been shown, if the strike limit did not block it (for example, upstream i.e. the save card flow). alexandertekle@google.com siyua@chromium.org payments-autofill-team@google.com Records the reason for closing the virtual card enroll bubble for flows that start from the {EnrollmentSource}. ShowType ({ShowType}) indicates whether the bubble is a first time show or a reshow triggered by the user. A subcategory indicating ({PreviousStrikes}) is also logged. Recorded when the bubble is closed. alexandertekle@google.com siyua@chromium.org payments-autofill-team@google.com Records the reason for starting the virtual card enroll bubble for flows that start from {EnrollmentSource}. Recorded when the bubble is shown. Records false the first time the bubble is shown, true for subsequent bubble shows. alexandertekle@google.com payments-autofill-team@google.com Logged when a strike is registered in the virtual card enrollment strike database because a user rejects the bubble, or when strikes are cleared because the user accepted enrollment. siyua@chromium.org jsaul@google.com payments-autofill-team@google.com Records which field in the virtual card manual fallback bubble was selected by the user and had its contents copied to the clipboard. Recorded on every click of a field in the bubble. siyua@chromium.org jsaul@google.com payments-autofill-team@google.com Records the reason for closing the virtual card manual fallback bubble. Recorded when the bubble is closed. siyua@chromium.org jsaul@google.com payments-autofill-team@google.com This metric is recorded whenever the virtual card manual fallback bubble is shown, after the user has just unmasked and autofilled a virtual card. It records whether the bubble has just appeared for the first time (false) or if it is being reshown due to user actions (true). battre@chromium.org chrome-autofill-team@google.com Logs the impact of the AutofillVoteForSelectOptionValues experiment. Metrics are only recorded for submitted forms (not for blur votes) to prevent double counting. battre@chromium.org chrome-autofill-alerts@google.com Tracks how the different wallet addresses are converted to local autofill profiles. yigu@chromium.org battre@chromium.org web-identity-eng@google.com Time elapsed between the user's first interaction with a form and the form's submission, for form with autocomplete="one-time-code". An interaction requires changing a form control's value manually or via autofill. The interaction can happen on a different form than the one which is submitted. This is recorded once per form submission. yigu@chromium.org battre@chromium.org web-identity-eng@google.com Time elapsed between form load and form submission, for forms with autocomplete="one-time-code". This is recorded once per form submission. yigu@chromium.org battre@chromium.org web-identity-eng@google.com Records whether a frame has ever used autocomplete="one-time-code" during its lifecycle. i.e. it's only recorded once per frame. In addition, we only record it if the frame has parsed forms. yigu@chromium.org battre@chromium.org web-identity-eng@google.com Records whether a frame collects phone number based on the field classification. It records once per frame only if it has parsed forms. Note that the field types may not be calculated if there are less than 3 fields in the form unless an autocomplete attribute is provided. e.g. if the form has only a single field regarding phone number without specifiying autocomplete="phone", a sample with "false" will be reported. yigu@chromium.org web-identity-eng@google.com Records whether a document collected phone number, and/or used WebOTP, and/or used OneTimeCode (OTC) during its lifecycle. i.e. it's recorded in the browser process when a document is destroyed. battre@chromium.org src/android_webview/OWNERS Records the state of an autofill session. battre@chromium.org src/android_webview/OWNERS Records whether Autofill with Google is the current Android autofill service. It is recorded on AutofillProvider initialization. Only recorded in Android P and beyond. battre@chromium.org src/android_webview/OWNERS Whether the autofill is created by activity context. battre@chromium.org src/android_webview/OWNERS Whether the autofill service is enabled in Android platform. jkeitel@google.com battre@chromium.org Records the events that ocurred during an Autofill session on Android. The emitted value is a bitmask whose bits have the following meaning: Bit #1 is true iff WebView received a callback from the Android Autofill framework. Bit #2 is true iff suggestions were displayed. Bit #3 is true iff the user changed the value of any field. Bit #4 is true iff the user changed the value of an autofilled field. Bit #5 is true iff a form field changed visibility during the Autofill session. Bit #6 is true iff a form submission was detected. pkotwicz@chromium.org chrome-autofill-alerts@google.com Counts whether users filled the form, given that they have already interacted with the form. This metric is recorded on Android WebView, only for forms that users interacted with. It is recorded only once per form, meaning that it does not matter if the user fills the form multiple times. If a form changes dynamically, then Autofill treats the different versions of the form as different forms. {AutofillFormType} pkotwicz@chromium.org chrome-autofill-alerts@google.com Counts whether users interacted with a form of a certain type. Focusing a field is sufficient to consider a form as being interacted with. The user does not need to type anything. Note that some forms may get focused on page load. This metric is recorded once per form observed by Autofill on Android WebView, but only for forms that Autofill classifies to be of the type indicated by the histogram name. If a form changes dynamically, Autofill interprets the forms before and after the change as two different forms and records two values. If a form did not have features that classify it as a form of a certain type (e.g. an address form or payment form), then nothing is recorded. {AutofillFormType} pkotwicz@chromium.org chrome-autofill-alerts@google.com Counts whether a form was parsed/interpreted to be of the type indicated in the histogram name. This metric is recorded once for each form observed by Autofill on Android WebView. If a form changes dynamically, then Autofill treats the different versions of the form as different forms. {AutofillFormType} pkotwicz@chromium.org chrome-autofill-alerts@google.com Counts whether users submitted a form that was filled via autofill. This metric is recorded once for each form observed by Autofill on Android WebView but only for forms that the user filled via Autofill. {AutofillFormType} pkotwicz@chromium.org chrome-autofill-alerts@google.com Counts for submitted forms whether the user filled any fields via Autofill. If the user reverts the filling, the form is still counted as filled. This metric is different from Autofill.WebView.KeyMetrics.FillingAcceptance in the sense that the latter is only recorded if the user has actually seen a prompt to fill data. {AutofillFormType} pkotwicz@chromium.org chrome-autofill-alerts@google.com Counts for submitted and autofilled forms on Android WebView whether users edited at least one filled value before submitting the form. {AutofillFormType} pkotwicz@chromium.org chrome-autofill-alerts@google.com Counts for filled (by Autofill) forms whether users submitted those forms. This is only recorded for forms that the user filled via Autofill on Android WebView. It does not matter if the user reverted the filling afterwards. This is recorded once Autofill stops tracking the form (e.g. due to a navigation or due to removal from the DOM). {AutofillFormType} pkotwicz@chromium.org chrome-autofill-alerts@google.com Counts for not filled (by Autofill) forms whether users submitted those forms. This is only recorded for Android WebView. It is only recorded for forms for which the user typed anything but did not fill anything. It does not matter if the user reverted what they typed. This is recorded once Autofill stops tracking the form (e.g. due to a navigation or due to removal from the DOM). {AutofillFormType} alexmitra@chromium.org src/android_webview/OWNERS Records the Autofill provider on the device if it matches a fixed list of package names or unknown otherwise. This is recorded once for a given AwContents. It is recorded on AutofillProvider initialization. Only recorded in Android P and beyond. battre@chromium.org src/android_webview/OWNERS Records whether Autofill with Google has suggestions and if the user selects any suggestion. It is recorded when the form is submitted. Only recorded in Android P and beyond. battre@chromium.org src/android_webview/OWNERS Records whether the server prediction of any field isn't NO_SERVER_DATA. This histogram is recorded when the server prediction is available for the current form, and only if AndroidAutofillQueryServerFieldTypes feature is enabled. battre@chromium.org src/android_webview/OWNERS Records whether and when the server prediction response of current autofill session is available even if query failed or there is no server data. This histogram is recorded when the prediction becomes available or the new session starts, and only if AndroidAutofillQueryServerFieldTypes feature is enabled. battre@chromium.org src/android_webview/OWNERS Records the source of form submission. battre@chromium.org src/android_webview/OWNERS The time taken to display suggestion. battre@chromium.org src/android_webview/OWNERS Whether the user changed autofilled field. jihadghanna@google.com chrome-autofill-alerts@google.com Records at submission time for each autofilled {FieldType} field where precedence was granted to heuristics over {AutocompleteStatus} Autocomplete whether the user edited the autofilled value or not.