Investigate difference between Signin_Impression_FromRecentTabs and Signin.SigninStartedAccessPoint.RecentTabs |
||
Issue descriptionOn M49-A Beta we're seeing a difference between the Signin_Impression_FromRecentTabs user aciton and the "recent tabs" bucket of Signin.SigninStartedAccessPoint. Since we just embed the sign in screen directly in the recent tabs UI on Android, these two numbers should theoretically be the same (since every impression is also a "started"). We should understand why there's a difference and make sure there's nothing wrong with the code.
,
Mar 3 2016
Okay got it. So really Signin_Impression_FromRecentTabs is the more accurate count of true "impressoins." That makes sense. One more thing to investigate before closing this out: on Beta Android, Signin_Impression_FromStartPage is much less than Signin.SigninStartedAccessPoint.[Start page]. This is the reverse of the recent tabs case (the user action is less than the access point). Any idea why this is happening?
,
Mar 21 2016
Closing this out since the original discrepancy has been resolved. I'll open another bug about the start page. |
||
►
Sign in to add a comment |
||
Comment 1 by gogerald@chromium.org
, Mar 3 2016