I'm curious what steps have been taken in the past several years to improve on this and how Freshpaint is approaching this. I think it's a really interesting problem and if done well, could be massively valuable. Good luck!
I'm curious what steps have been taken in the past several years to improve on this and how Freshpaint is approaching this. I think it's a really interesting problem and if done well, could be massively valuable. Good luck!
However, there are interesting use cases that are only possible via auto-tracking. Let's say a particular link on your website is broken (e.g. takes to an old sign-up page which is broken). You will be able to identify that that broken click "automatically" because the ratio of successfully signed up vs not-signed up users would be very low for people who click on that vs those who don't.
You can automatically highlight many such interesting insights by doing some basic stats counting. If you throw more advanced MLish stuff, you can find really interesting (but sometimes hard to explain) insights.
Happy to chat more if you want. Email in profile.
- You don't have the resources to setup tracking code.
- You want to look at data that you forgot to track previously. We've heard a lot of stories of people launching a new feature and forgetting to setup tracking on it.
If you have the resources to figure out and instrument everything you want to track ahead of time, then you should go ahead and do so. A manually tracked implementation is more likely to be correct than a autotracked one. Even so, auto-track is still useful as a tool for when you have new questions you want to ask or you realize that you need data that you aren't currently tracking.
You should not use autotrack to perform fishing expeditions where you just look at all the data and try to make sense of it. You should still have some guiding questions and autotrack is a tool that makes it easy to get the data you need to answer those questions.