mlerman@chromium.org Tracks user interactions as they sign in through a flow. The suffix of the histogram indicates what UI widget or application flow triggered the signin flow. fernandex@chromium.org 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@chromium.org 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. 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 avatar for one account in AccountFetcherService. This is recorded every time a User Avatar fetch request from AccountFetcherService succeeds. This histogram, along with Signin.AccountFetcher.AccountUserInfoFetchTime, will be used to decide whether to use OneGoogle library. 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 every time a User Info fetch request from AccountFetcherService succeeds. This histogram, along with Signin.AccountFetcher.AccountAvatarFetchTime, will be used to decide whether to use OneGoogle library. 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 consent by regular Gmail account or managed account. Recorded when the user signs in (iOS only). jlebel@chromium.org chrome-signin-team@chromium.org Records the sync consent done 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. samarchehade@chromium.org chrome-signin-team@google.com The time it takes to fetch the account information (user names, avatar) for one account on Android. This is recorded when account information is downloaded in FRE or when there is an accounts change event. bsazonov@chromium.org chrome-signin-team@google.com Number of Android accounts on device when entering the First Run Experience sign-in screen. alexilin@chromium.org bsazonov@chromium.org The time it takes to retrieve Gaia ids for all accounts from GoogleAuthUtil. alexilin@chromium.org bsazonov@chromium.org The time it takes to retrieve the list of accounts from the system. bsazonov@chromium.org chrome-signin-team@google.com Whether the persisted name of the FREMobileIdentityConsistencyStudy is consistent with the current value of low entropy source. Recorded on startup when the trial is registered. triploblastic@chromium.org chrome-signin-team@google.com The number of Android accounts present on the device. Recorded on startup. msarda@chromium.org droger@chromium.org Log the type of GAIA authentication error that occur whenever the error state changes. 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 cookie rotation request triggered by the bound session credentials feature. Recorded every time a cookie rotation request is performed. 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. 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 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. 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 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. 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. droger@chromium.org skym@chromium.org The number of signed in accounts in the cookie jar. 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. droger@chromium.org skym@chromium.org The number of signed out accounts in the cookie jar. droger@chromium.org skym@chromium.org The amount of time since the cookie jar last changed. droger@chromium.org skym@chromium.org The total number of accounts in the cookie jar. droger@chromium.org msarda@chromium.org Recorded when a Dice signin response is received and indicates whether the authorization code was present or not. droger@chromium.org msarda@chromium.org Records Dice responses (signin and signout). droger@chromium.org msarda@chromium.org Outcome of the token fetch in Dice signin. pastarmovj@chromium.org ydago@chromium.org 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. pastarmovj@chromium.org ydago@chromium.org 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. alexilin@chromium.org droger@chromium.org Result of the browser remote consent flow, which is a part of the chrome.identity.getAuthToken() extension API call. Desktop 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. 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. 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). droger@chromium.org msarda@chromium.org Reconds finished access token requests during Chrome reconcile, both successful or not, and return the GoogleAuthError state NONE is a success, other values are failures. mastiz@chromium.org msarda@chromium.org chrome-signin-team@google.com Records whether sync was turned on/consented on a profile at least once since the last time all profile data was wiped out (e.g. the user chose to clear data upon signout). This histogram is recorded upon profile load, and only for the case where the user is fully signed out. mastiz@chromium.org msarda@chromium.org chrome-signin-team@google.com Records whether sync was turned on/consented on a profile at least once since the last time all profile data was wiped out (e.g. the user chose to clear data upon signout). This histogram is recorded upon profile load, and only if sync is off (either the user is fully signed out, or the user is signed in without turning sync on). 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. alexilin@chromium.org chrome-signin-team@google.com Records various events that occur during the first run experience after the sign-in interception. ljjlee@google.com chrome-signin-team@google.com Records the latency for determining the signin interception heuristic, which runs for each signin interception. droger@chromium.org alexilin@chromium.org Records the outcome of the signin interception heuristic, which runs for each signin interception. alexilin@chromium.org droger@chromium.org Records the outcome of the enterprise signin interception bubble. Recorded when the bubble is dismissed. 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 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. 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. droger@chromium.org skym@chromium.org Current best guess if this device is shared between multiple users. 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 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 The status of the net or http communication to the Kids Management API. This is recorded for each request to the Kids Management API (ListFamilyMembers rpc). tju@google.com chrome-kids-eng@google.com This metric captures the latency of one individual call to the Kids Management API that might be retried if an error occurs. It includes both the actual RPC call and the time spent in requesting access token. For the overall request latency in retrying fetchers, see Signin.ListFamilyMembersRequest.OverallLatency. Googlers only: See go/chrome-kids-backend-monitoring for backend-related metrics. 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). tju@google.com chrome-kids-eng@google.com The status of every fetch to the Kids Management API, including the retried ones. The final status is case of retrying fetchers is recorded in Signin.ListFamilyMembersRequest.OverallStatus. tju@google.com chrome-kids-eng@google.com Latency of the calls to the Kids Management API that resulted with "{Status}" status. It includes both the actual RPC call and the time spent in requesting access token. 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). 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. 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. droger@chromium.org msarda@chromium.org Number of accounts in tokens sent to Gaia Multilogin. Recorded when Chrome does a request to /oauth/multilogin. alexilin@chromium.org droger@chromium.org Result of the OAuth2MintToken API call. 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. droger@chromium.org msarda@chromium.org Response status received from gaia Multilogin. bsazonov@chromium.org msarda@chromium.org chrome-signin-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). 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. droger@chromium.org msarda@chromium.org Records the execution time of the account reconciler using 100 buckets, up to 3 minutes. 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. 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. msarda@chromium.org droger@chromium.org This histogram records the success of setting each cookie after Multilogin response is received and parsed. bsazonov@chromium.org dgn@chromium.org chrome-signin-team@google.com Records that the user signed in to Chrome, and logs the original access point associated with this event. 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, 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: - This histogram is still in development and has a limited coverage of the Signin access points for now. See go/chrome-signin-metrics-revamp for more context on the planned work. - 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. 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. birnie@google.com bsazonov@chromium.org chrome-signin-team@google.com This histogram records the signin access point which was used when the signin disabled notification was shown. This is on Android only. droger@chromium.org chrome-signin-team@google.com Records the access point used by the `SigninManager` when setting the primary account. This is a subset of the histogram Signin.Signin.Completed, exclusively for the case when the primary account is set by `SigninManager`. msarda@chromium.org bsazonov@chromium.org droger@chromium.org chrome-signin-team@google.com Logs the reason of each completed sign in. 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. bsazonov@chromium.org dgn@chromium.org chrome-signin-team@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. skym@chromium.org If the user chose to delete their profile or not when signing out of an unmanaged account. When the user is not given a choice this metric is not recorded. msarda@chromium.org droger@chromium.org Track how a profile gets signed out. 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. jlebel@chromium.org chrome-signin-team@google.com Tracks the time it takes to call -[GCRSSOService identitiesWithError:] or -[GCRSSOService identitiesForDisplay]. See: https://crbug.com/897470. 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. birnie@google.com bsazonov@chromium.org chrome-signin-team@google.com This histogram records the sync access point which was used when the sync disabled notification was shown. This is on Android only. triploblastic@chromium.org bsazonov@chromium.org Records various UI and user action events related to the sync error message. Android only. triploblastic@chromium.org bsazonov@chromium.org Tracks where FirstSetupComplete bit is set from. 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. bsazonov@chromium.org dgn@chromium.org chrome-signin-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. triploblastic@chromium.org chrome-signin-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. msarda@chromium.org Counts how many times the SQL statements to get all tokens is valid. msarda@chromium.org Counts the results of loading a refresh token from the token database. alexilin@chromium.org fhorschig@chromium.org Recorded whenever the user interacts with reauthentication to complete a transaction (like interacting with the account store for passwords) and whether the reauth challenge was cleared. alexilin@chromium.org droger@chromium.org Records user actions performed in the reauthentication dialog/tab. triploblastic@google.com bsazonov@chromium.org User requested to wipe local device data on signout. This histogram is only recorded when the user is given a choice of whether or not to wipe data (not in cases where the data is either automatically wiped or automatically not wiped).