Skip to main content
joe_was_taken
joe_was_taken
Level 2
July 28, 2011
Delivered

Mobile Browsers should not be classified as "None" in Browsers Report

  • July 28, 2011
  • 29 replies
  • 26560 views

Today the "Browsers" report, classifies mobile devices as "None".

 

Displaying "None" even when a User-Agent is clearly captured, represents a confusing and misleading end-user experience.

 

If anything, this behavior only breeds mistrust of all reported data.

 

At a minimum, the "Browsers" report should behave similar to the "Browsers Type" report by presenting an "Other".

 

None should be reserved for the instances where the user-agent is unavailable, obscure, or otherwise not reasonably classifiable.

    29 replies

    Show previous replies
    hangt3385890
    hangt3385890
    Level 2
    January 31, 2013

    totally in need of #1 being available as soon as possible please!!!

    Melissa_Kavanag
    Melissa_Kavanag
    Level 2
    January 21, 2013

    Yes, I have numerous questions from users on this report because of the "none" category. I would be nice to just have it say "mobile."

    tbahama_mroberts
    New Participant
    November 26, 2012

    Please fix.  Not having this correct under-represents Safari as a browser in a big way. 

    benjamingaines2
    benjamingaines2
    Employee
    November 12, 2012
    This one is under consideration for a future release.
    bl87461
    bl87461
    New Participant
    November 1, 2012

    I'm behind this.  Tablets and other mobile devices are moving towards becoming the primary computing device for a a significant number of people.

     

    As a first step, taking the mobile browser out of the 'None' category is right, but we should also be looking to get more detail from the UA string or similar as well.

    danm84141867
    danm84141867
    Level 4
    October 25, 2012

    Our Browser report shows "None" as one of the top browser in many of our report suites. When I break that "None" down by user agent string, I see that almost all of them are mobile browsers. Please update the list of user agent strings used in the Browser report to include mobile browsers.

    JeroenJaspar
    JeroenJaspar
    Level 2
    September 21, 2012

    I also talked with Clientcare about the difference between "Browser" and "Browser Type" report.

    That all has to do with the "None" part.

    You can correlate the "Browser" Report with "Mobile OS" and so have a complete list, but it isn't possible to do this with the "Browser" Type Report.

     

    ClientCare responded: Currently this is working as we expect it to. 

    This can be true, but I hope they take this Idea in next Release to make the two reports behave logical and not as strange as currently.

    ericmatisoff1
    ericmatisoff1
    Level 5
    August 9, 2012

    Definitely a much-needed request. You can easily pull Mobile Browser in Google Analytics...

     

    In addition, the knowledge base has conflicting reports as to whether this is possible:

    The Browsers report KB article says v15 provides mobile browser data but v14 doesn't. However, the truth is, neither does.

    The Mobile KB article says mobile browser is inaccessible.

    DavidGo5
    Level 2
    July 29, 2012

    Couldn't agree more - in developing mobile sites that were functioning correctly for iOS / Android standard browsers, non-standard browsers (Firefox, Opera Mobile, Skyfire, Boat) had critical bugs.

     

    Without specific numbers we do not know which to focus on, and cannot justify the effort to fix.

    dberger-1
    dberger-1
    Level 2
    June 13, 2012

    I just talked to client care about this as well.

    When they identify the traffic as mobile, but they can't identify the Browser,  it should classify the Browser as "Unidentified - Mobile", so it least it's putting it in an understandable bucket.

    Show more replies
    Terms & ConditionsAccessibility statement

    Loading footer...