I think the biggest mistake is setting up analytics using client side SDKs, client side tracking. So, web and mobile SDKs, putting a mixpanel.track or segment.track in your web app or your mobile apps.
Server-side tracking beats client-side for analytics
Growth → Experimentation & Metrics
What we recommend instead, and that we've seen a lot more customers adopt recently is just track events from your servers instead of your clients. And that has three benefits. One, it's instantly cross platform. Web and mobile and TV and whatever other platform, they're all going to go through your servers, so you instantly get a hundred percent reach.
Engineers have been tracking events from servers forever. It's called logs, right? And events are just logs where they user ID in them. And so they don't need to deal with learning a new SDK and dealing with all of that.
All of these characteristics of the experience and the context that can help you look at hey, when a user only sees two drivers on the screen, they're much less likely to convert than a user who sees five drivers on a screen.
The symptom of a bad data tracking approach is you have a ton of rows with a ton of events, but every event has one property or no property being tracked.