41–47 of 47 posts
That is definitely not the case and this sounds like a cheap marketing wording on your web page. You may be visiting a prospect and may learn it from them the hard way how tracking code crushes "autotrack-and-collect-anything" approach by leaps and bounds.
I remember evaluating Heap (granted, a long time ago, so I'm sure it's evolved a lot since then) and the auto-tracking capabilities and retroactive analysis sounded awesome, but in practice it wasn't as valuable or easy as I thought. I found that in general, knowing the questions you want to answer and structuring your tracking around that to be far more useful, and that actually being able to take mountains of gener…
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.
Earlier quoted context omitted.
I just think that parent knows very well how to opt out of being tracked on his own.
Without further clarification, I'm honestly confused whether you comment is related to my own, or you just wanted to make this observation for its own sake.
I remember evaluating Heap (granted, a long time ago, so I'm sure it's evolved a lot since then) and the auto-tracking capabilities and retroactive analysis sounded awesome, but in practice it wasn't as valuable or easy as I thought. I found that in general, knowing the questions you want to answer and structuring your tracking around that to be far more useful, and that actually being able to take mountains of gener…
- 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.
Earlier quoted context omitted.
Good, server-side data is harder to fingerprint and track.
It’s pretty trivially easy to set a first-party cookie or ID for a user in local storage for non-logged-in users. Of course for SaaS all product usage is logged-in so fingerprinting doesn’t really apply.