Microsoft Edge browser is not detected in Google Analytics

Unfortunately this is true, at least as of the 30th of July 2015 at 10:47.

More and more users are installing the free Windows 10 upgrade and trying out the fresh new Edge browser that comes with the upgrade. Unfortunately there are no instances of the browser appearing in your Google Analytics reports. This will make analysis and struggle identification much more difficult if problems arise.

Google Analytics gets information about the visitors’ operating system (OS) and browser versions from the User Agent string (this is sent from your browser identifying some the technical details about your system, when you request a web page). Every browser and OS is uniquely identified when a request is made, using the User Agent string, however, the Edge browser did not inherit the Internetrix Explorer code base, as a result it has a new User Agent string, as per below;

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.<OS build number>
Source: https://msdn.microsoft.com/en-us/library/hh869301%28v=vs.85%29.aspx?f=255&MSPPError=-2147217396

The new Edge User Agent string is a combination of Safari (AppleWebKit), Chrome and it's own unique identifier - Edge. The new string also identifies the OS as version 10.0 and Windows x64 (64-bit). This User Agent string is rather similar to the Google Chrome browser, so it comes as no surprise that Edge is being falsely identified as Chrome in Google Analytics.

The following Edge browser User Agents have been found in the wild in order of popularity:

df

  1. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10240

  2. Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10240

  3. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10166

  4. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.9600

  5. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10162

  6. Mozilla/5.0 (Windows NT 10.0; Win64; x64; WebView/3.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10240

  7. Mozilla/5.0 (Windows Phone 10.0; Android 4.2.1; Microsoft; Lumia 640 XL LTE) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Edge/12.10166

  8. Mozilla/5.0 (Windows Phone 10.0; Android 4.2.1; NOKIA; 909) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Edge/12.10166

  9. Mozilla/5.0 (Windows Phone 10.0; Android 4.2.1; NOKIA; Lumia 1320) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Edge/12.10166

  10. Mozilla/5.0 (Windows Phone 10.0; Android 4.2.1; NOKIA; Lumia 1520) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Edge/12.10166

  11. Mozilla/5.0 (Windows Phone 10.0; Android 4.2.1; Nokia; Lumia 520) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Edge/12.10130

  12. Mozilla/5.0 (Windows Phone 10.0; Android 4.2.1; NOKIA; Lumia 830) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Edge/12.10512

  13. Mozilla/5.0 (Windows Phone 10.0; Android 4.2.1; NOKIA; Lumia 930) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Mobile Safari/537.36 Edge/12.10166

  14. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.135 Safari/537.36 Edge/12.10240

  15. Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36 Edge/12.0

  16. Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.71 Safari/537.36 Edge/12.0

Internetrix has created and shared a Custom Segment to help identify any existing sessions from Edge, the shared segment can be downloaded from Google Analytics Solution Gallery.

If you would like to create the custom segment yourself, below are instructions on how to do so.

  1. Navigate to the Audience Report in Google Analytics
  2. Click Add Segment and name it Edge visits (or a title of your choice)
  3. Choose Technology tab
  4. Enter Windows in the Operating System field and set match type exactly matches
  5. Enter NT in Operating System Version field and set match type exactly matches
  6. Enter Chrome in Browser field and set match type exactly matches
  7. Type 42.0.2 in Browser Version field
  8. Click Save
Microsoft_Edge_browser_is_not_detected_in_Google_Analytics_image_1

Unfortunately this solution is not a perfect fix, the majority of hits identified in this segment will be from the Edge browser, but it is not 100% accurate.

For Web 2.0 websites with rich user interactions, heavy JavaScript or any advanced tracking, Internetrix recommends creating a new Google Analytics View for identifying Edge browser traffic. The new browser only has a small market share at the moment, but following good practices and being proactive knowing your Edge traffic will help effectively identify issues with your web platforms and the new browser’s rendering engine and help eliminate visitor struggle.

Internetrix has prepared the following instructions on how to define the new Filter;

  • Filter Type: Custom -> Include
  • Filter Field: Audience/Users -> Operating System Version
  • Filter Pattern: NT

A more sophisticated approach to resolving the issue would be to rewrite the User Agent string to different existing User Agent string unique to the new View, but is recognisable by Google Analytics. An example would be to rewrite the UA string to good old Netscape, or other defunct browsers found in this list. You could then create an Advanced Filter to again rewrite this recognised UA string to some sort of Edge identified so the data appears as Edge in your reports.

Please note, these suggestions are a temporary work around and not the best way to fix the problem long term. Please contact Internetrix Google Analytics Team, if you need support or advice setting configuring these solutions.

Update, 5 Aug

The Edge browser appears in Google Analytics reports so filtering and segmenting is now easier.

Internetrix is a Google Analytics Certified Partner (GACP) and Google Analytics Premium reseller who delivers solutions to our clients to help them Win Online.

Add Your Comment

No one has commented on this page yet.

Subscribe to our mailing list to receive exclusive offers, free resources and more!