Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(3263)

Unified Diff: chrome/browser/profiles/profile_metrics.h

Issue 288493008: UMA Metrics for the user menu, including vasquette-detection (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src
Patch Set: Change histogram bucket order for maintainability. Created 6 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: chrome/browser/profiles/profile_metrics.h
diff --git a/chrome/browser/profiles/profile_metrics.h b/chrome/browser/profiles/profile_metrics.h
index 174c203c239affe270a5e0092e43b6a61ca85ab5..96e05e17ceaff3be37d814b9c7b5329383485064 100644
--- a/chrome/browser/profiles/profile_metrics.h
+++ b/chrome/browser/profiles/profile_metrics.h
@@ -96,6 +96,30 @@ class ProfileMetrics {
NUM_PROFILE_ENROLLMENT_METRICS,
};
+ // Enum for tracking user interactions with the user menu and user manager,
+ // including tracking if the vasquette was the start for user interaction.
+ // Note that the Enums are in pairs, with a base action coming first and the
+ // following item indicating the same action but initiated from the content
+ // area. An example of the interaction beginning in the content area is
+ // clicking "Manage Accounts" within account selection on a Google property.
+ enum ProfileDesktopSignout {
+ // User opened the user menu directly, and clicked lock.
+ PROFILE_DESKTOP_MENU_LOCK = 0,
+ // The content area caused the user menu to open, the user clicked lock.
+ PROFILE_DESKTOP_MENU_LOCK_FROM_CONTENT,
+ // User opened the user menu directly, and started removing an account.
+ PROFILE_DESKTOP_MENU_REMOVE_ACCT,
+ // The content area caused the user menu to open, the user started removing
+ // an account.
+ PROFILE_DESKTOP_MENU_REMOVE_ACCT_FROM_CONTENT,
+ // User opened the user menu directly, and started adding an account.
+ PROFILE_DESKTOP_MENU_ADD_ACCT,
+ // The content area caused the user menu to open, the user started adding an
+ // account.
+ PROFILE_DESKTOP_MENU_ADD_ACCT_FROM_CONTENT,
+ NUM_PROFILE_DESKTOP_SIGNOUT_METRICS,
+ };
+
static void UpdateReportedProfilesStatistics(ProfileManager* manager);
static void LogNumberOfProfiles(ProfileManager* manager);
@@ -108,6 +132,8 @@ class ProfileMetrics {
static void LogProfileSyncInfo(ProfileSync metric);
static void LogProfileAuthResult(ProfileAuth metric);
static void LogProfileUpgradeEnrollment(ProfileUpgradeEnrollment metric);
+ static void LogProfileDesktopSignout(ProfileDesktopSignout metric,
+ bool opened_from_content);
// These functions should only be called on the UI thread because they hook
// into g_browser_process through a helper function.
« no previous file with comments | « no previous file | chrome/browser/profiles/profile_metrics.cc » ('j') | chrome/browser/profiles/profile_metrics.cc » ('J')

Powered by Google App Engine
This is Rietveld 408576698