5 ms·
It’s likely a tracking event. I work for an e-commerce company and tracking menu open/close is a big metric.
by yurishimo 4y ago
It’s likely a tracking event. I work for an e-commerce company and tracking menu open/close is a big metric.
- vlovich123 4y agoBut why would these be network calls that block the UI?
- 6510 4y agoIt has to track what the user does. Logging what they did previously is slightly more complicated. I imagine using the resources to do something "useful" with the data has priority.
- xsmasher 4y agoBut the call doesn't have to "block" - the UI could proceed without waiting for the result of the call.
- dcow 4y agoAnalytics calls don't generally block the UI. Must be the call the fetch the string. Or incompetence.
- pjc50 4y agoPrevent the user from blocking the tracking?
- AnIdiotOnTheNet 4y agoAre such metrics even meaningful? It sounds like metrics-for-the-metrics-god, useless unactionable information.
- deleted 4y ago[deleted]
- brookst 4y agoThe problem is you often don’t know what metrics are meaningful until after the fact. Like, if new order starts drop by 4% while traffic remains constant, what happened? If that happens, you might want to see if people are using the menu more because something got harder to find on the page. I doubt anyone is looking purely at menu opens as a metric, unless maybe trying to reduce it. But for ongoing funnel and ad hoc investigations it could be useful. So you collect it. The obvious answer is sampling rather than collecting for every user, but then you get into complicated statistics about required sample sizes if you want to correlate multiple actions across tech and demographics. Again, easier to just collect it all.
- 6510 4y agoDo many oversized tests but carefully avoid testing the test themselves because why would you? Would you test the test of the test too? etc? Someone might one day conclude the tests cost more than they are worth but it wouldn't be the ones hired to inflict them.