rogerta@chromium.org The frequency of ways that new user profiles are added. droger@chromium.org chrome-signin-team@google.com Records the outcome of signed-in profile creation whenever it's started (by user choosing to sign-in in the first screen of the profile creation flow). droger@chromium.org chrome-signin-team@google.com Classification of what gaia names appear or appeared in this profile since the last time gaia cookies got deleted. Thus, this also includes signed-out accounts. In order to protect privacy, only reports whether multiple distinct gaia names appeared in this profile and if so, whether sync is enabled for one of them. Furthermore, this metric uses a low-entropy hash to detect distinct names. In case of a rare hash collision (less than 0.1% of cases), multiple names get recorded as a single name. Recorded on every activation of a Chrome window (for the respective profile). etienneb@chromium.org gab@chromium.org The number of installed apps when a profile is opened. droger@chromium.org chrome-signin-team@google.com The frequency of selection of each avatar. etienneb@chromium.org gab@chromium.org Size of the bookmarks database. msarda@chromium.org tangltom@chromium.org Recorded every time a browser window becomes active. Each profile on a client is assigned a unique bucket, i.e. whenever a browser window of profile x becomes active, an entry is recorded in bucket x. Example: A user has 2 profiles and opens 1 browser window for each of them. When the user switches back and forth between the windows, multiple entries will be recorded in bucket 1 and 2, corresponding to the profiles. Note: The guest profile has bucket 0. Regular profiles start at bucket 1. Incognito browser windows count towards the original profile. msarda@chromium.org droger@chromium.org anthonyvd@chromium.org This histogram tracks which UI screen was used to initiate and confirm the deletion of a profile. This does not track when the profile is actually deleted, which is an asynchronous process that happens later. Not all buckets in the histogram correspond to profile deletion so the sum is not the count of deleted profiles. alexilin@chromium.org droger@chromium.org msalama@chromium.org This histogram tracks the context of profile deletion whenever a profile is scheduled for deletion (from user action in the UI). Only recorded if the profile has a valid entry in ProfileAttributesStorage. arabm@google.com chrome-incognito@google.com Track if the off-the-record profile was immidiately destroyed when asked to be destroyed, or was scheduled for a delayed destruction, and possibly was not destroyed properly after the delay and was crashed. msarda@chromium.org tangltom@chromium.org This histogram tracks whether the accounts cached in the GAIA cookie service manager are stale when presenting the user menu when DICE is enabled. nicolaso@chromium.org cbe-eng@google.com Whether any profile reached a refcount of 0 at any point, prior to exiting Chrome. Recorded during teardown. arabm@google.com chrome-incognito@google.com Records if a Guest session is started by user's request or is forced by a policy. This is recorded when a Guest profile is created. rhalavati@chromium.org chrome-incognito@google.com This histogram records the lifetime duration of an off-the-record Guest profile. It is recorded once the profile for the Guest session is closed. dgn@chromium.org chrome-signin-team@google.com Records the type of Guest profile created, either a parent guest or the first child (off-the-record) guest profile for the active parent guest profile. It is recorded during the guest profile creation. rhalavati@chromium.org chrome-incognito@google.com This histogram records the lifetime duration of incognito profiles. It is recorded once an off the record profile for an incognito session is closed. From M91, this metric is not recorded for ChromeOS non user-triggered Incognito profiles. rhalavati@chromium.org chrome-incognito@google.com This histogram records the number of mainframe navigations that have been done during one Incognito session. It is recorded once an off the record profile for an incognito session is closed. From M91, this metric is not recorded for ChromeOS non user-triggered Incognito profiles. rhalavati@chromium.org chrome-incognito@google.com This histogram records the duration of an Incognito session on Android, when it goes to background or is closed by the user. The session duration is considered from when the Incognito profile is created. rhalavati@chromium.org chrome-incognito@google.com When Chrome comes back to foreground on Android and it already has an Incognito session, this histogram records the last duration time reported by 'Profile.Incognito.MovedToBackgroundAfterDuration' metric. The subtraction of these two histograms can give a histogram of Incognito session duration. nicolaso@chromium.org cbe-eng@google.com Recorded during BrowserProcess teardown. Indicates that a Profile still has ScopedProfileKeepAlive objects referencing it, of the given origin. This is a sign of a bug, or incorrect usage of the ScopedProfileKeepAlive API. Only regular Profiles are considered for this metric (no Incognito, Guest, or System Profiles). droger@chromium.org rsult@google.com chrome-signin-team@google.com Records the number of KeyedServices active for the System {ProfileType} Profile. This record is captured when the System {ProfileType} Profile is destroyed. It is currently done only when Chrome exits. In the future, there are plans to destroy System profiles as soon as the profile picker window is closed. This histogram considered a KeyedService as active even if NULL. This was fixed in M-106 in commit 903912cd. Non-NULL KeyedServices were no longer counted. However, that change forgot to revise the histogram names. The meaning of values in his histogram changed. In order to avoid having a histogram with a meaning that differs by Chrome version, this histogram was renamed in M-107 to Original-M-107. Original-M-107 counts only non-NULL KeyedServices. This histogram considered a KeyedService as active even if NULL. This was fixed in M-106 in commit 903912cd. Non-NULL KeyedServices were no longer counted. However, that change forgot to revise the histogram names. The meaning of values in his histogram changed. In order to avoid having a histogram with a meaning that differs by Chrome version, this histogram was renamed in M-107 to OTR-M-107. OTR-M-107 counts only non-NULL KeyedServices. dgn@chromium.org chrome-signin-team@google.com Tracks how often we have to render Lacros FRE whose welcome pages don't have a given name to display. We expect that it's very rare, if we have a non-trivial number of these without a given name, we will have to redesign the experience to nicely accomodate for it. dgn@chromium.org droger@chromium.org Records the entry point that triggered the lacros first run for the primary profile being shown. This is recorded when the first run is shown. If the FRE is skipped, this is never recorded. If the FRE is exited early and needs to be shown again, or if the user re-triggers the FRE while it is already shown, there would be more than one record for that install. dgn@chromium.org droger@chromium.org Records the outcome of the lacros first run for the primary profile (also in the case it gets skipped silently). nicolaso@chromium.org cbe-eng@google.com Number of Profiles that are currently loaded in memory, with a non-zero refcount. Recorded 30 minutes after startup, and every 30 minutes afterwards. Only regular Profiles are considered for this metric (no Incognito, Guest, or System Profiles). See also Profile.ZombieProfileCount, the number of Profiles with a refcount of 0. droger@chromium.org msarda@chromium.org chrome-signin-team@google.com Recorded when an actionable item(e.g. button, link) in the profile menu is clicked. rogerta@chromium.org Counts of users added and deleted. Percentages are not meaningful. Please look at the ratio of the counts/percentages. nicolaso@chromium.org cbe-eng@google.com Recorded when a profile directory gets deleted from disk, e.g. because it was an ephemeral profile, or the user requested its destruction. Indicates whether the operation succeeded or failed. If the operation fails, it may be retried (up to 3 times). Each try is tracked as a separate enum value. msarda@chromium.org droger@chromium.org Counts the number of Google-managed accounts linked to a profile. This may be counted multiple times per profile. Please review with the "Show user counts" option enabled on the dashboard. droger@chromium.org feuunk@chromium.org Counts the number of profiles on a user's machine every 24 hours while Chrome is running. As opposed to Profile.NumberOfProfiles, this counts only profiles that have been used in the last 28 days. agawronska@chromium.org michaelpg@chromium.org cros-families-eng@google.com Counts the number of locally managed profiles on a user's machine every 24 hours while Chrome is running, among cases with at least one profile. This counts only profiles that have been used in the last 28 days. Might have incomplete data between 2021-03-12 and 2021-05-26. droger@chromium.org chrome-signin-team@google.com Counts the number of profiles on a user's machine every 24 hours while Chrome is running. This counts the total number of profiles on the user's device, regardless of whether they've been used recently. droger@chromium.org chrome-signin-team@google.com Records the count of profiles for each profile switch (incl. switching between concurrently open profiles by activating their browser windows). The count excludes the Guest profile so records in bucket 1 denote switches between the single profile and the Guest profile. droger@chromium.org chrome-signin-team@google.com Counts the number of signed-in (syncing) profiles on a user's machine every 24 hours while Chrome is running. This counts only profiles that have been used in the last 28 days. msarda@chromium.org droger@chromium.org Counts the number of profiles unused within the past 28 days on a user's machine. This is recorded every 24 hours while Chrome is running. agawronska@chromium.org michaelpg@chromium.org cros-families-eng@google.com Tracks the percentage (0-100) of profiles that are locally managed, recorded when Chrome starts up. rsult@google.com chrome-signin-team@google.com Counts the number of times the user reorders profiles by drag and drop in the profile picker. Recorded every time the profile ordering changes. msarda@chromium.org alexilin@chromium.org Browsing session duration in minutes, recorded per profile. Each profile on a client is assigned a unique bucket. Recorded when the user switches profiles, after some time of inactivity(usually 5 minutes) or at browser shutdown. Example: A user has 2 profiles. They open a browser window of profile 1 and interact with the browser for 8 minutes. Then they open a browser window of profile 2 and interact with the browser for 3 minutes. Then they do nothing (=stay inactive) for while. The recorded values will be: (bucket 1: 8), (bucket 2: 3). Note: The guest profile has bucket 0. Regular profiles start at bucket 1. Incognito profiles count towards the original profile. droger@chromium.org chrome-signin-team@google.com The state of profile avatars as would be displayed to the user in the profile picker. Recorded on startup of Chrome and whenever Chrome is used after at least 30 minutes of inactivity. droger@chromium.org chrome-signin-team@google.com The number of days since a profile was last used. Recorded on startup of Chrome and whenever Chrome is used after at least 30 minutes of inactivity. droger@chromium.org chrome-signin-team@google.com The sync status of the profile. Recorded on startup of Chrome and whenever Chrome is used after at least 30 minutes of inactivity. droger@chromium.org chrome-signin-team@google.com The type of profile's unconsented primary account. Recorded on startup of Chrome and whenever Chrome is used after at least 30 minutes of inactivity. etienneb@chromium.org gab@chromium.org Total size of the profile data (excluding sub-folders). robertshield@chromium.org Indicates whether a profile had a reset trigger that caused it to launch a reset flow. The presence of this trigger is recorded during profile creation. msarda@chromium.org tangltom@chromium.org Helper histogram to track user actions per profile. Recorded when there is an active profile browser instance and a UMA UserAction is recorded, i.e. if there's an active profile, a recording of a UMA UserAction will result in a recording of a sample in this histogram. Each profile on a client is assigned a unique bucket, i.e. whenever a user action happens in a browser of profile x, an entry is recorded in bucket x. This histogram is used in the profile dashboard, see go/profile-metrics and go/profile-metrics-dashboard. Example: A user has 2 profiles and opens a browser window for each of them. When the user adds a new tab in each of the browsers, an entry is recorded in bucket 1 and 2, corresponding to the profiles. (Adding a new tab is a recorded user metrics action.) Note: The guest profile has bucket 0. Regular profiles start at bucket 1. Incognito profiles count towards the original profile. nicolaso@chromium.org cbe-eng@google.com Number of Profiles that are in a "zombie" state. Recorded 30 minutes after startup, and every 30 minutes afterwards. Only regular Profiles are considered for this metric (no Incognito, Guest, or System Profiles). A "zombie" profile is one of 2 things, depending on the DestroyProfileOnBrowserClose (DPoBC) variation: If DPoBC is false: the Profile has a refcount of 0, but is still loaded in memory. If DPoBC is false: the Profile object was destroyed, and isn't loaded in memory anymore. When a Profile is destroyed but gets loaded from disk again, it stops being a zombie. See also Profile.LiveProfileCount, the number of profiles with a non-zero refcount. etienneb@chromium.org gab@chromium.org Size of the {Database} database. These metrics were expired between July 2022 and June 2023 and may be missing data. vasilii@chromium.org ewald@chromium.org Whether any profile was shown in the list when the profile chooser was opened. msalama@chromium.org chrome-signin-team@google.com Records the state of the "Ask on startup" user preference that controls whether the profile picker should be shown on startup. Recorded on startup of Chrome. msalama@chromium.org chrome-signin-team@google.com Records the state of the "Ask on startup" checkbox upon user action to check/uncheck "Ask on startup" in the profile picker main screen. dgn@chromium.org chrome-signin-team@google.com [Desktop] The reason for which profile picker startup profiling was deemed complete. Logged once per session when the user opens a profile from the profile picker shown on startup. Used to understand user behavior shifts when ProfilePicker.FirstProfileTime.FirstWebContentsNonEmptyPaint regresses dgn@chromium.org chrome-signin-team@google.com Measure the elapsed time from when the user selects a profile on the startup profile picker to the first non empty paint of the first web contents. This is recorded when the user selects an existing profile from that profile picker shown on startup. Together with ProfilePicker.StartupTime.FirstPaint.FromApplicationStart, this metric is intended to capture the startup latency for a common case where Startup.FirstWebContents.NonEmptyPaint3 is not recorded due to the profile picker interrupting browser startup. dgn@chromium.org gabolvr@google.com for-you-fre@google.com Records the user's choice for the prompt asking if they want to set Chrome to be their default browser, in the first run experience. dgn@chromium.org for-you-fre@google.com Records the entry point that triggered the first run experience. This is recorded right before the first run is shown. If the FRE is skipped, this is never recorded. If the FRE is exited early and needs to be shown again (relevant only on Lacros where we support showing the FRE more than once), or if the user re-triggers the FRE while it is already shown, there would be more than one record for that install. Note: Profile.LacrosPrimaryProfileFirstRunEntryPoint on Lacros records the same data. dgn@chromium.org for-you-fre@google.com Records the status when the first run experience is exited. Note that some experiments can override the behaviour at the end of the first run, based on the the status. This histogram is recorded before the override happens. dgn@chromium.org for-you-fre@google.com Records the reason why the first run experience was marked finished. This aims at tracking how often policies or some pre-existing state suppresses the first run experience. It is tracked by the first run service itself, when the flow completes (or is suppressed). dgn@chromium.org jyammine@google.com chrome-signin-team@google.com Records the time between the first run of Chrome on Desktop is loaded and the organization name is available to be shown in the enterprise disclaimer. This is only logged if the device is managed and the policy store is loaded in the specified time delay. dgn@chromium.org jyammine@google.com chrome-signin-team@google.com Records the loading state of the clould policy store when it is loaded or after a specified time delay. This is recorded for the first run experience on desktop for managed devices. This is needed to track if the managed organization name has been properly displayed in the first run experience managed disclaimer. dgn@chromium.org for-you-fre@google.com Records first run service creations in this current profile. true is recorded if the service was successfully created, and false is recorded if it was suppressed because the feature is disabled. If this is not the first run or the profile is not able to display the first run experience, nothing will be recorded. msalama@chromium.org chrome-signin-team@google.com Records the reason why the profile picker has been shown to the user. Recorded every time the profile picker window is shown or reactivated. droger@chromium.org dgn@chromium.org chrome-signin-team@google.com The startup mode, used to decide whether the profile picker is shown at startup. Recorded during Chrome startup, at {StartupStep}. droger@chromium.org dgn@chromium.org chrome-signin-team@google.com The reason for the startup mode, used to decide whether the profile picker is shown at startup. Recorded during Chrome startup, at {StartupStep}. alexilin@chromium.org dgn@chromium.org chrome-signin-team@google.com Records the time between Chrome startup and the call to ProfilePickerView::Display(). Only recorded when the profile picker is shown at startup. alexilin@chromium.org dgn@chromium.org chrome-signin-team@google.com Records the time between web view creation and the first paint. Only recorded when the profile picker is shown at startup. alexilin@chromium.org dgn@chromium.org chrome-signin-team@google.com Records the time from the application start to the first non-empty paint of proflie picker's web contents. Only recorded when the profile picker is shown at startup. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of application start. alexilin@chromium.org dgn@chromium.org chrome-signin-team@google.com Records the time between web view creation and main view being initialized in javascript. Only recorded when the profile picker is shown at startup. alexilin@chromium.org dgn@chromium.org chrome-signin-team@google.com Records the time between ProfilePickerView::Display() is called and the web view creation. Only recorded when the profile picker is shown at startup. msalama@chromium.org chrome-signin-team@google.com Represents user navigation in the profile picker. Recorded every time a different UI is visible in the profile picker. msalama@chromium.org chrome-signin-team@google.com Records the action performed by the user in the profile picker. proberge@chromium.org Encodes from where the request for resetting the profile settings originated.