Difference between Chrome Mobile and Google Chrome in analytics | Community
Skip to main content
October 30, 2017

Difference between Chrome Mobile and Google Chrome in analytics

  • October 30, 2017
  • 1 reply
  • 9224 views

Hello,

We are actively troubleshooting a site that isn't appearing in 'Google Chrome' on iPhone per the user.    I wanted to understand how may users were accessing the site with their iphone and google chrome.   When the results presented there are two different types of entry for chrome.

Chrome Mobile (versions 47-62)  which is the more prominent in the results and Google Chrome 62.   Can someone help me understand the difference between these two entries.    

 

Chrome Mobile 55.0.2883
Chrome Mobile 56.0.2924
Chrome Mobile 47.0.2526
Chrome Mobile 54.0.2840
Firefox 9.2
Safari (unknown version)
Firefox 8.2
Firefox 9.1
Firefox 9.0
Mobile Safari 6.0
Google Chrome 62.0

We did notice on iphone,   if you access the site via the Google Chrome browser;   it does not work.    If you access the site through the Google App,  it works.

Any information or thoughts would be helpful

Thank you

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

Gigazelle
Adobe Employee
Adobe Employee
November 2, 2017

Can you help me understand your issue a bit more clearly? Is the issue that your implementation breaks while on Chrome mobile, while it works fine on the desktop?

November 3, 2017

Thank you for a response.

Yes, we are troubleshooting for Chrome on mobile,  works fine on desktop.  

The question of what is the difference between the 2 Chrome browsers listed above in the Analytics for iphone.  

     1.  Google App - Site Works

     2.  Google Chrome App for iPhone - Doesn't Work

On the Analytics - Is Chrome Mobile coming from the Google App and Google Chrome  from the Installed iphone Browser App?

Thank you

Gigazelle
Adobe Employee
Adobe Employee
November 9, 2017

I see. Well, this might be a difficult question to answer, since it seems to be specific to your implementation.

Are you able to see any JS errors while browsing via mobile? I think the key to your answer is going to be to be debugging your implementation while using Chrome Mobile.