We have been thinking about this a lot in my company (RudderLabs - where we have built an open-source product around auto-tracking). Totally agreed that managin

We have been thinking about this a lot in my company (RudderLabs - where we have built an open-source product around auto-tracking). Totally agreed that managing/using all this auto-track data can be really overwhelming and sometimes it is just easier to just generate the events via code. Your maintainability point is also very important - with events generated via code, you have a single owner for updating the website and updating the events as opposed to auto-track where the responsibilities are split between website developer and marketer. 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.