Create a custom GA event to fire just before the geo-routing starts, and another GA event for when the geo-routing is successful, so that we can get a better idea of how #73 may be causing users to stop using the app. Theoretically if there's an event logged for the "Route Search Request" but not one for "Route Search Success" and no "Route Search Error", then a user most likely got tired of waiting or thought the app froze and closed their browser window.
Relates to #73
Create a custom GA event to fire just before the geo-routing starts, and another GA event for when the geo-routing is successful, so that we can get a better idea of how #73 may be causing users to stop using the app. Theoretically if there's an event logged for the "Route Search Request" but not one for "Route Search Success" and no "Route Search Error", then a user most likely got tired of waiting or thought the app froze and closed their browser window.