triploblastic@google.com bsazonov@google.com chrome-signin-team@google.com Records the failure events with {Error} when fetching access tokens. The events are bucketed by OAuthConsumerId. Recorded on every access token fetch request failure. triploblastic@google.com bsazonov@google.com chrome-signin-team@google.com Records the success events when fetching access tokens. The events are bucketed by OAuthConsumerId. Recorded on every access token fetch request success. ddac@chromium.org ljjlee@google.com chrome-signin-team@google.com Records the duration of fetching the can_sign_in_to_chrome capability for age mismatch checks. Recorded when the fetch completes (either succeeds or times out). ddac@chromium.org ljjlee@google.com chrome-signin-team@google.com Records the result of the capability fetch in AgeMismatchCapabilitiesFetcher (False, True, or Timeout). Recorded once on the completion of each fetch attempt. ddac@google.com chrome-signin-team@google.com Records the duration it takes to build the External Privacy Context for an identity. Recorded when the asynchronous EPC build operation finishes. (iOS only). ddac@google.com chrome-signin-team@google.com Records the error code when the External Privacy Context build fails. Recorded when the asynchronous EPC build operation finishes with an error. (iOS only). ddac@google.com chrome-signin-team@google.com Records whether the External Privacy Context build was successful or not. Recorded when the asynchronous EPC build operation finishes. (iOS only). tju@google.com chrome-kids-eng@google.com chrome-signin-team@google.com Measures time that the users will most likely spend actively waiting for the Account Capabilities to load, when they were not available. Contrary to Signin.AccountCapabilities.UserVisibleLatency, this metric is more closely tracking the actual latency of the fetch of AccountCapabilities, by the means of impact on the user interface that had to present a loading spinner of similar view. Recorded when an extended account info is updated and the account info has Capabilities during displaying of the sync consent screen. Pre-stable M132 and M133 Desktop binaries have missing data. fernandex@google.com msarda@chromium.org triploblastic@chromium.org chrome-signin-team@google.com This histogram records the time it takes to fetch account capabilities from the system library {Caller}. fernandex@google.com msarda@chromium.org triploblastic@chromium.org chrome-signin-team@google.com This histogram records the outcome of the account capabilities fetch operation. This is recorded only on Android and iOS where Chrome fetches the account capabilities from the system library. tju@google.com chrome-kids-eng@google.com chrome-signin-team@google.com Indicates whether the Account Capabilities were immediately available when requested. Together with Signin.AccountCapabilities.UserVisibleLatency, they are tracking the time and the type of fetch (synchronous or asynchronous) from the user's perspective. Recorded when the following conditions hold: a sync consent screen is displayed, the user is signed in and not syncing, and the primary account info has Capabilities. Pre-stable M132 and M133 Desktop binaries have missing data. tju@google.com chrome-kids-eng@google.com chrome-signin-team@google.com Measures time that the users will most likely spend actively waiting for the Account Capabilities to load. This metric is not tracking the actual latency of the fetch of AccountCapabilities, but only the time when those capabilities are required but not available yet. Example use case of this metric is to track time needed to wait for the Account Capabilities before presenting the Signin consent screen. See Signin.AccountCapabilities.ImmediatelyAvailable to analyse what portion of data in this metric was recorded as immediately available (0ms). See Signin.AccountCapabilities.FetchLatency to analyse time spent by users that for whom the UI was blocked until the Capabilities were ready. Recorded in two situations. 1. When an extended account info is updated and the account info has Capabilities while the sync consent screen is displayed. 2. When the following conditions hold: a sync consent screen is displayed, the user is signed in and not syncing, and the primary account info has Capabilities. Pre-stable M132 and M133 Desktop binaries have missing data. alexilin@chromium.org msarda@chromium.org chrome-signin-team@google.com This histogram records the fetch duration every time Chrome {Result} account capabilities from network. This is recorded for {Priority}. This is recorded only on Desktop platforms where Chrome implements its own account capabilities fetcher. alexilin@chromium.org msarda@chromium.org chrome-signin-team@google.com This histogram records the outcome of the account capabilities fetch operation, for {Priority}. This is recorded only on Desktop platforms where Chrome implements its own account capabilities fetcher. bsazonov@chromium.org chrome-signin-team@google.com This histogram records the action taken by user after receiving the header from Gaia in the web sign-in flow. Currently only recorded on mobile. bsazonov@chromium.org chrome-signin-team@google.com Records the action taken by user after receiving the header from Gaia in the web sign-in flow. This histogram is another version of |Signin.AccountConsistencyPromoAction|, where the original one logs the promo events directly, and this histogram creates a variant for every promo event, and logs its access points instead. triploblastic@chromium.org chrome-signin-team@google.com The time it takes to fetch the account information (except avatar) for one account in AccountFetcherService. This is recorded when user info fetch succeeds. pmeuleman@google.com chrome-signin-team@google.com Logs the stable integer ID assigned to a Google account when it is first allocated for UMA metrics tracking. This assigns stable IDs from 0 to 99, and value 100 represents the cap/overflow bucket. rsult@google.com droger@chromium.org chrome-signin-team@google.com This histogram records whether the fetched account and the stored account in preferences have matching account Ids. Recorded whenever a fetched account is retreived from the server. rsult@google.com droger@chromium.org chrome-signin-team@google.com This histogram records whether the {AccountType} account is known in the preferences along with the validity of the refresh token. The value is recorded on profile load when loading the account information. rsult@google.com droger@chromium.org chrome-signin-team@google.com This histogram records the state of the account that is stored in the preferences; whether it is fully or partially known. Recorded whenever a fetched account is retrieved succesfully from the server. msarda@chromium.org treib@chromium.org chrome-signin-team@google.com Records, for each account in the IdentityManager at profile startup, the "type" of account, i.e. whether it's a consumer or enterprise/EDU account. If the check doesn't finish before shutdown, nothing may be recorded. See also "Signin.AccountManagementTypesSummary" for a combined view of all existing accounts. msarda@chromium.org treib@chromium.org chrome-signin-team@google.com Records the numbers of consumer and enterprise/EDU accounts in the IdentityManager at profile startup. Accounts for which the type check failed or timed out are not counted. If the check for any account doesn't finish before shutdown, nothing may be recorded. See also "Signin.AccountManagementType" for the more detailed type of each individual account. droger@chromium.org rsult@google.com chrome-signin-team@google.com Records the number of accounts removed from account-keyed signin preferences. Recorded when accounts are removed from preferences (e.g. clearing cookies or removing signed out accounts from the web), and the user is {SigninState} Chrome at the browser level. rsult@google.com chrome-signin-team@google.com Records the number of non-periodic full fetch triggers that resulted in at least one fetch request, logged and reset once every 24 hours (when a periodic refresh is triggered). rsult@google.com chrome-signin-team@google.com Records the percentage of signed-in accounts that required a network fetch relative to the total number of signed-in accounts during a fetch trigger. Recorded for triggers where at least one account required fetching. rsult@google.com chrome-signin-team@google.com Records when a single account preview preference request (e.g. from UI) is denied because the service is currently rate-limited due to a previous HTTP 429 error. rsult@google.com chrome-signin-team@google.com This records causes that did not result in any actual network fetches because the accounts were the ones already used for the last preference computation. rsult@google.com chrome-signin-team@google.com Records the trigger cause of a fetch cycle that was denied and not performed because the service is currently rate-limited due to a previous HTTP 429 error. rsult@google.com chrome-signin-team@google.com Records the initial trigger cause of a fetch cycle that did not result in any actual network fetches because the data for all accounts was already fully cached. rsult@google.com chrome-signin-team@google.com Records the trigger cause for a sync preview data fetch cycles. Recorded for {State} fetches. rsult@google.com chrome-signin-team@google.com Measures the duration of fetching sync preview data (including token fetching and network requests) for a signed-in account, split by {Result} fetches. Recorded when the fetch finishes. rsult@google.com chrome-signin-team@google.com Records whether a sync preview data fetch attempt for a signed-in account encountered an HTTP 429 (Too Many Requests) response from either endpoint (statistics or entities previews). Recorded whenever a network fetch completes. rsult@google.com chrome-signin-team@google.com Records the progress and outcome of fetching sync preview data (statistics and entities previews) for a signed-in account. Recorded at various steps: when the fetch is requested, when statistics or entities previews complete, and when the overall fetch finishes. jood@google.com treib@chromium.org chrome-signin-team@google.com Records the account profile mapping state on startup for the primary account in each profile. iOS only. jlebel@chromium.org chrome-signin-team@google.com Records the state of the account reconcilor when GAIA returns a specific response. The data in the "Inactive" bucket might be incorrect prior to M111. msarda@chromium.org sdefresne@chromium.org Number of accounts loaded from preferences by the AccountTracker. Invalid accounts are not counted. This is recorded on each profile load. msarda@chromium.org sdefresne@chromium.org This histogram records the AccountTracker account ID migration status from email to GAIA ID after the data is loaded from disk. It is more general than OAuth2Login.AccountRevoked.MigrationState that only record the event in case of errors and only on Android. This histogram will be used to check whether the migration has completed for all active installs on a given platform or not (and whether the code can be removed). This is recorded on each profile load. msarda@chromium.org chrome-signin-team@google.com Indicates whether the account was seeded when the account info needs to be refreshed. This histogram will be used to decide whether the account needs to be seeded during while refreshing the account info. msarda@chromium.org sinhak@chromium.org chrome-signin-team@google.com Indicates if the account being seeded by AccountTracker has an empty account id. This is in general an error as the account with an empty id cannot be tracked. This histogram will be used to decide the severity of AccountTracker receiving malformed account ids during the seeding process. jlebel@chromium.org chrome-signin-team@chromium.org Records the sign-in by regular Gmail account or managed account. Recorded when the user signs in (iOS only). triploblastic@chromium.org chrome-signin-team@google.com This histogram records states in the add account process launched from Chrome on Android. jlebel@chromium.org chrome-signin-mobile-team@google.com This histogram records the time to load the hosted domain. Recorded right after an account was added by the user action when {Status}. Only logged on iOS. jlebel@chromium.org chrome-signin-mobile-team@google.com This histogram records the time to load IsSubjectToEnterprisePolicies account capability. Recorded right after an account was added by the user action when {Status}. Only logged on iOS. jlebel@google.com msarda@google.com chrome-signin-team@google.com Logs the result of adding an account to the device. It is logged as soon as the add account to device operation finishes. The flow to add account to device is explicitly triggered in Chrome by the user in the following cases: a) a signed out user attempts to sign in to Chrome; b) a Chrome signed in user adds a secondary account. Note: This histogram is only logged for account that are added to the device from Chrome. If the users adds the account from another app, then this histogram is not logged. Only logged on iOS. jlebel@google.com msarda@google.com chrome-signin-team@google.com Logs the duration of the operation of adding an account to the device when the operation {Result}. It is logged as soon as the add account to device operation finishes. The flow to add account to device is explicitly triggered in Chrome by the user in the following cases: a) a signed out user attempts to sign in to Chrome; b) a Chrome signed in user adds a secondary account. Note: This histogram is only logged for account that are added to the device from Chrome. If the users adds the account from another app, then this histogram is not logged. Only logged on iOS. ddac@chromium.org ljjlee@google.com chrome-signin-team@google.com Records the user choice in the Age Mismatch Sign-Out dialog (Use another account, Use without an account). Logged when the user taps one of the buttons. ddac@chromium.org ljjlee@google.com chrome-signin-team@google.com Records the mode of the Age Mismatch Sign-Out dialog. "Standard" mode is used when the check is triggered outside of a sign-in flow (e.g. on app foreground). "Signin Flow" mode is used when the check is part of a sign-in operation. Logged when the dialog is presented. ddac@chromium.org ljjlee@google.com chrome-signin-team@google.com Records whether the 'Stay signed out' button is shown or hidden in the Age Mismatch prompt because the user is already signed in to a primary account. Logged when the prompt is displayed. ddac@chromium.org ljjlee@google.com chrome-signin-team@google.com Records the total time duration from the first age-mismatch sign-out until the user successfully signs in with the can_sign_in_to_chrome capability confirmed as true. The timestamp is stored in Local State (app-level), so the duration is measured across all profiles. The timestamp is not updated on subsequent consecutive age-mismatch sign-outs, representing the total continuous time spent without a valid/eligible account. Logged on iOS when the user successfully signs in with the can_sign_in_to_chrome capability true. shadmehr@google.com chrome-signin-mobile-team@google.com Indicates whether the user had accepted account management when attempting to sign in to a managed account on Android, recorded before the policy registration request is dispatched. mthiesse@chromium.org chrome-signin-team@google.com Records an enum at various points throughout the FRE signin flow. Useful to track at what point users drop off. twellington@chromium.org clhager@google.com Records an event when the user starts account reauthentication and the result of such reauthentication. bsazonov@chromium.org chrome-signin-mobile-team@google.com Number of Android accounts on device when entering the First Run Experience sign-in screen. bsazonov@chromium.org chrome-signin-team@google.com The time it takes to retrieve Gaia ids for all accounts from GoogleAuthUtil. bsazonov@chromium.org chrome-signin-mobile-team@google.com The time it takes to retrieve the list of accounts from the system. {AndroidGetAccountsTypes} triploblastic@chromium.org chrome-signin-team@google.com The number of Android accounts present on the device. Recorded on startup. alexilin@chromium.org msarda@chromium.org chrome-signin-team@google.com Records whether the API key matches the value passed via the experiment feature. Recorded once on startup. Note: This histogram is meaningful only when feature OverrideAPIKey is enabled. It should thus only be used from the Finch tab of the UMA dashboard. msarda@chromium.org droger@chromium.org Log the type of GAIA authentication error that occur whenever the error state changes. anthie@google.com rsult@google.com chrome-signin-team-desktop@google.com Records the count of the {AvatarPillPromoType} was shown when the user has intereacted with it. Recorded when that interaction was made. rsult@google.com chrome-signin-team@google.com Records the time between when a promo is shown on the avatar pill and the user interacts with it (clicks on it). If the user doesn't click the avatar pill, the histogram should not be recorded. rsult@google.com chrome-signin-team@google.com Records the promo type shown on the Avatar pill. Recorded when the promo is shown. amelies@google.com chrome-signin-team@google.com Records that sync was turned on while the user had account storage for bookmarks enabled. The record happens when the user opts in to sync. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records how long the generation of assertion for the cookie rotation request in a bound session has taken. Recorded every time a server-challenge is required to rotate bound cookies. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records the result of the assertion generation for the cookie rotation request in a bound session. Recorded at the attempt to sign a given server-challenge in order to rotate bound cookies. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records the result (network error or an HTTP response code) of a cookie rotation request triggered by the bound session credentials feature. Recorded every time a cookie rotation request is performed, only if the request {ChallengeType} challenge response. Cookie rotation is triggered if there is a bound session on startup, bound cookies soon to expire/expired and/or requests to the bound site are blocked on bound cookies. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records the network error occured during a cookie rotation request triggered by the bound session credentials feature. Recorded every time a cookie rotation request completes with a connection error. Cookie rotation is triggered if there is a bound session on startup, bound cookies soon to expire/expired and/or requests to the bound site are blocked on bound cookies. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records how many failed cookie rotation attempts were made during a cookie rotation endpoint outage for a bound session within the same user session (reset on startup). Server 5xx errors are considered to be an outage after a number of successive failures. {Interval}. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records how long a cookie rotation endpoint outage has taken for a bound session within the same user session (reset on startup). Server 5xx errors are considered to be an outage after a number of successive failures. Recorded when an outage is fixed (cookie rotation success, bound cookie becoming fresh) or session shutdown, overriden/terminated while an outage is ongoing. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records the result of the cookie rotation request triggered by the bound session credentials feature. {SessionOrigin} {Trigger} Cookie rotation is triggered if there is a bound session on startup, bound cookies soon to expire/expired and/or requests to the bound site are blocked on bound cookies. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records how long the cookie rotation flow has taken. {Trigger} Cookie rotation is triggered if there is a bound session on startup, bound cookies soon to expire/expired and/or requests to the bound site are blocked on bound cookies. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records whether a request was deferred due to a missing bound cookie. Recorded every time a request covered by a bound session completes with {Result}. "Covered by a bound session" means that a request will be deferred if it's missing a bound cookie. {Type} alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com In a bound session, requests are throttled when required bound cookies are stale and cookie refresh hasn't completed. This histogram records what triggered resuming a throttled request. Recorded for every throttled request that eventually completed {Result}. If a request was throttled by multiple bound sessions, this histogram will record the most "important" value determined by the `GetResumeBlockedRequestsTriggerPriority()` function. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records for how long a request was delayed due to a missing bound cookie. Recorded every time a request was deferred by the bound session credentials throttle, right before the request is resumed or canceled. {Type} ernn@google.com alexilin@chromium.org chrome-signin-team@google.com Recorded every time OAuthMultilogin response contains new bound session(s) to register but the binding key is missing. This should never happen given that the server responds with bound session(s) data only if the client proved the possession of the binding key. ernn@google.com alexilin@chromium.org chrome-signin-team@google.com Records the number of invalid bound session params in successful OAuthMultilogin response. Recorded every time successful OAuthMultilogin response contains new bound session(s) to register. ernn@google.com alexilin@chromium.org chrome-signin-team@google.com Records an error (or lack of any) that occured during parsing the device bound sessions data from the OAuthMultilogin API response. Recorded upon receiving a successful response from OAuthMultilogin API only if the cookie parsing completed successfully and the response contained extra information about device bound cookies. ernn@google.com alexilin@chromium.org chrome-signin-team@google.com Records the number of bound sessions registered by OAuthMultilogin. Recorded after cookies from a successful OAuthMultilogin response are set. Only recorded for Chrome instances that support OAuthMultilogin cookies binding. ernn@google.com alexilin@chromium.org chrome-signin-team@google.com Records the number of unknown domains in the device bound sessions data from the OAuthMultilogin API response. Recorded upon receiving a successful response from OAuthMultilogin API only if the cookie parsing and the device bound sessions parsing completed successfully. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com In a bound session, requests are throttled when required bound cookies are stale and cookie refresh hasn't completed. This histogram records what triggered resuming throttled requests. Recorded every time a batch of throttled requests are resumed. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records the number of bound sessions after initializing them from storage on Chrome startup. Recorded only when the device bound session credentials feature is enabled. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records how long the generation of a registration token for the bound session registration has taken. Recorded every time Chrome attempts to register a bound session after an invitation from the server via an HTTP header. This will not be recorded if Chrome couldn't parse the server invitation or just decided to ignore it. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records the result of generating a registration token for a bound session registration. Recorded every time Chrome attempts to register a bound session after an invitation from the server via an HTTP header. This will not be recorded if Chrome couldn't parse the server invitation or just decided to ignore it. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records the result of the bound session registration request. Recorded every time Chrome attempts to register a bound session after an invitation from the server via an HTTP header. This will not be recorded if Chrome couldn't parse the server invitation or just decided to ignore it. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records how long the bound session registration flow has taken. Recorded every time Chrome attempts to register a bound session after an invitation from the server via an HTTP header. This will not be recorded if Chrome couldn't parse the server invitation or just decided to ignore it. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records the result of an HTTP request (network error or an HTTP response code) that Chrome sends to report about the bound session termination. Chrome sends this requests immediately after terminating a bound session. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records the trigger for a bound session termination on the Chrome side (e.g. Clear cookie). Recorded immediately after the session is terminated. {SessionOrigin} alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records errors encountered while reading device bound sessions from disk at Chrome startup. Recorded once per bound session stored on disk. Not recorded for off-the-record profiles since they don't store bound session data on disk. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records errors encountered while saving device bound sessions to disk. Recorded once per bound session whenever it's saved to disk. This mainly happens when Chrome registers a new bound session but it also may happen during data migrations. Not recorded for off-the-record profiles since they don't store bound session data on disk. alexilin@chromium.org msalama@chromium.org chrome-signin-team@google.com Records how many successive batches of throttled network requests has timed out without the cookie being fresh in between. Recorded when cookies become fresh or on session termination/shutdown if any requests has hit the timeout. samarchehade@google.com chrome-signin-team@google.com When CCT is launched by AGA, records whether there is a mismatch between the account signed in to Chrome and the account signed in to the app that launched Chrome. This can happen if the user is signed in to Chrome but not the 1P app, or vice-versa, or if the user is signed in to both apps but with different accounts. samarchehade@google.com chrome-signin-team@google.com When CCT is launched from an eligible 1P app and there is a mismatch between the account signed in to Chrome and the account signed in to the app that launched Chrome, a mismatch notice might be displayed. However, this notice might be suppressed for a number of reasons. Records when the CCT account mismatch notice is suppressed and why. mmrashad@google.com src/components/sync/OWNERS Records the state of the EstimateNewSignInUsersWithFinchAvailablePopulation feature flag (True if enabled, False if disabled). Recorded exactly once per device-level user during their first sign-in (profile initialization), when the primary account is established for the first time. This tracks operating-system level user accounts, not secondary Google Accounts added via Settings. ChromeOS only. droger@chromium.org chrome-signin-team@google.com Records the user choice on the Chrome signout confrmation prompt, for the version of the dialog that is shown when {Variant}. ahijazi@chromium.org alexilin@chromium.org chrome-signin-team@google.com Records the outcome of evaluating cookie binding upgrade preconditions on the first account reconcilor run on startup. Recorded exactly once per profile load. ahijazi@chromium.org alexilin@chromium.org chrome-signin-team@google.com Records the device bound session creation result triggered by OAuthMultilogin response to a cookie binding upgrade request. Recorded upon completion. ahijazi@chromium.org alexilin@chromium.org chrome-signin-team@google.com Tracks the total duration of the OAuthMultilogin network request and DBSC session registration for cookie upgrade operations. Recorded upon completion. ahijazi@chromium.org alexilin@chromium.org chrome-signin-team@google.com Records whether the first startup reconciliation run had to be deferred because DBSC sessions were not yet fetched from the network process. Recorded only when preconditions for the cookie binding upgrade are met. ahijazi@chromium.org alexilin@chromium.org chrome-signin-team@google.com Tracks the latency of querying the network process for existing DBSC sessions on startup for cookie binding upgrades. Recorded upon successfully receiving the list of DBSC sessions from the network process, once per profile load. droger@chromium.org skym@chromium.org The relation between the account signed into chrome, and the account(s) in the cookie jar. This metric is never recorded when not signed into chrome. The version 1 of this histogram was recorded when the user was syncing ; the version 2 is recorded for all signed in users (including non-syncing). {AccountInvestigationReportingType} msarda@chromium.org droger@chromium.org chrome-signin-team@google.com The number of signed in accounts in the cookie jar for users that have a (possibly unconsented) primary account. Reported at most every 24 hours (using a persistent timer). Reporting is split based on the type of the primary account. {UnconsentedPrimaryAccountType} droger@chromium.org skym@chromium.org The number of signed in accounts in the cookie jar. {AccountInvestigationReportingType} droger@chromium.org skym@chromium.org The number of signed out accounts in the cookie jar. {AccountInvestigationReportingType} droger@chromium.org skym@chromium.org The amount of time since the cookie jar last changed. {AccountInvestigationReportingType} droger@chromium.org skym@chromium.org The total number of accounts in the cookie jar. {AccountInvestigationReportingType} lbarczynski@google.com myuu@google.com chrome-signin-mobile-team@google.com Records the total number of Google accounts present on the device at the moment the cross-device sign-in flow starts. Recorded for {ExternalEntryPoint}. lbarczynski@google.com myuu@google.com chrome-signin-mobile-team@google.com Records the initial state of the device and accounts after successfully parsing the cross-device sign-in deep link, but before the actual flow starts. Recorded for {ExternalEntryPoint}. lbarczynski@google.com myuu@google.com chrome-signin-mobile-team@google.com Records the raw external entry point ID detected from the cross-device sign-in URL (e.g., from a QR code scan). It's recorded only if the full URL is valid and was parsed successfully. rsult@google.com chrome-signin-desktop@google.com Records the shown count of the cross-device sign-in promo when it was dismissed by the user. Recorded for {CrossDeviceSigninPromoEntryPoint}. rsult@google.com chrome-signin-desktop@google.com Records that the cross-device sign-in QR Code bubble was opened, categorized by the entry point it was opened from. rsult@google.com chrome-signin-desktop@google.com Records the decision (allow to show or block reason) for showing the cross-device sign-in promo. Recorded for {CrossDeviceSigninPromoEntryPoint}. rsult@google.com chrome-signin-desktop@google.com Records the new shown count of the cross-device sign-in promo after it is shown. Recorded for {CrossDeviceSigninPromoEntryPoint}. ahijazi@chromium.org alexilin@chromium.org chrome-signin-team@google.com Records the size of the delayed network call queue when the effective connection type is {EffectiveConnectionType}. This is used to understand how often network calls are delayed despite having a valid network connection. This metric is emitted every 30 minutes. ernn@google.com alexilin@chromium.org chrome-signin-team@google.com This histogram records result of the attempt to create device bound sessions with the server-provided session(s) data from OAuthMultilogin. Only recorded for Chrome instances that support DBSC standard and OAuthMultilogin cookies binding. {PartitionSuffix} ernn@google.com alexilin@chromium.org chrome-signin-team@google.com This histogram records errors returned by the network process while creating device bound sessions with the server-provided session(s) data from OAuthMultilogin. It is recorded for every single session. A batch operation result is recorded in `Signin.DeviceBoundSessions.OAuthMultilogin.CreateSessionsResult`. Only recorded for Chrome instances that support DBSC standard and OAuthMultilogin cookies binding. {PartitionSuffix} msalama@chromium.org chrome-signin-team@google.com Records whether Gaia sends primary_is_connected=true in the linked accounts metadata when the profile has no primary account (unsigned profile). Emitted whenever primary_is_connected=true is processed in a DICE signin response. droger@chromium.org msarda@chromium.org Recorded when a Dice signin response is received and indicates whether the authorization code was present or not. ahijazi@chromium.org alexilin@chromium.org chrome-signin-team@google.com Records whether the AccountInfo is Present or Missing when processing a Dice "ENABLE_SYNC" header. Missing AccountInfo can happen during OAuth outages where the previous signin header didn't contain an authorization code. msalama@chromium.org chrome-signin-team@google.com Records the parsing status of the X-Chrome-ID-Consistency-Linked-Accounts-Meta header during a DICE web sign-in request. Emitted once per sign-in if the header is present, or if the response contains multiple accounts (even if the header is missing). ankushkush@google.com droger@chromium.org Records whether a user was force migrated out of the DICe state. This is recorded once per profile load for all users. droger@chromium.org msarda@chromium.org Records Dice responses (signin and signout). alexilin@chromium.org ahijazi@chromium.org chrome-signin-team@google.com Outcome of the token binding in Dice signin. Recorded upon a successful token fetch during Dice signin. Not recorded if the token fetch failed. droger@chromium.org msarda@chromium.org Outcome of the token fetch in Dice signin. ydago@chromium.org pastarmovj@chromium.org Warning: this histogram was expired from 2025-07-01 to 2026-04-15; data may be missing. Whether the user chose to create a new work profile after a signin while profile separation is enforced by policy. This is recorded after the user accepts or refuses to create a new profile when shown the enterprise profile confirmation dialog and enterprise profile separation is enforced by policy. ydago@chromium.org pastarmovj@chromium.org Warning: this histogram was expired from 2025-07-01 to 2026-04-15; data may be missing. Whether the user chose to create a new work profile after a signin while profile separation is not enforced by policy. This is recorded after the user accepts or refuses to create a new profile when shown the enterprise profile confirmation dialog and enterprise profile separation is not enforced by policy. droger@chromium.org chrome-signin-team@google.com Recorded on every startup (towards the end of primary account manager initialization) for users who are signed in but not syncing. It records 3 buckets: signed in users, signed in users with explicit bookmarks enabled, and signed in users with explicit extensions enabled. This helps track the migration of users to the explicit bookmarks and extensions prefs. kelvinjiang@chromium.org rsult@google.com chrome-signin-team@google.com Logged if the user has account extensions when making a choice on the Chrome signout confirmation prompt. Records if the user has chosen to either keep or uninstall all of their account extensions upon signing out, or if the signout was cancelled. amelies@google.com chrome-signin-team@google.com Records whether the user explicitly signed in for the first time or if they have previously done so before in the same profile. Recorded upon signing in through any access point. kelvinjiang@chromium.org rsult@google.com chrome-signin-team@google.com Records whether the user explicitly signed in through the extension install bubble entry point for the first time or if they have previously done so before in the same profile. Recorded upon signing in through the extension install bubble entry point only. alexilin@chromium.org droger@chromium.org chrome-signin-team@google.com Result of the chrome.identity.getAuthToken() extension API call. Recorded right before returning the result to an extension. Desktop only. {GetAuthTokenType} alexilin@chromium.org rsult@google.com chrome-signin-team@google.com Result of the chrome.identity.launchWebAuthFlow() extension API call. Recorded right before returning the result to an extension. Desktop only. ankushkush@google.com droger@chromium.org Records whether the browser instance was available after the timer to show the toast was fired. The toast is shown to confirm the user's migration to explicitly signed-in state, which happens early during the startup. This is recorded for all implicitly signed-in users with account management enabled. Since this is recorded during the migration of implicitly signed-in users to explicitly signed-in state which can happen only once per user lifetime, this histogram is recorded exactly once per user lifetime. ankushkush@google.com droger@chromium.org Records whether the user has account management enabled. This is recorded for all implicitly signed-in users early during the startup. Since this is recorded during the migration of implicitly signed-in users to explicitly signed-in state which can happen only once per user lifetime, this histogram is recorded exactly once per user lifetime. msarda@chromium.org alexilin@chromium.org Records whether the requests started from GaiaAuthFetcher include secure and insecure cookies. This is required to investigate the issue crbug.com/531646858. Only logged on iOS. droger@chromium.org msarda@chromium.org The number of requests initiated by the browser to log the user out from Google web. The Chrome account reconcilor enforces account consistency for Google accounts between the browser and web. In some cases it must force logout the user from Google web and then it sends a request to the Gaia logout endpoint. The expectation is that brower initiated logout is a rare event and should only occur in the following cases: a) it to be triggered when the browser fails to exchange an auth code for refresh tokens after a web sign-in (events which is counted by histogram Signin.DiceTokenFetchResult), b) when all refresh tokens are invalid (e.g when they cannot be loaded from disk). treib@chromium.org chrome-signin-team@google.com Recorded whenever a Gaia page (i.e. https://accounts.google.com/) was visited. The buckets distinguish various well-known pages. Not recorded in Incognito. iOS only. droger@chromium.org msarda@chromium.org Records finished access token requests during Chrome reconcile, both successful or not, and return the GoogleAuthError state NONE is a success, other values are failures. mlbipin@google.com chrome-signin-mobile-team@google.com Records the outcome of fetching the list of accounts from the platform-specific API that happens in the AccountManagerFacade. Android only. mlbipin@google.com chrome-signin-mobile-team@google.com Records whether API that fetches the list of accounts is available for use. Recorded when the availability check completes. Android only. mlbipin@google.com chrome-signin-mobile-team@google.com Tracks the latency of the account list API availability check.Recorded when the availability check completes. Android only. samarchehade@google.com chrome-signin-mobile-team@google.com Android only. The number of backoff retries necessary before fetching user accounts information from Google Play services succeeded. Recorded after every successful accounts fetching. samarchehade@google.com chrome-signin-team@google.com Android only. Whether account fetching succeeded or not. Recorded either after user accounts were successfully retrieved from Google Play or after failing after a maximum number of retries. triploblastic@google.com bsazonov@chromium.com chrome-signin-mobile-team@google.com Records that a signin HaTS survey may have been shown to the user. It means that we got a valid survey config and the user is eligible to be shown a survey. The survey may not get shown in the end due to external restrictions such as survey limit within 24 hours being reached. (Android only). triploblastic@google.com bsazonov@chromium.com chrome-signin-mobile-team@google.com Records that a trigger for signin HaTS survey was registered. This is registered only once per chrome run. (Android only). rsult@google.com droger@chromium.org treib@google.com chrome-signin-team@google.com Records the signin access point at the moment when the user is {ConsentLevel} Chrome, if they're already opted in to history sync. See also `Signin.HistoryOptInState.*`. rsult@google.com droger@chromium.org treib@google.com chrome-signin-team@google.com Records the user's history opt-in state, at the moment when the user is {ConsentLevel} Chrome. For `ConsentLevel::kSync` users, this is true by default, but may be false if the user had previously enabled sync and turned history off. Conversely, for `ConsentLevel::kSignin` users, it's false by default, unless the same user was previously signed in and has opted in then. Note that, depending on the signin entry point and other conditions, the user may be presented with a history opt-in right after this histogram records a "false" sample - for those cases, see `Signin.HistorySyncOptIn.Completed`. See also `Signin.HistoryAlreadyOptedInAccessPoint.*`, which for the "true" samples in this histogram records their signin access point. anthie@google.com chrome-signin-desktop-team@google.com Records the time spent until {SyncStartupEvent}. It is recorded when the sync service reaches a transport state past the initialization or when we exceed a given timeout and the sync service transport has not been updated. myuu@google.com bsazonov@chromium.org jlebel@chromium.org chrome-signin-team@google.com Records that {OptInFlowEvent}, and logs the original access point associated with this event. jlebel@chromium.org jood@google.com treib@chromium.org chrome-signin-team@google.com Records the decision whether to show an identity confirmation snackbar (and the reason for not showing it), whenever the app is foregrounded. iOS only. arthurmilchior@chromium.org chrome-signin-team@google.com Recorded when the identity snackbar is displayed. It records whether the name was available to display. iOS only. rsult@google.com chrome-signin-team@google.com Records the duration between requesting account preview preferences for an intercepted account and receiving the preference response (or reaching the timeout). Recorded before showing the interception bubble. rsult@google.com chrome-signin-team@google.com Records whether requesting account preview preferences for an intercepted account timed out before receiving the preference response. Recorded before showing the interception bubble. rsult@google.com droger@chromium.org Records the reason for dismissing {Type} bubble. This is recorded when a dismiss action is done. It could either be by pressing the Escape key when the bubble is shown or by pressing on the identity pill button. rsult@google.com chrome-signin-team@google.com Records the number of times the user dismisses the Chrome Signin Intercept Bubble before {Action} it. The value is recorded when the user is {Action} the Chrome Signin intercept bubble. No value is recorded when the bubble is dismissed/ignored. rsult@google.com droger@chromium.org Records the number of days that passed since the last time Chrome Signin Bubble was declined. This value is recorded when a reprompt is displayed. The value is not recorded if the Chrome Signin setting is explicitly set by the user. rsult@google.com droger@chromium.org Records the number of reprompts for the Chrome Signin Bubble. This value is recorded when a reprompt is displayed. The first bubble impression is not recorded here. The first reprompt (follow up impression) will first be recorded as 1. rsult@google.com chrome-signin-team@google.com Records the time between the display of the Chrome Signin intercept bubble and the user {Result} response by interacting with the bubble UI. alexilin@chromium.org chrome-signin-desktop-team@google.com Warning: this histogram was expired from 2026-04-12 to 2026-08-26; data may be missing. Records various events that occur during the first run experience after the sign-in interception. anthie@google.com chrome-kids-eng@google.com chrome-signin-team@google.com Records the supervision state of the intercepted user when the sign-in interception bubble is displayed, for different interception types that suport supervised user parametrization. This histograms records values for interceptions that happen when {InterceptType}. droger@chromium.org alexilin@chromium.org Records the outcome of the signin interception heuristic, which runs for each signin interception. rsult@google.com droger@chromium.org Records the outcome of the signin interception bubble. Recorded when the bubble is closed, either after the user did an explicit action through the bubble or when the bubble was closed because it was dismissed or ignored (browser is closed while the bubble was showing). This histogram records values for the Chrome Signin bubble, with the users {State}. alexilin@chromium.org droger@chromium.org Records the outcome of the signin interception bubble. Recorded when the bubble is closed, either after the user did an explicit action through the bubble or when the bubble was closed because it was dismissed or ignored (browser is closed while the bubble was showing). This histogram records values for the Enterprise {Mode}, with the {Status} account being enterprise. alexilin@chromium.org droger@chromium.org Records the outcome of the signin interception bubble. Recorded when the bubble is closed, either after the user did an explicit action through the bubble or when the bubble was closed because it was dismissed or ignored (browser is closed while the bubble was showing). This histogram records values for the {InterceptType}, with the users {SigninState}. droger@chromium.org msarda@chromium.org Reason for invalid Gaia credentials. Recorded when Signin.AuthError records invalid credentials. jlebel@chromium.org chrome-signin-team@google.com Records the access point from where the account menu was opened. Recorded every time the account menu is opened. iOS only. msarda@chromium.org treib@chromium.org chrome-signin-mobile-team@google.com [iOS only] Records the number of {AccountType} accounts on the device (across all profiles) at browser startup. See also "Signin.IOSAccountsOnDeviceManagementTypesSummary". msarda@chromium.org treib@chromium.org chrome-signin-mobile-team@google.com Companion to "Signin.IOSAccountsOnDeviceManagementTypesSummary". Records whether any unknown-type accounts were present at browser startup. msarda@chromium.org treib@chromium.org chrome-signin-mobile-team@google.com [iOS only] Records the numbers of consumer and enterprise/EDU accounts on the device at browser startup{DeviceType}. Accounts for which the type was not known yet are not counted (in practice, these are often managed accounts that Chrome just encountered for the first time). See also "Signin.IOSAccountsOnDeviceManagementTypesHadUnknownTypes" which records whether any unknown-type accounts were present, and "Signin.AccountManagementTypesSummary" which is similar to this histogram but is per-profile. jlebel@chromium.org treib@chromium.org chrome-signin-mobile-team@google.com When switching accounts, records whether the old and/or the new account were managed. Recorded independently of whether the account switch involved a profile switch. jlebel@chromium.org treib@chromium.org chrome-signin-mobile-team@google.com Records the outcome of profile initialzation done by AuthenticationService, which happens whenever a profile is loaded (i.e. on browser startup, plus whenever the user switches accounts/profiles). jlebel@chromium.org treib@chromium.org chrome-signin-mobile-team@google.com Records the reason for switching profiles on iOS, whenever a profile switch is kicked off. jlebel@chromium.org chrome-signin-team@google.com Records the number of identities after iOS device restore. Recorded at cold start when a device restore is detected, and only if the user was signed in before the device backup. jlebel@chromium.org chrome-signin-team@google.com Records the number of identities before iOS device restore. Recorded at cold start when a device restore is detected, and only if the user was signed in before the device backup. jlebel@chromium.org chrome-signin-team@google.com Records errors when creating sentinel files at cold start. Those sentinel files are used to detect a device restore. Histogram only for iOS. jlebel@chromium.org chrome-signin-team@google.com Records if the path for a sentinel file (used to detect iOS restore) is generated successfully. Recorded on cold start. jlebel@chromium.org chrome-signin-team@google.com Records whether the user is signed in or signed out before and after a device restore. Recorded at cold start when a device restore is detected. jlebel@chromium.org msarda@chromium.org chrome-signin-team@google.com Records whether the Gaia cookie is present when a user signed in to Chrome navigates to a Google-owned domain that is eligible for Mirror account consistency. This metrics tracks the user journeys that interact with authentication cookies and that could be disrupted if an external force (e.g. Apple's ITP) were to remove these cookies. This logging is limited to once every hour due to performance constraints. arthurmilchior@chromium.org treib@chromium.org chrome-signin-mobile-team@google.com Records when fetching the hosted domain for an account starts or finishes, while determining which profile to assign the account into. A fetch is started as soon as an account is detected (i.e. independent of Chrome signin state), if the hosted domain isn't locally cached already. Only recorded if kSeparateProfilesForManagedAccounts is enabled. jlebel@chromium.org chrome-signin-team@google.com Records the availability of an identity while the user signs in. Whether it is available for AccountProfileMapper and whether it is available for IdentityManager in the a profile. According to crbug.com/393340481 it is possible for an identity to be available in AccountProfileMapper and not in IdentityManager. This metric can be removed once `kSeparateProfilesForManagedAccounts` is launched and if `AccountProfileMapper` and `IdentityManager` are in sync. This is record only for iOS. jlebel@chromium.org treib@chromium.org chrome-signin-mobile-team@google.com The number of times the user switched accounts in the {TimeRange}. Emitted no more than once every 24 hours, as soon as Chrome detects that more than 24 hours passed from the last recording. Recorded only on iOS. jlebel@chromium.org msarda@chromium.org chrome-signin-team@google.com Count of the number of SSO accounts present on the device. Note that this is different to the number of accounts signed in in Chrome. The count is logged in this histogram each time the application goes to foreground. jlebel@chromium.org chrome-signin-mobile-team@google.com [iOS only] Records the result of retrieving an avatar from the system identity manager cache and preparing it in ResizedAvatarCache (on cache miss). Recorded each time an identity avatar is requested and is not already present in the memory cache. msarda@chromium.org droger@chromium.org Failure reason of ListAccounts call failure during account reconciliation, Chrome OS login, or signin internals queries. msarda@chromium.org droger@chromium.org Logs whether a task to check and trigger list accounts if they are stale is posted when ListAccounts fails. msarda@chromium.org droger@chromium.org Retry reason of failed ListAccounts calls (these calls calls are used to fetch the list of Google accounts present in the Gaia cookies). tju@google.com chrome-kids-eng@google.com Kids Management API fetchers have a retry logic that might trigger multiple individual calls to the Kids Management API one after the other. This metric captures the total time, including all individual latencies tracked in Signin.ListFamilyMembersRequest.Latency. tju@google.com chrome-kids-eng@google.com The final status of the fetch to the Kids Management API, visible to the user. Statuses of intermediate fetches (including final one) are tracked in the Signin.ListFamilyMembersRequest.Status metric. tju@google.com chrome-kids-eng@google.com The number of retries before a decisive status (OK or permanent error). jlebel@chromium.org msarda@chromium.org chrome-signin-team@google.com Counts the number of identities loaded by SSO library using the keychain API. The metric is recorded every time SSO updates the identity list (either on the first run, or when the cache is staled). Identities with and without auth error are counted. See: https://crbug.com/897470. jlebel@chromium.org msarda@chromium.org chrome-signin-team@google.com Tracks the time it takes to load identities by SSO library using the keychain API. The metric is recorded every time SSO updates the identity list (either on the first run, or when the cache is staled). See: https://crbug.com/897470. jlebel@chromium.org msarda@chromium.org chrome-signin-team@google.com Tracks the time it takes to load one identity in average by SSO library using the keychain API. This value is the total time taken by the keychain API to finish, divided by the number of identities returned. The metrics is recorded every time SSO updates the identity list (either on the first run, or when the cache is staled). See: crbug.com/897470. jlebel@chromium.org msarda@chromium.org chrome-signin-team@google.com Counts the number of identities with auth error, loaded by SSO library using the keychain API. The metric is recorded every time SSO updates the identity list (either on the first run, or when the cache is staled). droger@chromium.org msarda@chromium.org Action taken for tokens being loaded from the token database, at Chrome startup. Tokens can be either loaded into Chrome's token service or revoked. msalama@google.com chrome-signin-team@google.com Records whether the device supports Hybrid Transport (BLE) for MagiChrome. Recorded when the Chrome sign-in URL is generated. treib@chromium.org chrome-signin-team@chromium.org Records the Gaia "service type" received in an "X-Chrome-Manage-Accounts" header, indicating an action the user has selected on a Gaia page which is to be handled by Chrome, such as adding another account or managing accounts on the device. Applies only to "Mirror" platforms, i.e. Android, iOS, and ChromeOS. anthie@google.com chrome-signin-desktop-team@google.com Recorded when during a flow that requires the creation of a managed profile via the managed disclaimer service, we detect that another managed profile creation for a different user is in progress. Applies to Desktop platforms. alexilin@chromium.org droger@chromium.org chrome-signin-team@google.com Records the outcome of an attempt to move an account between profiles, specifically regarding whether the account's refresh token and binding key can be transferred. Recorded on every attempt to move an account between profiles, mainly via the sign-in intercept feature. droger@chromium.org msarda@chromium.org Number of accounts in tokens sent to Gaia Multilogin. Recorded when Chrome does a request to /oauth/multilogin. bsazonov@chromium.org droger@chromium.org treib@chromium.org chrome-signin-team@google.com The number of accounts that were active in the {TimeRange}, i.e. that were used as the primary account in any profile. Emitted no more than once every 24 hours, as soon as Chrome detects that more than 24 hours passed from the last recording, and only if at least one of the active accounts was a managed account. See also `Signin.NumberOfActiveAccounts.Last7/28Days` for the number of active accounts independent of managed-ness status. bsazonov@chromium.org droger@chromium.org treib@chromium.org chrome-signin-team@google.com The number of accounts that were active in the {TimeRange}, i.e. that were used as the primary account in any profile. Emitted no more than once every 24 hours, as soon as Chrome detects that more than 24 hours passed from the last recording. bsazonov@chromium.org droger@chromium.org treib@chromium.org chrome-signin-team@google.com The number of managed accounts that were active in the {TimeRange}, i.e. that were used as the primary account in any profile. Emitted no more than once every 24 hours, as soon as Chrome detects that more than 24 hours passed from the last recording. See also `Signin.NumberOfActiveAccounts.Last7/28Days` for the number of active accounts independent of managed-ness status. alexilin@chromium.org droger@chromium.org chrome-signin-team@google.com Result of the OAuth2MintToken API call. Recorded after the response is processed. Desktop only. Warning: this histogram was expired from 2024-05-19 to 2024-09-10; data may be missing. alexilin@chromium.org droger@chromium.org chrome-signin-team@google.com OAuth2 result of the OAuth2MintToken API call based on the server response. Recorded after the response is processed excluding net failure cases. Desktop only. This is recorded together with "Signin.OAuth2MintToken.ApiCallResult" but uses the same result type as "Gaia.ResponseForOAuth2AccessToken". alexilin@chromium.org droger@chromium.org chrome-signin-team@google.com Records an error code (or none) for a single OAuth2MintToken API fetch with {BindingState} refresh token. Recorded for requests with {TokenBindingAssertionValue}, after the response is processed. Desktop only. alexilin@chromium.org droger@chromium.org chrome-signin-team@google.com Records an encryption failure (or lack of any) that occured during OAuth2MintToken API fetch with {BindingState} refresh token. Recorded after the response is processed. Desktop only. msarda@chromium.org droger@chromium.org Reason fetching an OAuth2 Token failed or none in case of success. Available on all OSes. msarda@chromium.org droger@chromium.org Reason fetching an OAuth2 Token is being retried. Available on all OSes. alexilin@chromium.org chrome-signin-team@google.com Records an encryption failure (or lack of any) that occured during OAuthMultilogin API fetch. Recorded once per cookie while the response is being processed. droger@chromium.org msarda@chromium.org chrome-signin-team@google.com Response status received from gaia Multilogin. {PartitionSuffix} This is version 2 of the histogram, which also records network errors. droger@chromium.org msarda@chromium.org Response status received from gaia Multilogin. {PartitionSuffix} treib@chromium.org rsult@google.com droger@chromium.org chrome-signin-team@google.com Recording the count of open tabs, at the moment when the user is {ConsentLevel} Chrome. msarda@chromium.org droger@chromium.org chrome-signin-team@google.com Logs whether the primary account info is properly tracked by the account tracker service. If it is not, then it logs whether the primary account info was restored. msarda@chromium.org droger@chromium.org chrome-signin-team@google.com Logs the state of the main primary account preferences when the primary account manager is loaded. bsazonov@chromium.org msarda@chromium.org chrome-signin-mobile-team@google.com Recorded when request intitator is checked after receiving X-Chrome-Connected header with GAIA_SERVICE_TYPE_INCOGNITO. The recorded bucket represents the result of the check (i.e. whether the received initiator origin is allowed to trigger requests that end up sending X-Chrome-Connected header). mlbipin@google.com chrome-signin-mobile-team@google.com Records which the state of the target account when the mirror header is received. This is recorded when the GAIA_SERVICE_TYPE_ADDSESSION header is received. mlbipin@google.com chrome-signin-mobile-team@google.com Records whether the web signin loading dialog was shown, not shown (because signin finished fast enough), or dismissed by the user. Recorded when the web signin process finishes or the dialog is dismissed. mlbipin@google.com chrome-signin-mobile-team@google.com Records the duration of the wait for WebSignin to complete before it was aborted. Recorded when WebSignin is aborted. mlbipin@google.com chrome-signin-mobile-team@google.com Time taken for cookies to be minted and the user to be redirected to a specified URL. Recorded from when the WebSigninRedirectCoordinator is initialized to when the user either gets redirected or if the user receives an error. mlbipin@google.com chrome-signin-mobile-team@google.com Records the outcome of the wait for WebSignin to complete. Recorded when the WebSignin process either completes or is aborted, along with whether a loading dialog was shown during the wait. myuu@google.com chrome-signin-mobile-team@google.com This histogram records how many times the sign-in promo of the {AccessPoint} has been shown when a {Action} is done on the same promo (Android Only). bsazonov@chromium.org chrome-signin-mobile-team@google.com Recorded when a reauth flow triggered from an explicit reauthentication UI is {Event}. Recorded bucket designates the explicit reauthentication UI in which the reauthentication flow was triggered. Only recorded on iOS. bsazonov@chromium.org chrome-signin-mobile-team@google.com Recorded when a reauth flow triggered within the sign-in flow is {Event}. Recorded bucket designates the sign-in flow in which the reauthentication flow was triggered. Only recorded on iOS. msarda@chromium.org droger@chromium.org Records whether all external connections have been successfully checked (a value of "true") or not ("false") when the reconciler attempts to perform MergeSession. msarda@chromium.org chrome-signin-team@google.com Records whether the accounts in the cookie jar are fresh when StartReconcile is called on the AccountReconcilor. droger@chromium.org msarda@chromium.org Records the execution time of the account reconciler using 100 buckets, up to 3 minutes. {Signin_Reconciler_Duration_UpTo3mins} msarda@chromium.org droger@chromium.org Records the time it took to successfully check all external connections whenever the reconciler performs a reconciliation. msarda@chromium.org droger@chromium.org Records the time it took to check only a portion of external connections whenever the reconciler performs a reconciliation. This means that either a network error occured while checking some sites or the site did not respond before the check timeout. msarda@chromium.org droger@chromium.org Records the operation executed by the reconcilor to reconcile the accounts (or no-op if the accounts are already consistent). droger@chromium.org msarda@chromium.org msalama@chromium.org Records the number of consecutive {RequestType} requests not allowed by the account reconcilor throttler due to back off time required between successive requests with the same paramaters. Recorded on the throttler destruction, a reset upon a new different request or a no operation reconciliation cycle or an allowed request upon a sufficient time to refill. droger@chromium.org msarda@chromium.org msalama@chromium.org chrome-signin-team@google.com Recorded when the account reconcilor tries to change the cookie to match the tokens and performs a {Operation} operation. Records the event which triggered the reconcile. droger@chromium.org msarda@chromium.org Source for refresh token revocation. This is used to track the sources for signing out of Google accounts and is required to validate that the browser is not revoking tokens for large parts of the user population. ahijazi@chromium.org alexilin@chromium.org bsazonov@chromium.org chrome-signin-team@google.com Records the total time elapsed from when the profile's credential loading sequence starts (via LoadCredentialsInternal on the UI thread) to when all refresh tokens are loaded into memory and ready for use. Recorded exactly once per profile startup. For Android, this measures the latency from the native delegate calling LoadCredentialsInternal, through GMS Core account fetching and validation, to when tokens are ready in memory. This includes the Java account manager IPC roundtrip and native account seeding. For Desktop, this measures the latency from the native delegate calling LoadCredentialsInternal, through DB thread query overhead, local SQLite token decryption, and key manager initialization on the UI thread. droger@chromium.org msarda@chromium.org Source for refresh token updated to invalid tokens. The refresh token is updated to an permanently invalid token when the user attempts to sign out of the primary account without turning off sync. This histogram is used to track the sources for invalidating the token of the primary account and is required to validate that the browser is not invalidating the token of the primary account for large parts of the user population. droger@chromium.org msarda@chromium.org Source for refresh token updated to valid tokens. This is used to track the sources for adding Google accounts to the browser. triploblastic@google.com chrome-signin-mobile-team@google.com Records whether mdm notification was suppressed for scope limited errors. Every time chrome tries to get an access token for a set of scopes and gets an error, we will call mdm service to check if it wants to show a notification for this error. If it's a scope limited error we will not call the mdm service. So any notification it would have shown is effectively suppressed. iOS only. msarda@chromium.org chrome-signin-team@google.com This histogram is recorded when the session is ending and only if the web sign-in status is unknown. It records the duration of the session that was spent in an "Unknown" state. This histogram is used to validate that long sessions with "Unknown" cookie sign-in status are short. An "Unknown" sign-in state indicates that the list of accounts in cookie jar haven't been refreshed for the current session yet. During this time, Chrome only has access to a cached, potentially stale list of accounts from disk. This time is measured in milliseconds and the session duration (session start and session end points, including the exclusion of idle time) follows the same definition as the one used for the Session.TotalDuration histogram. msarda@chromium.org droger@chromium.org This histogram records the success of setting each cookie after Multilogin response is received and parsed. rsult@google.com droger@chromium.org Records the value of the setting for automatic Chrome Signin choice. The value is recorded upon Chrome Signin. rsult@google.com chrome-signin-team@google.com This histogram records each modification of the setting value of "Sign in to Chrome when you sign in to other Google services" done by the user through the Settings page. If the setting was shown and not modified, a value for no modification is recorded when the user closes or navigates away from Chrome settings. If the setting is not shown, no values are recorded at all. kbajkiewicz@google.com chrome-signin-desktop-team@google.com This histogram records the count at which the {PromoType} when the user signs in through it. jlebel@chromium.org chrome-signin-mobile-team@google.com Logs the browser type when the Gaia server triggers the manage account dialog. Most likely, this is recorded when the user taps on a manage accounts button in Google web site (like gmail, drive, etc…). Only logged on iOS. arthurmilchior@chromium.org chrome-signin-team@google.com msarda@chromium.org jlebel@chromium.org This histogram is recorded when two sign-in views are being opened at the same time. This indicates the duration between the two sign-in events. arthurmilchior@chromium.org chrome-signin-team@google.com msarda@chromium.org jlebel@chromium.org This histogram is recorded when two sign-in views are being opened at the same time. This indicates the access point which triggered the {View} to be opened. bsazonov@chromium.org dgn@chromium.org msarda@chromium.org chrome-signin-team@google.com chrome-ds@google.com Records that the user signed in to Chrome, and logs the original access point associated with this event. This histogram is of special interest to the chrome-ds@. Do not change its semantics or retire it without talking to them first. {Profile} bsazonov@chromium.org dgn@chromium.org chrome-signin-team@google.com Records that the option to sign in to Chrome was offered to the user{AccountState} and logs the original access point associated with this event. This histogram is still in development and has a limited coverage of the Signin access points for now. bsazonov@chromium.org dgn@chromium.org chrome-signin-team@google.com Records that the user started the flow to sign in to Chrome, and logs the original access point associated with this event. Notes: - For the First Run, we log it once for the whole first run flow, it does not get recorded multiple times if the user steps back in the flow and chooses again to sign in. - More access points were added in M134 in iOS, which should lead to an increase in the number of log, not related to an actual increase in usage. myuu@google.com chrome-signin-mobile-team@google.com Logs the duration of the Android sign-in flow, from when the user triggers {FlowVariant} sign-in until {Event} occurs, recorded when the {Event} occurs. The time spent on the management notice is excluded. Only recorded on Android. bsazonov@chromium.org chrome-signin-team@google.com Logs the original access point of each aborted sign in. Only logged on Android. droger@chromium.org msarda@chromium.org tangltom@chromium.org Tracks the state of a user's signin-allowed preference. This is recorded at every startup. msarda@chromium.org bsazonov@chromium.org droger@chromium.org chrome-signin-team@google.com Logs the original access point of each completed sign in. {SigninAccountStatus} Note: See also more modern metrics such as Signin.SignIn.Completed and Signin.SyncOptIn.Completed that provide similar insights (but exclude reauth). More information about modernization can be found in http://go/chrome-signin-metrics-revamp. bsazonov@chromium.org chrome-signin-mobile-team@google.com This histogram records the signin access point which was used when the signin disabled notification was shown. Recorded on Android only. droger@chromium.org anthie@google.com chrome-signin-team@google.com Recorded when setting set the browser's primary account for non-automatic sign-ins. When the feature `BrowserSigninInSyncHeaderOnGaiaIntegration` is enabled, this also records the place where the browser sign-in would take place, if the feature was disabled. See also the enum `GaiaIntegrationState` description. droger@chromium.org anthie@google.com chrome-signin-team@google.com Records the elapsed time between the handling of the LST token and the handing of the Dice Sync header when the user signs in to Chrome browser. If no Dice Sync header is sent from the Gaia server, then this histogram is not recorded. This histogram is not relevant and not recorded for Web sign-ins, as in this case the Dice Sync header is not sent. Chrome guarantees that the Sync header processing happens after the LST token processing so this elapsed time will be positive. In the unlikely edge case that GAIA sends the Sync header before Chrome can enforce the proper ordering between the LST and the Sync token, this histogram is not recorded and `Signin.SigninManager.UnexpectedSyncHeaderProcessingBeforeLST` will be recorded instead. droger@chromium.org anthie@google.com chrome-signin-team@google.com Recorded when the user signs in to their Google Account through a Chrome sign-in entry point. This is not recorded for Web sign-in as they do not involve the Dice Sync Header. Records a `True` sample when the Dice Sync header arrives after a timeout window since the reception of the LST token or does not arrive at all. Records a `False` sample if the header arrives within a time window from the LST token. Also records `False` in the unlikely edge case that the Sync header arrives before the LST is even requested (and before Chrome can enforce their proper ordering to be first the LST and then the Sync header processing). For the latter edge case see also the histogram `Signin.SigninManager.UnexpectedSyncHeaderProcessingBeforeLST`. This histogram is not recorded if the user closes the sign-in tab before the timeout window is reached. droger@chromium.org anthie@google.com chrome-signin-team@google.com Recorded when the user signs in to their Google Account through a Chrome sign-in entry point. This is not recorded for Web sign-in as they do not involve the Dice Sync Header. A value is recorded when, unexpectedly, the Dice sync header is processed before the LST token: This can only happen if the Sync header is received before the request for the LST happens. If the LST is first requested, then the processing of the LST and the Sync header is coordinated by Chrome so that they happen in the right order (first LST, then Sync header). amelies@google.com chrome-signin-team@google.com Records that the signin interceptor detected the user entering an inconsistent state by signing into the web with an account B while being in sign in pending state with account A. {Profile} rsult@google.com droger@chromium.org chrome-signin-desktop-team@google.com Records that the option to re-authenticate to the Signed in account in Chrome was offered to the user while in Sign-in Pending state and logs the original access point associated with this event. This histogram is still in development and has a limited coverage of the Signin access points for now. rsult@google.com chrome-signin-team@google.com Records the access point of the resolution event from Signin Pending to Signed in. The value is recorded when the user {Status}. rsult@google.com chrome-signin-team@google.com Records the time spent from entering the Signin Pending state to {ResolutionType}. The value is recorded when the resolution method is applied. rsult@google.com chrome-signin-team@google.com Records the resolution method used when in Signin Pending, either Sign in (reauth) or sign out of Chrome. The value is recorded when the resolution is applied. {Profile} amelies@google.com chrome-signin-team@google.com Records the access point associated with the sign in promo. Recorded when the promo is {UserAction} by the user. msarda@chromium.org bsazonov@chromium.org droger@chromium.org chrome-signin-team@google.com Logs the original access point that displayed the signin or reauth Gaia page, before the page is displayed. {SigninAccountStatus} Note: See also more modern metrics such as Signin.SignIn.Started and Signin.SyncOptIn.Started that provide similar insights (but exclude reauth). More information about modernization can be found in http://go/chrome-signin-metrics-revamp. bsazonov@chromium.org dgn@chromium.org msarda@chromium.org chrome-signin-team@google.com chrome-ds@google.com Records that the user signed out of Chrome, and logs the original access point associated with this event. Note that turning off Sync almost always signs the user out, in which case both this histogram and Signin.SyncTurnOff.Completed are recorded. This histogram is of special interest to the chrome-ds@. Do not change its semantics or retire it without talking to them first. {Profile} esalma@google.com chrome-signin-team@google.com Logs whether a managed user using an unmanaged browser chooses to proceed with signout or not, after a warning dialog about data clearing is shown. Note: iOS only. msarda@chromium.org droger@chromium.org Track how a profile gets signed out. rsult@google.com pmeuleman@google.com Recorded when the sync preview is fetched for a smart account selection. Data Point: {BooleanDataPoint} {ProfileIndex} {AccountIndex} rsult@google.com pmeuleman@google.com Recorded when the sync preview is fetched for a smart account selection. The recorded range and number of buckets vary by data type to match the expected scale of that specific data type. Data Point: {CountDataPoint} {ProfileIndex} {AccountIndex} jlebel@chromium.org chrome-signin-team@google.com Tracks the error code by -[SSOService identitiesWithError:]. See: https://crbug.com/981082. jlebel@chromium.org chrome-signin-team@google.com Tracks the SSO identity cache state before calling -[GCRSSOService identitiesWithError:] or -[GCRSSOService identitiesForDisplay]. See: https://crbug.com/897470. {SigninSSOIdentityListRequestCacheRequestState} jlebel@chromium.org chrome-signin-team@google.com Tracks the time it takes to call `GetSSOIdentities()`. See: https://crbug.com/897470. {SigninSSOIdentityListRequestDurationCacheState} jlebel@chromium.org chrome-signin-team@google.com Tracks the time between -[GCRSSOService fetchIdentitiesWithCallback:] and the callback is invoked. See: https://crbug.com/897470. jlebel@chromium.org chrome-signin-team@google.com Counts the number of cookies returned by -[WKHTTPCookieStore getAllCookies:]. This histogram is to help to understand how many callbacks from |getAllCookies:| can be missing. And if the number of cookies is related in that iOS bug. See: crbug.com/880981. jlebel@chromium.org chrome-signin-team@google.com Tracks the time it takes for -[WKHTTPCookieStore getAllCookies:] to finish and call its callback. Note that nothing is logged is -[WKHTTPCookieStore getAllCookies:] fails to calls its callback. This histogram is to help to understand how many callbacks from |getAllCookies:| can be missing, related to a bug from iOS. And if the number of cookies is related in that iOS bug. See: crbug.com/880981. jlebel@chromium.org chrome-signin-team@google.com Counts the number of times -[WKHTTPCookieStore getAllCookies:] is called and the number of times it calls its callback. This histogram is to help to understand how many callbacks from |getAllCookies:| can be missing, related to a bug from iOS. And if the number of cookies is related in that iOS bug. See: crbug.com/880981. tju@google.com chrome-kids-team@google.com chrome-signin-team@google.com Records the appearance of the button set on sync or history sync opt in screens. Recorded when the buttons are displayed to the user. Note: On some platforms (eg. Android) that allow selecting account for the consent, this is recorded each time that the account is changed and the buttons have to be redrawn. bsazonov@chromium.org dgn@chromium.org chrome-signin-team@google.com Records that the sync opt-in was completed by the user, and logs the original access point associated with this event. This is recorded when the user chooses to opt-in, whether they chose to proceed with the default settings or to open the sync settings first. {Profile} ernn@google.com rsult@google.com chrome-signin-team-desktop@google.com Records the count at which the Sync promo on the Identity Pill was shown when the user has successfuly intereacted with it (E.g. successfully turned sync). Recorded when that interaction was succesfully made. ernn@google.com chrome-signin-team@google.com Records that the sync opt-in was offered to the user and logs the original access point associated with this event. Recorded whenever the sync opt-in promo is shown (e.g. in the profile menu). Note: This is not recorded for every access point yet. rsult@google.com dgn@chromium.org chrome-signin-desktop-team@google.com Records that the user chose to navigate to the sync settings page from the sync confirmation screen. Logs this in the context of the access point associated with this event. bsazonov@chromium.org dgn@chromium.org chrome-signin-team@google.com Records that the sync confirmation screen was shown to the user, and logs the access point associated with this event. Note that due to some product quirks, this is recorded also when the "sync disabled" screen is shown, matching what happens with the completion event. See crbug.com/1398463 for more info. rsult@google.com chrome-signin-team@google.com Records the time spent from entering the Sync Paused state to {ResolutionType}. The value is recorded when the resolution method is applied. triploblastic@chromium.org chrome-signin-mobile-team@google.com This histogram records how many times sync promos have been shown (including the current one) across all access points when {Action} the {AccessPoint} sync promo (Android Only). bsazonov@chromium.org dgn@chromium.org chrome-signin-team@google.com Records that the user turned off sync, and logs the original access point associated with this event. {Profile} samarchehade@google.com chrome-signin-team@google.com Analogous to MobileFre.FromLaunch.{Event}. The amount of time between when the fullscreen signin and history sync promo activity was started and when {Event}. Android only. alexilin@chromium.org ahijazi@chromium.org chrome-signin-team@google.com Value indicating how the number of the bound refresh tokens relates to the total number of valid refresh tokens. This is recorded each time any tokens have been successfully loaded into memory from the database, which typically happens on startup. alexilin@chromium.org ahijazi@chromium.org chrome-signin-team@google.com Whether all refresh tokens in a single profile are bound to the same key. The expectation is that all tokens should be bound to the same key. This is recorded each time any tokens have been successfully loaded into memory from the database, which typically happens on startup. Recorded only if at least two of the successfully loaded tokens are bound. alexilin@chromium.org ahijazi@chromium.org chrome-signin-team@google.com Records the result of the assertion generation for a bound token exchange request. Recorded at the assertion generation completion, whenever a bound refresh token is exchanged for an access token or authentication cookies. alexilin@chromium.org ahijazi@chromium.org chrome-signin-team@google.com Records the result of generating a registration token for obtaining a bound refresh token. Recorded every time Chrome attempts to request a bound refresh token during Dice signin. This will not be recorded if token binding is not supported by either Chrome or GAIA. alexilin@chromium.org chrome-signin-team@google.com Records the total end-to-end duration required to perform an opportunistic refresh token binding upgrade against GAIA servers, including both local binding key registration JWT generation and the subsequent network API call. When an unbound session refresh token encounters a server challenge during access token minting, Chrome initiates this opportunistic upgrade. Recorded immediately upon the final completion or abortion of the upgrade flow (regardless of success or failure). alexilin@chromium.org chrome-signin-team@google.com Records whether token binding upgrade eligibility flag is enabled when starting an access token request. Recorded when an access token request is started. Desktop only. alexilin@chromium.org chrome-signin-team@google.com Records the network error code or HTTP response status of the opportunistic refresh token binding upgrade request sent to GAIA servers. When an unbound session refresh token encounters a server challenge during access token minting, Chrome initiates this opportunistic upgrade. Recorded immediately upon the completion of the upgrade API network call. alexilin@chromium.org chrome-signin-team@google.com Records whether a token binding upgrade was requested by the server upon successful completion of an access token request. Recorded when processing a successful access token response. Desktop only. alexilin@chromium.org chrome-signin-team@google.com Records the overall result of an opportunistic refresh token binding upgrade attempt, indicating whether it succeeded, failed due to local registration token generation error, or encountered network/server errors. When an unbound session refresh token encounters a server challenge during access token minting, Chrome initiates this opportunistic upgrade. Recorded upon the final completion or abortion of the token upgrade attempt. alexilin@chromium.org chrome-signin-team@google.com Records the result of attempting to save a refresh token binding key in memory and persist it. Recorded upon receiving the wrapped binding key from the opportunistic upgrade token flow. Desktop only. msarda@chromium.org Counts how many times the SQL statements to get all tokens is valid. ahijazi@chromium.org alexilin@chromium.org msarda@chromium.org chrome-signin-team@google.com Records the raw time spent querying the WebDatabase's 'token_service' table and decrypting the retrieved credentials on the database task runner. Measures from the moment the database query is executing inside TokenWebDataBackend::GetAllTokens, to the execution of SQLite query, up to when the tokens are successfully decrypted via OSCrypt. Recorded exactly once per profile startup. Note: Unlike Signin.RefreshTokensLoaded.Duration, this metric excludes thread hopping and in-memory delegate initialization overhead. alexilin@chromium.org chrome-signin-team@google.com Counts the results of loading wrapped binding keys from the token database. msarda@chromium.org Counts the results of loading a refresh token from the token database. alexilin@chromium.org chrome-signin-team@google.com Records the number of tokens removed from the token database when cleaning up unreadable credentials. This cleanup is triggered when updating credentials for an account if some tokens failed to load from the database earlier in the session (e.g. due to a transient decryption error). wfh@chromium.org chrome-signin-team@google.com Reports the status of a token write to the SQLite DB. This is reported each time a token is written to the SQLite DB. rsult@google.com chrome-signin-team@google.com Records the access point of Chrome Sign in when the user was in a web signed in only state before with the same account. Recorded when the Chrome Signin event occurres. rsult@google.com chrome-signin-team@google.com Records the time spent from being in Web Signin only to signing in to Chrome via {AccessPoint}. The value is recorded when signing in to Chrome. mlbipin@google.com chrome-signin-mobile-team@google.com The time taken for an to have cookies minted after a web sign-in or an account is added to android. Recorded from the creation of the WebSigninTracker until the account is successfully detected in the cookie, or until an error or timeout occurs.