rogerta@chromium.org The frequency of ways that new user profiles are added. rsult@google.com 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). 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 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 dullweber@chromium.org 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. 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. Warning: this histogram was expired from 2023-10-11 to 2024-06-18; data may be missing. duellweber@chromium.org 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. arabm@google.com 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. 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. arabm@google.com 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. arabm@google.com 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). Warning: this histogram was expired from 2024-04-28 to 2024-06-18; data may be missing. 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. Warning: this histogram was expired 2023-10-11 to 2024-06-18; data may be missing. rsult@google.com droger@chromium.org chrome-signin-desktop-team@google.com Recorded when an actionable item (e.g. button, link) in the profile menu is clicked. {ProfileType}. 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. Warning: this histogram was expired 2024-04-28 to 2024-06-18; data may be missing. 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 used in the last {ProfileActivityThreshold} on a user's machine. Only emitted for users with at least one profile (of any type). This histogram can be compared with Profile.NumberOfProfiles, which counts all profiles regardless of activity and also is emitted on clients with no profiles of any type. These include only "regular" profiles; neither of these histograms include system or guest profiles even if some are open at the time the histogram is emitted. Both histograms do not count incognito profiles separately; they are considered part of their "parent" profile. However, as of Feb 2024 intention is not reality. Chrome on Android assumes the (sole) profile is active, even if it is not. Before M129, Chrome on iOS assumed the (sole) profile is inactive, even if it is active. On desktop platforms (all milestones) and on iOS M129+, the activity detection is believed to work reliably. Also of note: ChromeOS has a notion of "users". A ChromeOS device may have multiple users. Users are an entirely different concept than profiles. ChromeOS may allow a user to have and use multiple profiles someday. As of Feb 2024, it does not. On non-iOS platforms, this histogram is emitted on startup if it has been more than 24 hours since the last time the histogram was emitted. It is also emitted while Chrome is running when Chrome realizes that it has been 24 hours since the last time the histogram was emitted. (This normally happens 24 hours after the last emit, but may be longer if the device was asleep / suspended at the time. If so, it will be emitted when the device wakes up.) One consequence of this 24 hour timer is that a user may use Chrome in a day and not emit this histogram. For example, if a user used Chrome the previous day at 5pm and a histogram was emitted then, then used Chrome on this day at 10am, then closed Chrome, this histogram will not be emitted on this day. On iOS, this histogram is always emitted on profile open and not emitted any other time. agawronska@chromium.org cros-families-eng@google.com Counts the number of locally managed profiles on a user's machine. Only emitted for users with at least one profile (of any type). Does not include guest profiles even if they are managed per device policy and even if one is open at the time the histogram is emitted. An incognito profile is also not counted separately (even if it is managed); it is considered part of its "parent" profile. This is intended to count only profiles that have been used in the last {ProfileActivityThreshold}. However, active usage detection does not work correctly on all platforms and for all Chrome versions. See details in the description of Profile.NumberOfActiveProfiles. On non-iOS platforms, this histogram is emitted on startup if it has been more than 24 hours since the last time the histogram was emitted. It is also emitted while Chrome is running when Chrome realizes that it has been 24 hours since the last time the histogram was emitted. (This normally happens 24 hours after the last emit, but may be longer if the device was asleep / suspended at the time. If so, it will be emitted when the device wakes up.) One consequence of this 24 hour timer is that a user may use Chrome in a day and not emit this histogram. For example, if a user used Chrome the previous day at 5pm and a histogram was emitted then, then used Chrome on this day at 10am, then closed Chrome, this histogram will not be emitted on this day. On iOS, this histogram is always emitted on profile open and not emitted any other time. 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. Includes only "regular" profiles; does not include system or guest profiles even if some are open at the time the histogram is emitted. An incognito profile is also not counted separately; it is considered part of its "parent" profile. Note: ChromeOS has a notion of "users". A ChromeOS device may have multiple users. Users are an entirely different concept than profiles. ChromeOS may allow a user to have and use multiple profiles someday. As of Feb 2024, it does not. On non-iOS platforms, this histogram is emitted on startup if it has been more than 24 hours since the last time the histogram was emitted. It is also emitted while Chrome is running when Chrome realizes that it has been 24 hours since the last time the histogram was emitted. (This normally happens 24 hours after the last emit, but may be longer if the device was asleep / suspended at the time. If so, it will be emitted when the device wakes up.) One consequence of this 24 hour timer is that a user may use Chrome in a day and not emit this histogram. For example, if a user used Chrome the previous day at 5pm and a histogram was emitted then, then used Chrome on this day at 10am, then closed Chrome, this histogram will not be emitted on this day. On iOS, this histogram is always emitted on profile open and not emitted any other time. This counts the total number of profiles on the user's device, regardless of whether they've been used recently. alexilin@chromium.org chrome-signin-team@google.com Records the count of profiles every time a profile is initialized. The count includes the newly initialized profile. Only recorded for on-disk profiles (Incognito and Guest are excluded, for example). The total histogram count can be used to estimate how many profiles were initialized in total. 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. Only emitted for users with at least one profile (of any type). This is intended to count only profiles that have been used in the last {ProfileActivityThreshold}. However, active usage detection does not work correctly on all platforms and for all Chrome versions. See details in the description of Profile.NumberOfActiveProfiles. On non-iOS platforms, this histogram is emitted on startup if it has been more than 24 hours since the last time the histogram was emitted. It is also emitted while Chrome is running when Chrome realizes that it has been 24 hours since the last time the histogram was emitted. (This normally happens 24 hours after the last emit, but may be longer if the device was asleep / suspended at the time. If so, it will be emitted when the device wakes up.) One consequence of this 24 hour timer is that a user may use Chrome in a day and not emit this histogram. For example, if a user used Chrome the previous day at 5pm and a histogram was emitted then, then used Chrome on this day at 10am, then closed Chrome, this histogram will not be emitted on this day. On iOS, this histogram is always emitted on profile open and not emitted any other time. msarda@chromium.org droger@chromium.org Counts the number of profiles that have not been used within the past 28 days on a user's machine. Only emitted for users with at least one profile (of any type). This is intended to count only profiles that have not been used in the last {ProfileActivityThreshold}. However, active usage detection does not work correctly on all platforms and for all Chrome versions. See details in the description of Profile.NumberOfActiveProfiles. On non-iOS platforms, this histogram is emitted on startup if it has been more than 24 hours since the last time the histogram was emitted. It is also emitted while Chrome is running when Chrome realizes that it has been 24 hours since the last time the histogram was emitted. (This normally happens 24 hours after the last emit, but may be longer if the device was asleep / suspended at the time. If so, it will be emitted when the device wakes up.) One consequence of this 24 hour timer is that a user may use Chrome in a day and not emit this histogram. For example, if a user used Chrome the previous day at 5pm and a histogram was emitted then, then used Chrome on this day at 10am, then closed Chrome, this histogram will not be emitted on this day. On iOS, this histogram is always emitted on profile open and not emitted any other time. longbowei@google.com zhangwenyu@google.com cros-families-eng@google.com Tracks the percentage (0-100) of profiles that are locally managed. Only emitted for users with at least one profile (of any type). Both numerator and denominator include only "regular" profiles; neither include system or guest profiles (even if some are open at the time the histogram is emitted and even if guest profiles are managed per device policy). Likewise, both histograms do not count incognito profiles separately (even if managed); they are considered part of their "parent" profile. This is intended to count only profiles in the numerator that have been used in the last {ProfileActivityThreshold}. However, active usage detection does not work correctly on all platforms and for all Chrome versions. See details in the description of Profile.NumberOfActiveProfiles. On non-iOS platforms, this histogram is emitted on startup if it has been more than 24 hours since the last time the histogram was emitted. It is also emitted while Chrome is running when Chrome realizes that it has been 24 hours since the last time the histogram was emitted. (This normally happens 24 hours after the last emit, but may be longer if the device was asleep / suspended at the time. If so, it will be emitted when the device wakes up.) One consequence of this 24 hour timer is that a user may use Chrome in a day and not emit this histogram. For example, if a user used Chrome the previous day at 5pm and a histogram was emitted then, then used Chrome on this day at 10am, then closed Chrome, this histogram will not be emitted on this day. On iOS, this histogram is always emitted on profile open and not emitted any other time. etienneb@chromium.org chrome-signin-team@google.com Counts the number of times a profile error dialog is shown. The dialog will ask the user if they want to upload an error report for Google to debug the issue. 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 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. {ProfileStateGroup} 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. {ProfileStateGroup} 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. {ProfileStateGroup} etienneb@chromium.org gab@chromium.org Total size of the profile data (excluding sub-folders). anthonyvd@chromium.org chrome-catan@google.com Total size of the profile data (including sub-folders). Recorded with some delay after a profile is loaded, excluding off-the-record profiles. 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. spvm@chromium.org catan-team@chromium.org Records the status of the creation/acquiry of the Profile.lock file on Windows in a {BrowserProfileType} profile. Specifically whether it was locked by another process or if the previous session crashed. Recorded once per profile load. spvm@chromium.org catan-team@chromium.org Records the status of the previous exit of the profile load for a {BrowserProfileType} profile on Windows. Specifically, whether there was a crash, and whether there was an unacked crash bubble present. Recorded once per profile load only if Profile.lock was successfully acquired and both Profile.waiting_for_crash_ack and Profile.crashed were successfully created. spvm@chromium.org catan-team@chromium.org Records the Windows error code following the {Operation} call on the `Profile.{File}` file in a {BrowserProfileType} profile, which may otherwise corrupt subsequent data reporting of Profile.Windows.LoadStatus given that the marker files were left around. 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. droger@chromium.org chrome-password-manager-metrics-alerts@google.com 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. atharvmaan@google.com chrome-desktop-ui-waterloo@google.com Same as ProfilePicker.FirstProfileTime.FirstWebContentsNonEmptyPaint, but recorded only for browser launches initiated automatically by the OS. dgn@chromium.org 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 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). ernn@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. ernn@google.com rsult@google.com chrome-signin-desktop-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. ernn@google.com kbajkiewicz@google.com chrome-signin-desktop-team@google.com Records the Feature Showcase step the user was looking at when they clicked the 'Start Browsing' button. ernn@google.com kbajkiewicz@google.com chrome-signin-desktop-team@google.com Records the Feature Showcase step when it is eligible to be shown to the user during the first run experience. Recorded when the user first enter the Feature Showcase step. Records each step the user is eligible for. ernn@google.com kbajkiewicz@google.com chrome-signin-desktop-team@google.com Records the Feature Showcase step when it is shown to the user during the first run experience. Recorded every time a step is shown. ernn@google.com kbajkiewicz@google.com chrome-signin-desktop-team@google.com Records the action taken by the user on the {FeatureShowcaseStep} step in the First Run Experience Feature Showcase. Recorded when the step is completed. ernn@google.com kbajkiewicz@google.com chrome-signin-desktop-team@google.com Records when the user changes the theme or color scheme mode on the Themes and Customization step of the First Run Experience Feature Showcase. Recorded the first (and only) time a user interacts with the color picker on the Themes and Customization step. ernn@google.com kbajkiewicz@google.com chrome-signin-desktop-team@google.com Records the step every time the user clicks on the media effects action button in the First Run Experience flow to {Action} media effects, i.e. sound and animations (if applicable). rsult@google.com chrome-signin-team@google.com Recorded when the user is reauth-ing to unlock a Profile using the profile picker flows. Records successful and failed flows. 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@google.com ernn@google.com chrome-signin-team@google.com Records steps from the ProfilePickerSignInProvider, when they are reached. Introduced for debugging https://crbug.com/445316497, extended to provide better insights into the flow during the FRE refresh project. rsult@google.com 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. Warning: this histogram was expired from 2025-07-13 to 2025-09-02; data may be missing. rsult@google.com 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 profile picker's web contents. Only recorded when the profile picker is shown at startup. See Startup.FirstWebContents.NonEmptyPaint3 for a definition of application start. Warning: this histogram was expired from 2025-07-13 to 2025-09-02; data may be missing. {StartupTemperatureSuffix} 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. rsult@google.com chrome-signin-team@google.com Records the step at which the flow was ended. The value is emitted when the flow is completed or aborted. {ProfilePickerFlowType} rsult@google.com chrome-signin-team@google.com Records the total flow duration. The value is emitted when the flow is completed or aborted. {ProfilePickerFlowType} anthie@google.com rsult@google.com chrome-signin-team@google.com Records the error type when there is an error during the sign-in flow. {ProfilePickerFlowType} rsult@google.com chrome-signin-team@google.com Records the duration of {StepName} {StepFlowDuration}. The value is emitted when the step is ended or switched. {ProfilePickerFlowType} rsult@google.com chrome-signin-team@google.com Records the step that {StepStatus}. Recorded when the step status change happens. {ProfilePickerFlowType}