commit | 1d071ff5b69115b7110207ee812f801e1e40aa0b | [log] [tgz] |
---|---|---|
author | Fernando Ramirez <ferny@google.com> | Fri Jun 27 19:43:02 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 27 19:43:02 2025 |
tree | 5200677a1dfc3a04e38108e876481b5e1d56c4ce | |
parent | b31e1fc140bdc4c18f60b371009358a993e7cc9d [diff] |
[Card Benefits][Metrics] Add selected without benefit 2+ card metric For the card benefits project, we are going to begin tracking form event metrics when users have 2 or more server cards on Payments Autofill, with at least 1 card eligible to show benefits. We also plan to migrate the existing benefit form event enums to a new, benefit-specific form event enum class. This CL adds `kSuggestionWithoutBenefitSelectedWithMultipleServerCards` to a new benefit-specific form event enum class. This CL also logs this enum to the `Autofill.FormEvents.CreditCard.Benefits` histogram. The new form event enum will allow us to track lift in selection rate: (kSuggestionWithBenefitSelectedWithMultipleServerCards + kSuggestionWithoutBenefitSelectedWithMultipleServerCards) / kSuggestionWithBenefitShownWithMultipleServerCards go/card-benefit-2-or-more-server-card-metrics Bug: 417323667, 417228483 Change-Id: I1df15eb48750f19f7ff16c6b0d9b4a62bfc1f350 Validate-Test-Flakiness: skip Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6659138 Reviewed-by: Olivia Saul <osaul@google.com> Reviewed-by: Stephen McGruer <smcgruer@chromium.org> Commit-Queue: Fernando Ramirez <ferny@google.com> Reviewed-by: Yishui Liu <yishuil@google.com> Reviewed-by: Vinny Persky <vinnypersky@google.com> Cr-Commit-Position: refs/heads/main@{#1480021}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.