joshuatan@google.com junhuihe@google.com tushartushar@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the latency for invoking the payment app since a payment link was detected. {Result} indicates whether the initial launch of the payment app was successful or not. [Frequency] Logged once per A2A payflow. [Trigger] The histogram is logged when the payment app is invoked. joshuatan@google.com junhuihe@google.com tushartushar@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the latency for invoking the payment app since a payment link was detected. {Result} indicates whether the initial launch of the payment app was successful or not. The payment is supported by {Scheme}. [Frequency] Logged once per A2A payflow. [Trigger] The histogram is logged when the payment app is invoked. joshuatan@google.com junhuihe@google.com tushartushar@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the reasons why the A2A payflow was exited. [Trigger] A2A payflow was exited early. [Frequency] Logged at most once per A2A payflow. joshuatan@google.com junhuihe@google.com tushartushar@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the reasons why the A2A payflow was exited. The payment is supported by {Scheme}. [Trigger] A2A payflow was exited early. [Frequency] Logged at most once per A2A payflow. joshuatan@google.com junhuihe@google.com tushartushar@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the overall latency for the A2A transaction. The latency is measured from when the payment app is opened to when Chrome receives a callback after the transaction. The result of the transaction is {A2ATransactionResult}. [Frequency] Logged at most once per A2A payflow. [Trigger] The histogram is logged when the result of the A2A transaction is received. joshuatan@google.com junhuihe@google.com tushartushar@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the overall latency for the A2A transaction. The latency is measured from when the payment app is opened to when Chrome receives a callback after the transaction. The result of the transaction is {A2ATransactionResult}. The payment is supported by {Scheme}. [Frequency] Logged at most once per A2A payflow. [Trigger] The histogram is logged when the result of the A2A transaction is received. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com On a webpage that is eligible for eWallet transactions on Chrome, this histogram logs user actions on the eWallet FOP selector. FOP selector UI will be different according to the {AvailableEwalletsConfiguration}, which might affect user behaviors. {AvailableEwalletsConfiguration} infers the available eWallet accounts for this profile. [Frequency] Logged once per eWallet payflow. eWallet payflow is triggered at most once per page load. [Trigger] User interacts with the eWallet FOP selector. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the latency for seeing the FOP selector since a payment link was detected. [Frequency] Logged once per payflow. Ewallet payflow is triggered at most once per page load. [Trigger] The histogram is logged when the eWallet FOP selector is shown. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the latency for seeing the FOP selector since a payment link was detected. The payment is supported by {Scheme}. [Frequency] Logged once per payflow. Ewallet payflow is triggered at most once per page load. [Trigger] The histogram is logged when the eWallet FOP selector is shown. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com Latency for the call to fetch the client token. The client token is fetched from the platform specific payment library in preparation for facilitating the payment using Google Pay. Logged when an eWallet payflow is triggered. {Result} is the token fetch result. The payment is supported by {Scheme}. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com Logs true when a request is sent to the Initiate Payment backend endpoint. It should never log a false case. The payment is supported by {Scheme}. [Frequency] Logged at most once per eWallet flow. [Trigger] User selects an eWallet payment from the list of options shown in the eWallet UI. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com Logs the latency for the InitiatePayment backend endpoint and breaks it down by the result. Logged when an eWallet payflow is triggered, at most once per page-load. The result is {Result}. The payment is supported by {Scheme}. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com Logs true when a request is sent to to payments platform (client) which faciliates the payment. It should never log a false case. The payment is supported by {Scheme}. [Frequency] Logged at most once per eWallet flow. [Trigger] User selects an eWallet instrument from the list of options shown in the eWallet UI and the backend returns the instruction to trigger the purchase action flow. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com Logs the latency for the call made to payments platform (client) which faciliates the payment and breaks it down by the result of the call. The result is {Result}. The payment is supported by {Scheme}. Whether the chosen payment FOP is bound to the device: {IsDeviceBound}. [Frequency] Logged at most once per eWallet payflow. [Trigger] User selects a payment instrument from the list of options shown in the eWallet UI. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com Latency for the call to check whether the FacilitatedPayments API client is available or not. Logged when an eWallet link is found on the page, at most once per page-load. The result is {Result}. The payment is supported by {Scheme}. The API client's availability is checked to determine whether Chrome can offer to facilitate the payment using Google Pay. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com Latency for the call to fetch risk data which was a {Result}. The payment is supported by {Scheme}. Logged then the eWallet payflow is triggered. The risk data gives device's risk fingerprint which is used to decide whether or not to process the transaction. [Frequency] Logged at most once per page load. nicluo@google.com siashah@google.com hfizt@google.com payments-autofill-team@google.com Logs the reason why the eWallet New Account Linking onboarding flow was exited early. [Trigger] The onboarding flow terminates early. [Frequency] Logged at most once per onboarding flow. nicluo@google.com siashah@google.com hfizt@google.com payments-autofill-team@google.com Logs the reason why the eWallet New Account Linking onboarding flow was exited early for {Scheme}. [Trigger] The onboarding flow terminates early. [Frequency] Logged at most once per onboarding flow. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the reasons why the payflow was exited. [Trigger] Payflow was exited early. [Frequency] Logged at most once per payflow. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the reasons why the payflow was exited. The payment is supported by {Scheme}. [Trigger] Payflow was exited early. [Frequency] Logged at most once per payflow. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the UI screens being shown to the user. The payment is supported by {Scheme}. [Frequency] Each enum value is logged at most once per payflow. [Trigger] The browser gets signal that a {Scheme} payment link exists on the page, and the user clicks on the UI screens to proceed with payment. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com Logs true when a payment link is detected on a merchant webpage. [Trigger] A payment link on a merchant page has triggered the payment link push payment flow. [Frequency] Logged once per page load. nicluo@google.com siashah@google.com hfizt@google.com payments-autofill-team@google.com Logs true when a payment link is detected on a merchant webpage and the user is eligible for the eWallet new account linking onboarding flow (meaning they have no linked eWallet accounts but have unlinked creation options available). [Trigger] A payment link is detected and the user has no standard linked eWallet accounts but has matching eWallet creation options. [Frequency] Logged once per page load. junhuihe@google.com qihuizhao@google.com payments-autofill-team@google.com Logs true when a payment link is detected on a merchant webpage. The payment is supported by {Scheme}. [Trigger] A payment link on a merchant page has triggered the payment link push payment flow. [Frequency] Logged once per page load. longsheng@google.com siashah@google.com payments-autofill-team@google.com The count for the number of times user accepted the Pix account linking prompt. 'Accepted' is logged when the prompt is accpeted and `Not accepted` is not logged. [Frequency] Logged once per Pix account linking flow. [Trigger] User clicks the Accept button on Pix account linking prompt. longsheng@google.com siashah@google.com payments-autofill-team@google.com The count for the number of times the Pix account linking prompt is shown. 'Shown' is logged when the prompt is shown and `Not shown` is not logged. [Frequency] Logged once per Pix account linking flow. [Trigger] The histogram is logged when the prompt appears after user completes the payment on their bank/payment app and return back to Chrome. siashah@google.com payments-autofill-team@google.com On a webpage that is eligible for Pix payments, this histogram logs the time taken by the user to select a Pix account to pay with after the FOP selector is shown. [Frequency] Logged once per Pix payflow. Pix payflow is triggered at most once per page load. [Trigger] The histogram is logged when the user selects the Pix account to pay with on the FOP selector. siashah@google.com payments-autofill-team@google.com On a webpage that is eligible for Pix transactions on Chrome, this histogram logs user actions on the Pix FOP selector. [Frequency] Logged once per Pix payflow. Pix payflow is triggered at most once per page load. [Trigger] User interacts with the Pix FOP selector. siashah@google.com payments-autofill-team@google.com On a webpage that is eligible for Pix payments, this histogram logs the latency for seeing the FOP selector since a user copies the Pix payment code on the browser. [Frequency] Logged once per Pix payflow. Pix payflow is triggered at most once per page load. [Trigger] The histogram is logged when the Pix FOP selector is shown. longsheng@google.com siashah@google.com payments-autofill-team@google.com Logged when a Pix code is copied to the clipboard within an iframe if the iframe's URL is empty, about:blank, or about:srcdoc. Indicates whether the iframe is same-origin with the main frame. This is useful for diagnosing failures in the allowlist check. longsheng@google.com siashah@google.com payments-autofill-team@google.com A Pix-specific histogram. Emits the type of URL for the iframe when a likely Pix code is copied to the clipboard within an iframe. [Trigger] User copies a likely Pix code to the clipboard in an iframe. [Frequency] Logged at most once per Pix payflow. siashah@google.com payments-autofill-team@google.com Logs the latency for the call made to payments platform (client) which faciliates the payment and breaks it down by the result of the call. The result is {Result}. [Frequency] Logged at most once per Pix payflow. [Trigger] User selects a payment instrument from the list of options shown in the Pix UI and the backend returns the instruction to trigger the purchase action flow in GMSCore. siashah@google.com payments-autofill-team@google.com On a webpage that is eligible for facilitated payments, this histogram logs the reasons why the payflow was exited. [Trigger] Payflow was exited early. [Frequency] Logged at most once per payflow. siashah@google.com payments-autofill-team@google.com A Pix-specific histogram. Emits the result of validating a Pix payment code. [Trigger] User copies a Pix payment code to their clipboard, either manually for via a merchant's copy button. [Frequency] Logged once per Pix payflow. Pix payflow is triggered at most once per page load. dcheng@chromium.org payments-autofill-team@google.com Emits the result of validating a Pix payment code using the Rust Pix QR code parser. [Trigger] User copies a Pix payment code to their clipboard, either manually or via a merchant's copy button. [Frequency] Logged once per Pix payflow. Pix payflow is triggered at most once per page load. siashah@google.com payments-autofill-team@google.com Latency for the Pix payment code validation with {PaymentCodeValidationResult} as result. The validation is done in a sandboxed utility process to safely process strings from the renderer without compromising the browser process. The string would have already been verified to contain the Pix identifier prefix (0014br.gov.bcb.pix). [Frequency] As the Pix payflow is only allowed to be triggered once per page load, this metric similarly can only be logged at most once per page load. [Trigger] The user copies a Pix payment code to their clipboard, either manually for via a merchant's copy button. dcheng@chromium.org payments-autofill-team@google.com Compares the C++ Pix code validation result against the Rust Pix code validation result. The C++ result is {PaymentCodeValidationResult}. The Rust result is translated into the C++ enumeration space for an apples-to-apples comparison. [Trigger] User copies a Pix payment code to their clipboard, either manually or via a merchant's copy button. [Frequency] Logged once per Pix payflow. Pix payflow is triggered at most once per page load. siashah@google.com payments-autofill-team@google.com A Pix-specific histogram. Emits true when a likely Pix code is copied to the clipboard on any merchant webiste. A likely Pix code contains substring "0014br.gov.bcb.pix", but this is logged before the merchant allowlist check, which could thereafter fail and not trigger a PIX FOP selector UI. [Trigger] User copies a likely Pix code to the clipboard. [Frequency] Logged once per Pix payflow. Pix payflow is triggered at most once per page load. longsheng@google.com siashah@google.com payments-autofill-team@google.com A Pix-specific histogram. Emits true when a likely Pix code is copied to the clipboard within an iframe. A likely Pix code contains substring "0014br.gov.bcb.pix", but this is logged before the iframe allowlist check, which could thereafter fail and not trigger a Pix FOP selector UI. [Trigger] User copies a likely Pix code to the clipboard. [Frequency] Logged once per Pix payflow. Pix payflow is triggered at most once per page load. longsheng@google.com siashah@google.com payments-autofill-team@google.com Logs the result of the Pix purchase action and breaks it down by the type of the frame that initiated the transaction. This log represents {Result} for {FrameType}. [Frequency] Logged at most once per Pix payflow. Pix payflow is triggered at most once per page load. [Trigger] User copies the Pix code, goes through the steps to complete the transaction, and at the end Chrome receives the result of the transaction. Note: A `Succeeded` result doesn't indicate that the transaction was successful. It only means that the payments backend was contacted, and a response was received. siashah@google.com payments-autofill-team@google.com Logs the overall latency for the Pix transaction as experienced by the user and breaks it down by the result of the transaction. The timer starts when the user copies the Pix code, and ends when Chrome receives the result of the transaction (which also coincides with all Chrome and platform UIs closing). The result is {Result}. [Frequency] Logged at most once per Pix payflow. Pix payflow is triggered at most once per page load. [Trigger] User copies the Pix code, goes through the steps to complete the transaction, and at the end Chrome receives the result of the transaction. Note: A `Succeeded` result doesn't indicate that the transaction was successful. It only means that the payments backend was contacted, and a response was received. joshuatan@google.com junhuihe@google.com tushartushar@google.com payments-autofill-team@google.com Logs true when the toggle for A2A is enabled and false otherwise. Does not log if the toggle is not updated. [Trigger] User updates the toggle for A2A from the "Pay with non-card payment methods" settings page. [Frequency] Logged once per toggle update. joshuatan@google.com junhuihe@google.com tushartushar@google.com payments-autofill-team@google.com Logs true when the toggle for Ewallet is enabled and false otherwise. Does not log if the toggle is not updated. [Trigger] User updates the toggle for Ewallet from the "Pay with non-card payment methods" settings page. [Frequency] Logged once per toggle update. joshuatan@google.com junhuihe@google.com tushartushar@google.com payments-autofill-team@google.com Emits true when the "Pay with non-card payment methods" settings page is shown. Never emits false. [Trigger] User selects the Pay with non-card payment methods preference from the Payment Methods settings page. [Frequency] Logged once for every time the page is shown. siashah@google.com payments-autofill-team@google.com Emits true when the FacilitatedPayments settings page is shown. Does not emit any other value. [Trigger] User selects the Pay with a facilitated payment type preference from the Payment Methods settings page. [Frequency] Logged once for every time the page is shown. siashah@google.com payments-autofill-team@google.com Logs true when the toggle for {FacilitatedPaymentsType} is enabled and false otherwise. Does not log if the toggle is not updated. [Trigger] User updates the toggle for {FacilitatedPaymentsType} from the facilitated payments settings page. [Frequency] Logged once per toggle update. longsheng@google.com siashah@google.com hfizt@google.com nicluo@google.com payments-autofill-team@google.com This histogram logs the reasons as to why the {FacilitatedPaymentsType} account linking flow was exited. The flow is said to be completed if Chrome successfully opens Wallet's {FacilitatedPaymentsType} account linking page. [Trigger] {FacilitatedPaymentsType} account linking flow was exited early. [Frequency] Logged at most once per payflow. longsheng@google.com siashah@google.com hfizt@google.com nicluo@google.com payments-autofill-team@google.com Latency for the call to fetch the client token for the {FacilitatedPaymentsType} account linking flow. The client token is fetched from the platform-specific payment library. {Result} is the token fetch result. [Frequency] Logged once per {FacilitatedPaymentsType} account linking flow. [Trigger] The GMSCore API returns the token or fails. longsheng@google.com siashah@google.com hfizt@google.com nicluo@google.com payments-autofill-team@google.com Records the amount of time that it takes to receive a response from the server endpoint that checks the {FacilitatedPaymentsType} account linking eligibility (GetDetailsForCreatePaymentInstrument). [Frequency] Logged once per {FacilitatedPaymentsType} account linking flow. [Trigger] The histogram is logged when the server endpoint returns a response. longsheng@google.com siashah@google.com hfizt@google.com nicluo@google.com payments-autofill-team@google.com Records the eligibility response received from the server endpoint that checks the {FacilitatedPaymentsType} account linking eligibility (GetDetailsForCreatePaymentInstrument). [Frequency] Logged once per {FacilitatedPaymentsType} account linking flow. [Trigger] The histogram is logged when the server endpoint returns a response. hfizt@google.com payments-autofill-team@google.com On a webpage that is eligible for {FacilitatedPaymentsType} transactions on Chrome, this histogram logs when the account linking prompt failed to show to the user. [Frequency] Logged once per payflow. [Trigger] The account linking prompt failed to show. hfizt@google.com payments-autofill-team@google.com On a webpage that is eligible for {FacilitatedPaymentsType} transactions on Chrome, this histogram logs the duration that the account linking prompt was shown to the user before they interacted with it. [Frequency] Logged once per payflow. [Trigger] The user takes an action on the prompt (accepts or dismisses it). hfizt@google.com payments-autofill-team@google.com On a webpage that is eligible for {FacilitatedPaymentsType} transactions on Chrome, this histogram logs the duration that the account linking prompt was shown to the user before they interacted with it, specifically when the user {UserAction}. [Frequency] Logged once per payflow. [Trigger] The user interacts with the account linking prompt. hfizt@google.com payments-autofill-team@google.com On a webpage that is eligible for {FacilitatedPaymentsType} transactions on Chrome, this histogram logs events related to the account linking prompt. [Frequency] Logged once per event. [Trigger] The prompt is shown or the user interacts with the account linking prompt. longsheng@google.com siashah@google.com payments-autofill-team@google.com Logs whether the {FacilitatedPaymentsType} account linking process was successful or not. [Frequency] Logged exactly once per account linking flow. [Trigger] Chrome receives the outcome callback after attempting the account linking flow via GMSCore. siashah@google.com payments-autofill-team@google.com Latency for the call to fetch the client token. The client token is fetched from the platform specific payment library in preparation for facilitating the payment using Google Pay. {Result} is the token fetch result. [Frequency] Logged at most once per {FacilitatedPaymentsType} payflow. [Trigger] Page is loaded and the main frame contains a valid payment code for {FacilitatedPaymentsType}. siashah@google.com payments-autofill-team@google.com Logs true when a request is sent to the Initiate Payment backend endpoint. It should never log a false case. [Frequency] Logged at most once per {FacilitatedPaymentsType} flow. [Trigger] User selects a payment instrument from the list of options shown in the {FacilitatedPaymentsType} UI. siashah@google.com payments-autofill-team@google.com Logs the latency for the InitiatePayment backend endpoint and breaks it down by the result. The result is {Result}. [Frequency] Logged at most once per {FacilitatedPaymentsType} payflow. [Trigger] User selects a payment instrument from the list of options shown in the {FacilitatedPaymentsType} UI. siashah@google.com payments-autofill-team@google.com Logs true when a request is sent to to payments platform (client) which faciliates the payment. It should never log a false case. [Frequency] Logged at most once per {FacilitatedPaymentsType} flow. [Trigger] User selects a payment instrument from the list of options shown in the {FacilitatedPaymentsType} UI and the backend returns the instruction to trigger the purchase action flow in GMSCore. siashah@google.com payments-autofill-team@google.com Latency for the call to check whether the FacilitatedPayments API client is available or not. The result is {Result}. The API client's availability is checked to determine whether Chrome can offer to facilitate the payment using Google Pay. [Frequency] Logged at most once per {FacilitatedPaymentsType} payflow. [Trigger] Page is loaded and the main frame contains a valid payment code for {FacilitatedPaymentsType}. siashah@google.com payments-autofill-team@google.com Latency for the call to fetch risk data which was a {Result}. The risk data gives device's risk fingerprint which is used to decide whether or not to process the transaction. [Frequency] Logged at most once per page load. [Trigger] The browser gets signal that a {FacilitatedPaymentsType} code exists on the page. siashah@google.com payments-autofill-team@google.com On a webpage that is eligible for facilitated payments, this histogram logs the UI screens being shown to the user. [Frequency] Each enum value is logged at most once per {FacilitatedPaymentsType} payflow. [Trigger] The browser gets signal that a {FacilitatedPaymentsType} code exists on the page, and the user clicks on the UI screens to proceed with payment. junhuihe@google.com qihuizhao@google.com tushartushar@google.com payments-autofill-team@google.com On a webpage that is eligible for payment link push payment on Chrome, this histogram logs user actions when a FOP selector has {PaymentLinkFopSelectorTypes}. [Frequency] Logged once per payment link payflow. It is recorded when a fop is selected for payment, "Turn off payment prompt" link clicked, or "Manage payment methods" option selected. [Trigger] User interacts with the non card payment methods FOP selector. junhuihe@google.com qihuizhao@google.com tushartushar@google.com payments-autofill-team@google.com On a webpage that is eligible for payment link push payment on Chrome, this histogram logs user actions when a FOP selector has {PaymentLinkFopSelectorTypes}. The payment is supported by {Scheme}. [Frequency] Logged once per payment link payflow. It is recorded when a fop is selected for payment, "Turn off payment prompt" link clicked, or "Manage payment methods" option selected. [Trigger] User interacts with the non card payment methods FOP selector. junhuihe@google.com qihuizhao@google.com tushartushar@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the latency for seeing the {PaymentLinkFopSelectorTypes} since a payment link was detected. [Frequency] Logged once per payflow. Payment link payflow is triggered at most once per page load. [Trigger] The histogram is logged when the payment link FOP selector is shown. junhuihe@google.com qihuizhao@google.com tushartushar@google.com payments-autofill-team@google.com On a webpage with a valid payment link, this histogram logs the latency for seeing the {PaymentLinkFopSelectorTypes} FOP selector since a payment link was detected. The payment is supported by {Scheme}. [Frequency] Logged once per payflow. Payment link payflow is triggered at most once per page load. [Trigger] The histogram is logged when the payment link FOP selector is shown.